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

View File

@ -218,7 +218,7 @@ A future extension could add this functionality.
be? be?
*RESOLVED*: The lifetime of the instance. *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 A future extension may be added to expose a way to destroy these objects
and/or support display hotplug. and/or support display hotplug.

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? as input to semaphore state import operations?
*RESOLVED*: Implementations must return an error to the application if the *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. import operation.
However, implementations need not validate handles are of the exact type However, implementations need not validate handles are of the exact type
specified by the application. specified by the application.

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 any resources or synchronization primitives referenced is unaffected by the
call or its failure. call or its failure.
If fname:vkQueuePresentKHR fails in such a way that the implementation can: If fname:vkQueuePresentKHR fails in such a way that the implementation is
not make that guarantee, the implementation must: return unable to make that guarantee, the implementation must: return
ename:VK_ERROR_DEVICE_LOST. ename:VK_ERROR_DEVICE_LOST.
However, if the presentation request is rejected by the presentation engine However, if the presentation request is rejected by the presentation engine

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 any resources or synchronization primitives referenced by the submitted
command buffers and any semaphores referenced by pname:pSubmits is command buffers and any semaphores referenced by pname:pSubmits is
unaffected by the call or its failure. unaffected by the call or its failure.
If fname:vkQueueSubmit fails in such a way that the implementation can: not If fname:vkQueueSubmit fails in such a way that the implementation is unable
make that guarantee, the implementation must: return to make that guarantee, the implementation must: return
ename:VK_ERROR_DEVICE_LOST. ename:VK_ERROR_DEVICE_LOST.
See <<devsandqueues-lost-device,Lost Device>>. See <<devsandqueues-lost-device,Lost Device>>.