status-im
/
Vulkan-Docs
mirror of https://github.com/status-im/Vulkan-Docs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix "can not" 

- 2x improper use per Terminology
- 2x just grammar
This commit is contained in:
Petr Kraus 2018-03-16 17:39:05 +01:00
parent ce60b9c887
commit eaef9db837
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/specs/vulkan/appendices/VK_KHR_display.txt
View File

@ -218,7 +218,7 @@ A future extension could add this functionality.
be?
*RESOLVED*: The lifetime of the instance.
These objects can not be destroyed.
These objects cannot be destroyed.
A future extension may be added to expose a way to destroy these objects
and/or support display hotplug.

2
doc/specs/vulkan/appendices/VK_KHR_external_semaphore.txt
View File

@ -72,7 +72,7 @@ Requiring this level of trust is undesireable for many potential use cases.
as input to semaphore state import operations?
*RESOLVED*: Implementations must return an error to the application if the
provided semaphore state handle can not be used to complete the requested
provided semaphore state handle cannot be used to complete the requested
import operation.
However, implementations need not validate handles are of the exact type
specified by the application.

4
doc/specs/vulkan/chapters/VK_KHR_swapchain/wsi.txt
View File

@ -997,8 +997,8 @@ If it does, the implementation must: ensure that the state and contents of
any resources or synchronization primitives referenced is unaffected by the
call or its failure.
If fname:vkQueuePresentKHR fails in such a way that the implementation can:
not make that guarantee, the implementation must: return
If fname:vkQueuePresentKHR fails in such a way that the implementation is
unable to make that guarantee, the implementation must: return
ename:VK_ERROR_DEVICE_LOST.
However, if the presentation request is rejected by the presentation engine

4
doc/specs/vulkan/chapters/cmdbuffers.txt
View File

@ -908,8 +908,8 @@ If it does, the implementation must: ensure that the state and contents of
any resources or synchronization primitives referenced by the submitted
command buffers and any semaphores referenced by pname:pSubmits is
unaffected by the call or its failure.
If fname:vkQueueSubmit fails in such a way that the implementation can: not
make that guarantee, the implementation must: return
If fname:vkQueueSubmit fails in such a way that the implementation is unable
to make that guarantee, the implementation must: return
ename:VK_ERROR_DEVICE_LOST.
See <<devsandqueues-lost-device,Lost Device>>.