features.txt: Fix typos
This commit is contained in:
parent
45f435e4ba
commit
8e2bad0fd9
|
@ -429,7 +429,7 @@ check for the supported properties of individual formats.
|
|||
mustnot: be used in shader modules. This also indicates whether shader
|
||||
modules can: declare the code:ClipDistance capability.
|
||||
* [[features-features-shaderCullDistance]] pname:shaderCullDistance
|
||||
indicates whether cull distances are suppored in shader code. If this
|
||||
indicates whether cull distances are supported in shader code. If this
|
||||
feature is not enabled, the code:CullDistance built-in decoration
|
||||
mustnot: be used in shader modules. This also indicates whether shader
|
||||
modules can: declare the code:CullDistance capability.
|
||||
|
@ -453,7 +453,7 @@ check for the supported properties of individual formats.
|
|||
return resource residency information are supported in shader code. If
|
||||
this feature is not enabled, the code:OpImageSparse* instructions
|
||||
mustnot: be used in shader code. This also indicates whether shader
|
||||
modules can: declare the op:SparseResidency capability. The feature
|
||||
modules can: declare the code:SparseResidency capability. The feature
|
||||
requires at least one of the ptext:sparseResidency* features to be
|
||||
supported.
|
||||
* [[features-features-shaderResourceMinLod]] pname:shaderResourceMinLod
|
||||
|
@ -713,7 +713,7 @@ properties of the physical device:
|
|||
ename:VK_DESCRIPTOR_TYPE_STORAGE_BUFFER,
|
||||
ename:VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC,
|
||||
ename:VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC, or
|
||||
enume:VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT count against this limit. For
|
||||
ename:VK_DESCRIPTOR_TYPE_INPUT_ATTACHMENT count against this limit. For
|
||||
the fragment shader stage the framebuffer color attachments also count
|
||||
against this limit.
|
||||
* [[features-limits-maxDescriptorSetSamplers]]
|
||||
|
|
Loading…
Reference in New Issue