From 8e6af6259bd1dd47d81c36f0562ff362ca5d42c3 Mon Sep 17 00:00:00 2001 From: Gangzheng Tong Date: Fri, 11 Apr 2025 15:34:07 -0700 Subject: 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 --- docs/user-guide/05-capabilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/user-guide/05-capabilities.md') 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 -- cgit v1.2.3