Improve navigation (#5)

Author: JoseEmilio-ARM

en/18_ray_tracing.adoc

@@ -0,0 +1,3 @@
+== SIGGRAPH 2025: Hands-on Vulkan Ray Tracing with Dynamic Rendering
+
+Find the course link:courses/18_Ray_tracing/00_Overview.adoc[here]

en/courses/18_Ray_tracing/00_Overview.adoc

@@ -4,6 +4,8 @@
 
 Welcome! In this series, we enhance a Vulkan renderer with ray tracing features to implement real-time pixel-perfect shadows (with and without transparency) and a bonus reflection effect. You will work with provided scaffolded code (based on the Vulkan Tutorial) and fill in key shader functions following step-by-step instructions.
 
+Slides available link:Vulkan%20Ray%20Tracing%20With%20Dynamic%20Rendering.pdf[here].
+
 By the end, you'll learn how to:
 
 - Use Vulkan dynamic rendering (no pre-defined render passes) and verify it with RenderDoc.

en/courses/18_Ray_tracing/README.adoc

@@ -6,17 +6,20 @@ Official event page:
 - https://www.khronos.org/events/siggraph-2025#vulkan-ray-tracing-lab
 
 Session details (from the SIGGRAPH listing):
+
 - Title: Hands-on Vulkan Ray Tracing With Dynamic Rendering
 - When: Thursday, August 14 — 11:45am–1:15pm (SIGGRAPH Lab)
 - Where: Vancouver Convention Centre, West Building, Exhibit Hall B
 - Notes: A SIGGRAPH registration is required to attend. Limited seating; first-come, first-served.
 
 Authors / Presenters:
+
 - Jose Emilio Muñoz Lopez (Arm)
 - Steve Winston (Holochip)
 
 Attribution:
+
 - The instructional flow and lab content here are adapted from the above SIGGRAPH 2025 lab. Please cite the authors above when referencing or reusing this material.
-- Portions of the code and guidance build upon the open-source Khronos Vulkan Tutorial and use helper libraries vk-bootstrap and Vulkan-RAII, as referenced in the lab description.
+- Portions of the code and guidance build upon the open-source Khronos Vulkan Tutorial and use helper libraries like Vulkan-RAII, as referenced in the lab description.
 
 If you notice any discrepancy with the official SIGGRAPH listing (title, time, location, or presenters), please open an issue so we can correct the attribution promptly.