Fix more broken links

Author: SaschaWillems

en/00_Introduction.adoc

@@ -129,8 +129,7 @@ certain Vulkan feature.
 That means that the site is also useful as a reference.
 All the Vulkan functions and types are linked to the specification, so you
 can click them to learn more.
-You are encouraged to submit feedback to https://github
-.com/KhronosGroup/Vulkan-Docs[this Khronos repository].
+You are encouraged to submit feedback to https://github.com/KhronosGroup/Vulkan-Docs[this Khronos repository].
 
 As mentioned before, the Vulkan API has a rather verbose API with many
 parameters to give you maximum control over the graphics hardware.

en/01_Overview.adoc

@@ -28,8 +28,8 @@ with the existing APIs somehow. This resulted in less than ideal abstractions
 Aside from these new features, the past decade also saw an influx of mobile
 and embedded devices with powerful graphics hardware. These mobile GPUs have
  different architectures based on their energy and space requirements.
-One such example is https://en.wikipedia.org/wiki/Tiled_rendering[tiled
-rendering], which would benefit from improved performance by offering the
+One such example is https://en.wikipedia.org/wiki/Tiled_rendering[tiled rendering], 
+which would benefit from improved performance by offering the
 programmer more control over this functionality.
 Another limitation originating from the age of these APIs is limited
 multi-threading support, which can result in a bottleneck on the CPU side.

en/02_Development_environment.adoc

@@ -297,7 +297,7 @@ The most important parts you'll need for developing Vulkan applications on
 Linux are the Vulkan loader, validation layers, and a couple of command-line
 utilities to test whether your machine is Vulkan-capable:
 
-Download the VulkanSDK tarball from (https://vulkan.lunarg.com/)[LunarG].
+Download the VulkanSDK tarball from https://vulkan.lunarg.com/[LunarG].
 Place the uncompressed VulkanSDK in a convenient path, and create a symbolic
 link to the latest on like so:
 
@@ -410,9 +410,9 @@ CMake project for Vulkan and write a little bit of code to make sure that
 everything works.
 
 I will assume that you already have some basic experience with CMake, like
-how variables and rules work. If not, you can get up to speed very quickly with (https://cmake.org/cmake/help/book/mastering-cmake/cmake/Help/guide/tutorial/)[this tutorial].
+how variables and rules work. If not, you can get up to speed very quickly with https://cmake.org/cmake/help/book/mastering-cmake/cmake/Help/guide/tutorial/[this tutorial].
 
-You can now use the ink:/attachments/[attachments] directory in this tutorial as a template for your
+You can now use the link:/attachments/[attachments] directory in this tutorial as a template for your
 Vulkan projects. Make a copy, rename it to something like `HelloTriangle`
 and remove all the code in `main.cpp`.
 
@@ -465,7 +465,7 @@ Most of the instructions here are essentially a lot of "plumbing," so we can get
 Also, keep in mind that during the following instructions whenever we mention the folder `vulkansdk` we are referring to the folder where you extracted the Vulkan SDK.
 
 We recommend using CMake everywhere, and Apple is no different. An example
-of how to use CMake for Apple can be found (https://medium.com/practical-coding/migrating-to-cmake-in-c-and-getting-it-working-with-xcode-50b7bb80ae3d)[here]
+of how to use CMake for Apple can be found https://medium.com/practical-coding/migrating-to-cmake-in-c-and-getting-it-working-with-xcode-50b7bb80ae3d[here]
 We also have documentation for using a cmake project in Apple environments
 at the VulkanSamples project.  It targets both iOS and Desktop Apple.
 

en/03_Drawing_a_triangle/00_Setup/04_Logical_device_and_queues.adoc

@@ -162,7 +162,7 @@ extension in the swap chain chapter.
 
 Previous implementations of Vulkan made a distinction between instance and
 device-specific validation layers, but this is
-(https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap40.html#extendingvulkan-layers-devicelayerdeprecation)[no longer the case].
+link:https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/chap40.html#extendingvulkan-layers-devicelayerdeprecation[no longer the case].
 That means that the `enabledLayerCount` and `ppEnabledLayerNames` fields of
 `VkDeviceCreateInfo` are ignored by up-to-date implementations.
 

en/03_Drawing_a_triangle/01_Presentation/01_Swap_chain.adoc

@@ -158,7 +158,7 @@ that order with an 8-bit unsigned integer for a total of 32 bits per pixel. The
 the `VK_COLOR_SPACE_SRGB_NONLINEAR_KHR` flag. Note that this flag used to be
 called `VK_COLORSPACE_SRGB_NONLINEAR_KHR` in old versions of the specification.
 
-For the color space we'll use SRGB if it is available, because it [results in more accurate perceived colors](http://stackoverflow.com/questions/12524623/). It is also pretty much the standard color space for images, like the textures we'll use later on.
+For the color space we'll use SRGB if it is available, because it link:http://stackoverflow.com/questions/12524623/[results in more accurate perceived colors]. It is also pretty much the standard color space for images, like the textures we'll use later on.
 Because of that we should also use an SRGB color format, of which one of the most common ones is `VK_FORMAT_B8G8R8A8_SRGB`.
 
 Let's go through the list and see if the preferred combination is available:
@@ -267,7 +267,7 @@ resolution that best matches the window within the `minImageExtent` and
 `maxImageExtent` bounds. But we must specify the resolution in the correct unit.
 
 GLFW uses two units when measuring sizes: pixels and
-[screen coordinates](https://www.glfw.org/docs/latest/intro_guide.html#coordinate_systems).
+link:https://www.glfw.org/docs/latest/intro_guide.html#coordinate_systems[screen coordinates].
 For example, the resolution `{WIDTH, HEIGHT}` that we specified earlier when
 creating the window is measured in screen coordinates. But Vulkan works with
 pixels, so the swap chain extent must be specified in pixels as well.