Resolve some typos (#2333)

BUILD.adoc

@@ -481,7 +481,7 @@ toolchain yourself.
 [[building-epub-outputs]]
 === Building EPUB Outputs
 
-The `epub` target will generate an EPUB file in in
+The `epub` target will generate an EPUB file in
 `$(OUTDIR)/epub/vkspec.epub`. Note that the `epub` target is
 community-contributed, and not supported by Khronos. See
 https://github.com/KhronosGroup/Vulkan-Docs/pull/2286 for more.

appendices/VK_QCOM_image_processing.adoc

@@ -58,7 +58,7 @@ The instructions do not-support sampling of mipmap, multi-plane,
 multi-layer, multi-sampled, or depth/stencil images.
 The instructions can be used in any shader stage.
 
-Implementations of this this extension should support these operations
+Implementations of this extension should support these operations
 natively at the HW instruction level, offering potential performance gains
 as well as ease of development.
 

appendices/VK_QCOM_image_processing2.adoc

@@ -25,7 +25,7 @@ It builds on the functionality of QCOM_image_processing with the addition of
   * The code:opImageBlockMatchWindowSADQCOM` SPIR-V instruction builds upon
     the functionality of code:opImageBlockMatchSADQCOM` by repeatedly
     performing block match operations across a 2D window.
-    The "`2D windowExtent`" and "`compareMode`" are are specified by
+    The "`2D windowExtent`" and "`compareMode`" are specified by
     slink:VkSamplerBlockMatchWindowCreateInfoQCOM in the sampler used to
     create the _target image_.
     Like code:OpImageBlockMatchSADQCOM, code:opImageBlockMatchWindowSADQCOM

appendices/VK_QCOM_multiview_per_view_viewports.adoc

@@ -36,7 +36,7 @@ include::{generated}/interfaces/VK_QCOM_multiview_per_view_viewports.adoc[]
 
 === Issues
 
-1) Is is possible to enable/disable the
+1) Is it possible to enable/disable the
 <<features-multiview-per-view-viewports, pname:multiviewPerViewViewports>>
 feature for individual render pass instances?
 
@@ -45,14 +45,14 @@ vkCreateDevice, then all created render pass instances (including dynamic
 render passes from `apiext:VK_KHR_dynamic_rendering`) and all created
 VkPipelines will have the feature enabled.
 This approach was chosen because it simplifies application code and there is
-no known use case enable/disable the feature for individual render passes or
+no known use case to enable/disable the feature for individual render passes or
 pipelines.
 
 2) When this extension is used, is the value of code:ViewportIndex
 implicitly written by the last pre-rasterization shader stage and can the
 value of code:ViewportIndex be read in the fragment shader?
 
-*RESOLVED*: No, use of the extension extension does not add an implicit
+*RESOLVED*: No, use of the extension does not add an implicit
 write to code:ViewportIndex in any shader stage, and additionally, the value
 of code:ViewportIndex in the fragment shader is undefined.
 

appendices/VK_QCOM_render_pass_transform.adoc

@@ -114,10 +114,10 @@ uint32_t  minor = ((driverVersion) >> 12) & 0x3ff);
 uint32_t  patch = ((driverVersion) & 0xfff);
 ----
 
-If the Adreno major.minor.patch version is greater than or equal to to
+If the Adreno major.minor.patch version is greater than or equal to
 512.469.0, then simply use the VK_STRUCTURE_TYPE values as defined in
 vulkan_core.h.
-If the version is less than or equal to to 512.468.0, then use the alternate
+If the version is less than or equal to 512.468.0, then use the alternate
 values for the two VK_STRUCTURE_TYPEs in the table below.
 
 .fname:Adreno Driver Requirements

chapters/VK_NV_low_latency2/low_latency2.adoc

@@ -216,7 +216,7 @@ include::{generated}/api/structs/VkGetLatencyMarkerInfoNV.adoc[]
   * pname:sType is a elink:VkStructureType value identifying this structure.
   * pname:pNext is either `NULL` or a pointer to a structure extending this
     structure.
-  * pname:timingCount is an integer related to the number of of previous
+  * pname:timingCount is an integer related to the number of previous
     frames of latency data available or queried, as described below.
   * pname:pTimings is either `NULL` or a pointer to an array of
     slink:VkLatencyTimingsFrameReportNV structures.

chapters/accelstructures.adoc

@@ -1262,7 +1262,7 @@ structure should be 152 bytes in size.
 include::{generated}/validity/structs/VkAccelerationStructureMotionInstanceNV.adoc[]
 --
 
-[open,refpage='VkAccelerationStructureMotionInstanceDataNV',desc='Union specifying a acceleration structure motion instance data for building into an acceleration structure geometry',type='structs']
+[open,refpage='VkAccelerationStructureMotionInstanceDataNV',desc='Union specifying an acceleration structure motion instance data for building into an acceleration structure geometry',type='structs']
 --
 :refpage: VkAccelerationStructureMotionInstanceDataNV
 

chapters/capabilities.adoc

@@ -876,7 +876,7 @@ ifdef::VK_KHR_maintenance6[]
 Instead of querying all the potential formats that the application might use
 in the descriptor layout, the application can: use the
 slink:VkPhysicalDeviceMaintenance6PropertiesKHR::pname:maxCombinedImageSamplerDescriptorCount
-property to determine the maximum descriptor size that that will accommodate
+property to determine the maximum descriptor size that will accommodate
 any and all <<formats-requiring-sampler-ycbcr-conversion, formats that
 require a sampler {YCbCr} conversion>> supported by the implementation.
 endif::VK_KHR_maintenance6[]

chapters/interfaces.adoc

@@ -756,10 +756,10 @@ include::{generated}/api/structs/VkRenderingInputAttachmentIndexInfoKHR.adoc[]
     color attachments to be used as input attachments.
   * pname:pDepthInputAttachmentIndex is either `NULL`, or a pointer to a
     code:uint32_t value defining the index for the depth attachment to be
-    used an an input attachment.
+    used as an input attachment.
   * pname:pStencilInputAttachmentIndex is either `NULL`, or a pointer to a
     code:uint32_t value defining the index for the stencil attachment to be
-    used an an input attachment.
+    used as an input attachment.
 
 This structure allows applications to remap attachments to different input
 attachment indices.

chapters/memory.adoc

@@ -4482,7 +4482,7 @@ endif::VK_VERSION_1_2,VK_KHR_image_format_list[]
 
 
 [[memory-external-android-hardware-buffer-buffer-resources]]
-===== Android Hardware Buffer Buffer Resources
+===== Android Hardware Buffer Resources
 
 Android hardware buffers with a format of code:AHARDWAREBUFFER_FORMAT_BLOB
 and usage that includes code:AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER can: be

chapters/primsrast.adoc

@@ -4091,7 +4091,7 @@ include::{generated}/api/structs/VkPipelineRasterizationConservativeStateCreateI
 
 If this structure is not included in the pname:pNext chain,
 pname:conservativeRasterizationMode is considered to be
-ename:VK_CONSERVATIVE_RASTERIZATION_MODE_DISABLED_EXT, and and conservative
+ename:VK_CONSERVATIVE_RASTERIZATION_MODE_DISABLED_EXT, and conservative
 rasterization is disabled.
 
 Polygon rasterization can: be made conservative by setting

chapters/renderpass.adoc

@@ -6894,8 +6894,8 @@ areas, may: be used by the implementation for optimizations, but does not
 affect loads, stores, or resolves.
 
 If this structure is present and if pname:perViewRenderAreaCount is not
-zero, then pname:perViewRenderAreaCount must: be at least least one greater
-than the most significant bit set in any any element of
+zero, then pname:perViewRenderAreaCount must: be at least one greater
+than the most significant bit set in any element of
 slink:VkRenderPassMultiviewCreateInfo::pname:pViewMasks.
 ifdef::VK_VERSION_1_3,VK_KHR_dynamic_rendering[or slink:VkRenderingInfo::pname:viewMask]
 

chapters/shaders.adoc

@@ -639,7 +639,7 @@ how some other getter-type commands work in Vulkan.
 Because shader binary data is only usable in its entirety, it would never be
 useful for the implementation to return partial data.
 Because of this, nothing is written to pname:pData unless pname:pDataSize is
-large enough to fit the data it its entirety.
+large enough to fit the data in its entirety.
 ====
 
 Binary shader code retrieved using fname:vkGetShaderBinaryDataEXT can: be

chapters/textures.adoc

@@ -3617,7 +3617,7 @@ matching of two blocks within a single image.
 
 Similar to an equivalent code:OpImageFetch instruction,
 code:opImageBlockMatchSAD and code:opImageBlockMatchSAD specify an
-code:image and an integer texel code:coordinate which which describes the
+code:image and an integer texel code:coordinate which describes the
 bottom-left texel of the target block.
 There are three additional inputs.
 The code:reference and code:refCoodinate specifies bottom-left texel of the
@@ -3790,7 +3790,7 @@ The target coordinates are combinations of coordinates from
 latexmath:[(u,v)] to latexmath:[(u + windowWidth - 1, v + windowHeight - 1)]
 where latexmath:[windowHeight] and latexmath:[windowWidth] are specified by
 slink:VkSamplerBlockMatchWindowCreateInfoQCOM::pname:windowExtent.
-At each each target coordinate, a
+At each target coordinate, a
 <<textures-blockmatch-filteroperation,block matching operation>> is
 performed, resulting in a difference metric.
 The reference coordinate latexmath:[(s,t)] is fixed.

chapters/video/encode.adoc

@@ -697,7 +697,7 @@ include::{generated}/api/structs/VkVideoEncodeSessionParametersFeedbackInfoKHR.a
     were <<encode-overrides,overridden>> by the implementation.
 
 Depending on the used video encode operation, additional codec-specific
-structures can: be be included in the pname:pNext chain of this structure to
+structures can: be included in the pname:pNext chain of this structure to
 capture codec-specific feedback information about the requested parameter
 data, as described in the corresponding sections.
 

proposals/VK_KHR_maintenance5.adoc

@@ -63,7 +63,7 @@ Some tile-based GPUs can benefit from providing an optimal render area granulari
 === vkGetDeviceProcAddr to return NULL for functions beyond app version
 
 Existing implementations have different behaviour when returning function pointers from `vkGetDeviceProcAddr()`
-for supported core functions of versions greater than than the version requested by the application.
+for supported core functions of versions greater than the version requested by the application.
 
 === Add vkCmdBindIndexBuffer2KHR with a size parameter
 

proposals/VK_QCOM_image_processing.adoc

@@ -276,7 +276,7 @@ VkSampler objects created for use with the built-ins added with this extension
 must be created with `VK_SAMPLER_CREATE_IMAGE_PROCESSING_BIT_QCOM`.
 Such samplers must not be used with the other existing `OpImage*` built-ins
 unrelated to this extension.  In practice, this means an application must create
-dedicated VkSamplers use use with this extension.
+dedicated VkSamplers for use with this extension.
 
 The `OpImageSampleWeightedQCOM` and `OpImageSampleBoxFilterQCOM` built-ins
 support samplers with `unnormalizedCoordinates` equal to `VK_TRUE` or
@@ -466,7 +466,7 @@ values for a weight image descriptor.
 For a separable weight filtering, the view will be type VK_IMAGE_VIEW_TYPE_1D_ARRAY.
 Horizontal weights for all phases are packed in layer '0' and the vertical weights for
 all phases are packed in layer '1'.  Within each layer, the weights are arranged into
-groups of 4.  For each group, the weights are ordered by by phase. Expressed as a
+groups of 4.  For each group, the weights are ordered by phase. Expressed as a
 formula, the 1D texel offset for all weights and phases within each layer is computed as:
 
 [source,c]
@@ -490,7 +490,7 @@ For each texel covered by the box, a weight value is computed by the implementat
 The weight is proportional to the area of the texel covered.  Those texels that are
 fully covered by the box receive a weight of 1.0.  Those texels that are partially
 covered by the box receive a weight proportional to the covered area.  For example,
-a texel that has one one quarter of its area covered by the box will receive a
+a texel that has one quarter of its area covered by the box will receive a
 weight of 0.25.
 
 If the sampler `reductionMode` is `VK_SAMPLER_REDUCTION_MODE_WEIGHTED_AVERAGE` then the

scripts/doctransformer.py

@@ -336,7 +336,7 @@ def apiMatch(self, oldname, newname):
         return oldname.rstrip(upper) == newname.rstrip(upper)
 
     def transformFile(self, lines):
-        """Transform lines, and possibly output to to the given file."""
+        """Transform lines, and possibly output to the given file."""
 
         for line in lines:
             self.state.incrLineNumber()

style/extensions.adoc

@@ -929,7 +929,7 @@ This case will come up very rarely.
 
 When an extension introduces a new flags (etext:*Flags) type, it should also
 introduce a corresponding new bitmask (etext:*FlagBits) type.
-The flags type contains zero more more bits from the bitmask, and is used to
+The flags type contains zero or more bits from the bitmask, and is used to
 specify sets of bits for commands or structures.
 
 In some cases, a new flags type will be defined with no individual bits yet