Fix code listing link formatting

Overv · Overv · commit 5442a3bf18b8 · 2017-01-19T22:50:41.000+01:00
diff --git a/03_Drawing_a_triangle/00_Setup/00_Base_code.md b/03_Drawing_a_triangle/00_Setup/00_Base_code.md
@@ -319,4 +319,4 @@ When you run the program now you should see a window titled `Vulkan` show up
 until the application is terminated by closing the window. Now that we have the
 skeleton for the Vulkan application, let's [create the first Vulkan object](!Drawing_a_triangle/Setup/Instance)!
 
-[C++ code](/code/base_code.cpp) /
+[C++ code](/code/base_code.cpp)
diff --git a/03_Drawing_a_triangle/00_Setup/01_Instance.md b/03_Drawing_a_triangle/00_Setup/01_Instance.md
@@ -128,7 +128,7 @@ variable that stores the number of extensions and an array of
 optional first parameter that allows us to filter extensions by a specific
 validation layer, which we'll ignore for now.
 
-To allocate an array to hold the extension details we first need to know how 
+To allocate an array to hold the extension details we first need to know how
 many there are. You can request just the number of extensions by leaving the
 latter parameter empty:
 
@@ -170,4 +170,4 @@ list.
 Before continuing with the more complex steps after instance creation, it's time
 to evaluate our debugging options by checking out [validation layers](!Drawing_a_triangle/Setup/Validation_layers).
 
-[C++ code](/code/instance_creation.cpp) /
+[C++ code](/code/instance_creation.cpp)
diff --git a/03_Drawing_a_triangle/00_Setup/02_Validation_layers.md b/03_Drawing_a_triangle/00_Setup/02_Validation_layers.md
@@ -377,4 +377,4 @@ you how helpful the validation layers are with catching them and to teach you
 how important it is to know exactly what you're doing with Vulkan. Now it's time
 to look at [Vulkan devices in the system](!Drawing_a_triangle/Setup/Physical_devices_and_queue_families).
 
-[C++ code](/code/validation_layers.cpp) /
+[C++ code](/code/validation_layers.cpp)
diff --git a/03_Drawing_a_triangle/00_Setup/03_Physical_devices_and_queue_families.md b/03_Drawing_a_triangle/00_Setup/03_Physical_devices_and_queue_families.md
@@ -277,4 +277,4 @@ Great, that's all we need for now to find the right physical device! The next
 step is to [create a logical device](!Drawing_a_triangle/Setup/Logical_device_and_queues)
 to interface with it.
 
-[C++ code](/code/physical_device_selection.cpp) /
+[C++ code](/code/physical_device_selection.cpp)
diff --git a/03_Drawing_a_triangle/00_Setup/04_Logical_device_and_queues.md b/03_Drawing_a_triangle/00_Setup/04_Logical_device_and_queues.md
@@ -159,4 +159,4 @@ With the logical device and queue handles we can now actually start using the
 graphics card to do things! In the next few chapters we'll set up the resources
 to present results to the window system.
 
-[C++ code](/code/logical_device.cpp) /
+[C++ code](/code/logical_device.cpp)
diff --git a/03_Drawing_a_triangle/01_Presentation/00_Window_surface.md b/03_Drawing_a_triangle/01_Presentation/00_Window_surface.md
@@ -215,4 +215,4 @@ In case the queue families are the same, the two handles will most likely have
 the same value now. In the next chapter we're going to look at swap chains and
 how they give us the ability to present images to the surface.
 
-[C++ code](/code/window_surface.cpp) /
+[C++ code](/code/window_surface.cpp)
diff --git a/03_Drawing_a_triangle/01_Presentation/01_Swap_chain.md b/03_Drawing_a_triangle/01_Presentation/01_Swap_chain.md
@@ -585,4 +585,4 @@ We now have a set of images that can be drawn onto and can be presented to the
 window. The next two chapters will cover how we can set up the images as render
 targets and then we start looking into the actual drawing commands!
 
-[C++ code](/code/swap_chain_creation.cpp) /
+[C++ code](/code/swap_chain_creation.cpp)
diff --git a/03_Drawing_a_triangle/01_Presentation/02_Image_views.md b/03_Drawing_a_triangle/01_Presentation/02_Image_views.md
@@ -42,7 +42,7 @@ deleter function.
 ```c++
 void createImageViews() {
     swapChainImageViews.resize(swapChainImages.size(), VDeleter<VkImageView>{device, vkDestroyImageView});
-    
+
 }
 ```
 
@@ -119,4 +119,4 @@ quite ready to be used as a render target just yet. That requires one more step
 of indirection, known as a framebuffer. But first we'll have to set up the
 graphics pipeline.
 
-[C++ code](/code/image_views.cpp) /
+[C++ code](/code/image_views.cpp)
diff --git a/03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.md b/03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.md
@@ -96,4 +96,4 @@ void createGraphicsPipeline() {
 }
 ```
 
-[C++ code](/code/graphics_pipeline.cpp) /
+[C++ code](/code/graphics_pipeline.cpp)

Original file line number	Diff line number	Diff line change
`@@ -96,4 +96,4 @@ void createGraphicsPipeline() {`
`96`	`96`	`}`
`97`	`97`	```
`98`	`98`
`99`		`-[C++ code](/code/graphics_pipeline.cpp) /`
	`99`	`+[C++ code](/code/graphics_pipeline.cpp)`