diff options
| author | jsmall-nvidia <jsmall@nvidia.com> | 2022-07-28 10:10:59 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-28 10:10:59 -0400 |
| commit | 260fc5fbe58f2cf976d64993054c638769bc280f (patch) | |
| tree | 8bf5fd03bcfc9a47de0c27a5b63f3a485e94a560 | |
| parent | ed37dcbc175d07134cb0493f5e379a19e97c82f5 (diff) | |
Create nvapi-support.md
| -rw-r--r-- | docs/nvapi-support.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/nvapi-support.md b/docs/nvapi-support.md index aa2396b06..7cd6eeb32 100644 --- a/docs/nvapi-support.md +++ b/docs/nvapi-support.md @@ -3,7 +3,7 @@ NVAPI Support Slang provides support for [NVAPI](https://developer.nvidia.com/nvapi) in several ways -* Slang allows the use of NVAPI directly, by the inclusion of the `#include "nvHLSLExtns.h"` header in your Slang code. Doing so will make all the NVAPI functions directly available and usabe within your Slang source code. +* Slang allows the use of NVAPI directly, by the inclusion of the `#include "nvHLSLExtns.h"` header in your Slang code. Doing so will make all the NVAPI functions directly available and usable within your Slang source code. * NVAPI is used to provide features implicitly for certain targets. For example support for [RWByteAddressBuffer atomics](target-compatibility.md) on HLSL based targets is supported currently via NVAPI. * Direct and implicit NVAPI usage can be freely mixed. @@ -82,4 +82,4 @@ Links More details on how this works can be found in the following PR -* [Simplify workflow when using NVAPI #1556](https://github.com/shader-slang/slang/pull/1556)
\ No newline at end of file +* [Simplify workflow when using NVAPI #1556](https://github.com/shader-slang/slang/pull/1556) |