Merge pull request #665 from krOoze/fix_broken_links

Fix some broken links

doc/specs/vulkan/appendices/VK_KHR_external_fence_capabilities.txt

@@ -15,7 +15,7 @@ include::meta/VK_KHR_external_fence_capabilities.txt[]
   - James Jones, NVIDIA
   - Jeff Juliano, NVIDIA
   - Cass Everitt, Oculus
-  - Contributors to `<<VK_KHR_external_semaphore_capablities>>`
+  - Contributors to `<<VK_KHR_external_semaphore_capabilities>>`
 
 An application may wish to reference device fences in multiple Vulkan
 logical devices or instances, in multiple processes, and/or in multiple

doc/specs/vulkan/appendices/VK_KHR_multiview.txt

@@ -56,7 +56,7 @@ None.
 
 === New SPIR-V Capabilities
 
-  * <<spirvenv-capabilities-table-multiview,code:MultiView>>
+  * <<spirvenv-capabilities-multiview,code:MultiView>>
 
 === Promotion to Vulkan 1.1
 

doc/specs/vulkan/appendices/boilerplate.txt

@@ -37,7 +37,7 @@ created some additional bindings.
 Applications normally will include the header `vulkan.h`.
 In turn, `vulkan.h` always includes the following headers:
 
-  * <<boilerplate-vk-platform,`vk_platform.h`>>, defining platform-specific
+  * <<boilerplate-platform-macros,`vk_platform.h`>>, defining platform-specific
     macros and headers.
   * <<boilerplate-vulkan-core,`vulkan_core.h`>>, defining APIs for the
     Vulkan core and all registered extensions _other_ than window

doc/specs/vulkan/appendices/spirvenv.txt

@@ -51,7 +51,8 @@ ifdef::VK_VERSION_1_1,VK_KHR_device_group[]
   * code:DeviceGroup
 endif::VK_VERSION_1_1,VK_KHR_device_group[]
 ifdef::VK_VERSION_1_1,VK_KHR_multiview[]
-  * code:MultiView
+  * [[spirvenv-capabilities-multiview]]
+    code:MultiView
 endif::VK_VERSION_1_1,VK_KHR_multiview[]
 
 If the implementation supports any of the optional: features described in
@@ -98,6 +99,7 @@ endif::VK_VERSION_1_1[]
 endif::VK_VERSION_1_1,VK_KHR_shader_draw_parameters[]
 ifndef::VK_VERSION_1_1[]
 ifdef::VK_KHR_multiview[]
+[[spirvenv-capabilities-multiview]]
 | code:MultiView                          | <<VK_KHR_multiview,VK_KHR_multiview>>
 endif::VK_KHR_multiview[]
 ifdef::VK_KHR_device_group[]

doc/specs/vulkan/appendices/versions.txt

@@ -59,7 +59,7 @@ The only changes to the functionality added by these extensions were to
 <<features-features-shaderDrawParameters, feature bit>> added to determine
 support in the core API, and
 <<features-features-variablePointersStorageBuffer,
-pname:variablePointerStorageBuffer>> from `VK_KHR_variable_pointers` was
+pname:variablePointersStorageBuffer>> from `VK_KHR_variable_pointers` was
 made optional.
 
 Additionally, Vulkan 1.1 added support for

doc/specs/vulkan/chapters/VK_EXT_debug_utils.txt

@@ -14,9 +14,9 @@ The <<debugging-command-buffer-labels,Command Buffer Labels>> section
 describes how to associate logical elements of the scene with commands in a
 slink:VkCommandBuffer.
 
-The <<debug-messengers,Debug Messengers>> section describes how to create
-debug messenger objects associated with an application supplied callback to
-capture debug messages from a variety of Vulkan components.
+The <<debugging-debug-messengers,Debug Messengers>> section describes how to
+create debug messenger objects associated with an application supplied
+callback to capture debug messages from a variety of Vulkan components.
 
 [[debugging-object-debug-annotation]]
 === Object Debug Annotation

doc/specs/vulkan/chapters/cmdbuffers.txt

@@ -822,7 +822,7 @@ executable state>>.
 ifdef::VK_EXT_debug_utils[]
   * [[VUID-vkEndCommandBuffer-commandBuffer-01815]]
     If pname:commandBuffer is a secondary command buffer, there must: not be
-    an outstanding flink:vkCmdBeginUtilsLabelEXT command recorded to
+    an outstanding flink:vkCmdBeginDebugUtilsLabelEXT command recorded to
     pname:commandBuffer that has not previously been ended by a call to
     flink:vkCmdEndDebugUtilsLabelEXT.
 endif::VK_EXT_debug_utils[]

doc/specs/vulkan/chapters/fundamentals.txt

@@ -471,7 +471,13 @@ existing applications.
 
 Shared library implementations should: provide library symbols for commands
 in the highest version of this Specification they support, and for
-<<wsi,Window System Integration>> extensions relevant to the platform.
+ifdef::VK_KHR_surface[]
+<<wsi,Window System Integration>>
+endif::VK_KHR_surface[]
+ifndef::VK_KHR_surface[]
+Window System Integration
+endif::VK_KHR_surface[]
+extensions relevant to the platform.
 They may: also provide library symbols for commands defined by additional
 extensions.
 
@@ -860,8 +866,6 @@ options, but basetype:VkFlags is not used directly in the API.
 Instead, a etext:Vk*Flags type which is an alias of basetype:VkFlags, and
 whose name matches the corresponding etext:Vk*FlagBits that are valid for
 that type, is used.
-These aliases are described in the <<boilerplate-flags,Flag Types>> appendix
-of the Specification.
 
 --