Update 09-reflection.md (#5886)

docs/user-guide/09-reflection.md

@@ -14,7 +14,7 @@ Our goals in this chapter are to:
 * Provide an underlying mental model for how Slang's reflection information represents the structure of a program
 
 We will describe the structure of a program that traverses all of the parameters of a shader program and prints information (including binding locations) for them.
-The code shown here is derived from the [`reflection-api`](https://github.com/shader-slang/slang/tree/master/examples/reflection-api) example that is included in the Slang repository.
+The code shown here is derived from the [reflection-api](https://github.com/shader-slang/slang/tree/master/examples/reflection-api) example that is included in the Slang repository.
 Readers may find it helpful to follow along with that code, to see a more complete picture of what is presented here.
 
 Compiling a Program
@@ -1630,4 +1630,4 @@ Conclusion
 ----------
 
 At this point we have provided a comprehensive example of how to robustly traverse the information provided by the Slang reflection API to get a complete picture of the shader parameters of a program, and what target-specific locations they were bound to.
-We hope that along the way we have also imparted some key parts of the mental model that exists behind the reflection API and its representations.
+We hope that along the way we have also imparted some key parts of the mental model that exists behind the reflection API and its representations.