From 79a4549d0eeed766d38a06fc93f7029e6a7a5a87 Mon Sep 17 00:00:00 2001 From: Petr Kraus Date: Mon, 4 Dec 2017 20:46:27 +0100 Subject: [PATCH] Fix Note markup --- .../VK_KHR_android_surface/platformCreateSurface_android.txt | 2 +- doc/specs/vulkan/chapters/features.txt | 2 +- doc/specs/vulkan/chapters/resources.txt | 2 +- doc/specs/vulkan/chapters/shaders.txt | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/specs/vulkan/chapters/VK_KHR_android_surface/platformCreateSurface_android.txt b/doc/specs/vulkan/chapters/VK_KHR_android_surface/platformCreateSurface_android.txt index 11c527f5..3b05280f 100644 --- a/doc/specs/vulkan/chapters/VK_KHR_android_surface/platformCreateSurface_android.txt +++ b/doc/specs/vulkan/chapters/VK_KHR_android_surface/platformCreateSurface_android.txt @@ -29,7 +29,7 @@ same code:ANativeWindow and any attempts to connect to the same code:ANativeWindow through other platform mechanisms will fail. [NOTE] -.NOTE +.Note ==== In particular, only one sname:VkSurfaceKHR can: exist at a time for a given window. diff --git a/doc/specs/vulkan/chapters/features.txt b/doc/specs/vulkan/chapters/features.txt index 6ecf576b..2d0c7fbf 100644 --- a/doc/specs/vulkan/chapters/features.txt +++ b/doc/specs/vulkan/chapters/features.txt @@ -18,7 +18,7 @@ explicitly queried before use to ensure they are supported by the implementation. [NOTE] -.Note on extensibility +.Note ==== The features and limits are reported via basic structures (that is slink:VkPhysicalDeviceFeatures and slink:VkPhysicalDeviceLimits), as well as diff --git a/doc/specs/vulkan/chapters/resources.txt b/doc/specs/vulkan/chapters/resources.txt index e1dae46d..3dd78818 100644 --- a/doc/specs/vulkan/chapters/resources.txt +++ b/doc/specs/vulkan/chapters/resources.txt @@ -3890,8 +3890,8 @@ A buffer or image memory barrier is not required to acquire _ownership_ when no queue family owns the resource - it is implicitly acquired upon first use within a queue. -.Note [NOTE] +.Note ==== Images still require a <> from ename:VK_IMAGE_LAYOUT_UNDEFINED or ename:VK_IMAGE_LAYOUT_PREINITIALIZED diff --git a/doc/specs/vulkan/chapters/shaders.txt b/doc/specs/vulkan/chapters/shaders.txt index b71c5e99..c1b7f343 100644 --- a/doc/specs/vulkan/chapters/shaders.txt +++ b/doc/specs/vulkan/chapters/shaders.txt @@ -278,8 +278,8 @@ The order that coherent writes to different locations become available is undefined, unless enforced by a memory barrier instruction or other memory dependency. -.Note [NOTE] +.Note ==== Explicit memory dependencies must: still be used to guarantee availability and visibility for access via other buffers, buffer views, or image views. @@ -295,8 +295,8 @@ write. Atomic operations ensure automatic availability and visibility for writes and reads in the same way as those to code:Coherent variables. +[NOTE] .Note -[[NOTE]] ==== Memory accesses performed on different resource descriptors with the same memory backing may: not be well-defined even with the code:Coherent