diff options
| author | Gangzheng Tong <gtong@nvidia.com> | 2025-04-11 15:34:07 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-11 22:34:07 +0000 |
| commit | 8e6af6259bd1dd47d81c36f0562ff362ca5d42c3 (patch) | |
| tree | 86e7a9671dae748922ca18eec544a318cd708443 /docs/user-guide/05-capabilities.md | |
| parent | 61a6c211b1587a7b9ed6a24ae1ba6fe0600c80d8 (diff) | |
Fix user-guide typos (#6789)
* Fix user-guide typos
Use LLM to scan each of the markdown files to fix typos.
Try not to change anything but the typos in this CL.
* typo not caught by LLM
* add output of ./build_toc.ps1
Diffstat (limited to 'docs/user-guide/05-capabilities.md')
| -rw-r--r-- | docs/user-guide/05-capabilities.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user-guide/05-capabilities.md b/docs/user-guide/05-capabilities.md index 6426cb37c..b398ba3a5 100644 --- a/docs/user-guide/05-capabilities.md +++ b/docs/user-guide/05-capabilities.md @@ -12,7 +12,7 @@ Slang exposes operations from all target platforms to allow the user to take max A consequence of this approach is that the user is now responsible for maintaining compatibility of their code. For example, if the user writes code that uses a Vulkan extension currently not available on D3D/HLSL, they will get an error when attempting to compile that code to D3D. -To help the user to maintain compatibility of their shader code on platforms matter to their applications, Slang's type system can now infer and enforce capability requirements +To help the user to maintain compatibility of their shader code on platforms that matter to their applications, Slang's type system can now infer and enforce capability requirements to provide assurance that the shader code will be compatible with the specific set of platforms before compiling for that platform. For example, `Texture2D.SampleCmp` is available on D3D and Vulkan, but not available on CUDA. If the user is intended to write cross-platform code that targets CUDA, they will |