summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorElie Michel <eliemichel@users.noreply.github.com>2024-11-25 05:50:50 +0100
committerGitHub <noreply@github.com>2024-11-25 12:50:50 +0800
commite30f0537126f611b7cad81404f9d0c19c6b57ddf (patch)
treec3d51ac3a3166e337ed3a9956726a3740763d6cb /docs
parentdacfa159acf00e25444ce73bbe53252a5983762c (diff)
Fix broken link in 09-reflection.md (#5655)
* Fix broken link in 09-reflection.md * Fix another link on 08-compiling.md --------- Co-authored-by: Ellie Hermaszewska <ellieh@nvidia.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/user-guide/08-compiling.md2
-rw-r--r--docs/user-guide/09-reflection.md4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/user-guide/08-compiling.md b/docs/user-guide/08-compiling.md
index 6f60ef6f8..23a33d914 100644
--- a/docs/user-guide/08-compiling.md
+++ b/docs/user-guide/08-compiling.md
@@ -829,7 +829,7 @@ The details of how Slang computes layout, what guarantees it makes, and how to i
Because the layout computed for shader parameters may depend on the compilation target, the `getLayout()` method actually takes a `targetIndex` parameter that is the zero-based index of the target for which layout information is being queried.
This parameter defaults to zero as a convenience for the common case where applications use only a single compilation target at runtime.
-See [Using the Reflection API] chapter for more details on the reflection API.
+See [Using the Reflection API](reflection) chapter for more details on the reflection API.
### Linking
diff --git a/docs/user-guide/09-reflection.md b/docs/user-guide/09-reflection.md
index 0c9311212..ff874fb5f 100644
--- a/docs/user-guide/09-reflection.md
+++ b/docs/user-guide/09-reflection.md
@@ -13,7 +13,7 @@ The Slang API allows layout to be queried on any program object represented by a
slang::ProgramLayout* layout = program->getLayout();
```
-Please see the [Compiling Code with Slang](/user-guide/compiling) section on creating program objects.
+Please see the [Compiling Code with Slang](compiling) section on creating program objects.
Note that just as with output code, the reflection object (and all other objects queried from it) is guaranteed to live as long as the request is alive, but no longer.
Unlike the other data, there is no easy way to save the reflection data for later user (we do not currently implement serialization for reflection data).
@@ -224,4 +224,4 @@ unsigned int attribCount = funcReflection->getUserAttributeCount();
slang::UserAttribute* attrib = funcReflection->getUserAttributeByIndex(0);
const char* attribName = attrib->getName();
-``` \ No newline at end of file
+```