switch from link to xref.

Author: gpx1000

en/Building_a_Simple_Engine/Appendix/appendix.adoc

@@ -335,5 +335,5 @@ When designing your engine architecture, consider:
 3. *Team Size and Experience* - More complex architectures may be harder to work with for smaller teams.
 4. *Project Scope* - A small project may not need the complexity of a full ECS.
 
-link:../Engine_Architecture/02_architectural_patterns.adoc[Back to Architectural Patterns]
-link:../Engine_Architecture/05_rendering_pipeline.adoc[Back to Rendering Pipeline]
+xref:../Engine_Architecture/02_architectural_patterns.adoc[Back to Architectural Patterns]
+xref:../Engine_Architecture/05_rendering_pipeline.adoc[Back to Rendering Pipeline]

en/Building_a_Simple_Engine/Camera_Transformations/01_introduction.adoc

@@ -22,10 +22,10 @@ By the end of this chapter, you'll have a solid understanding of 3D transformati
 Before starting this chapter, you should have completed the main Vulkan tutorial. You should also be familiar with:
 
 * Basic Vulkan concepts:
-** link:../../03_Drawing_a_triangle/03_Drawing/01_Command_buffers.adoc[Command buffers]
-** link:../../03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.adoc[Graphics pipelines]
-* link:../../04_Vertex_buffers/00_Vertex_input_description.adoc[Vertex] and link:../../04_Vertex_buffers/03_Index_buffer.adoc[index buffers]
-* link:../../05_Uniform_buffers/00_Descriptor_set_layout_and_buffer.adoc[Uniform buffers]
+** xref:../../03_Drawing_a_triangle/03_Drawing/01_Command_buffers.adoc[Command buffers]
+** xref:../../03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.adoc[Graphics pipelines]
+* xref:../../04_Vertex_buffers/00_Vertex_input_description.adoc[Vertex] and xref:../../04_Vertex_buffers/03_Index_buffer.adoc[index buffers]
+* xref:../../05_Uniform_buffers/00_Descriptor_set_layout_and_buffer.adoc[Uniform buffers]
 * Basic programming concepts and C++
 
-link:02_math_foundations.adoc[Next: Mathematical Foundations]
+xref:02_math_foundations.adoc[Next: Mathematical Foundations]

en/Building_a_Simple_Engine/Camera_Transformations/04_camera_implementation.adoc

@@ -684,9 +684,9 @@ void gameLoop(float deltaTime) {
 
 [NOTE]
 ====
-For more advanced camera techniques, refer to the Advanced Camera Techniques section in the link:../Appendix/appendix.adoc[Appendix].
+For more advanced camera techniques, refer to the Advanced Camera Techniques section in the xref:../Appendix/appendix.adoc[Appendix].
 ====
 
 In the next section, we'll integrate our camera system with Vulkan to render 3D scenes.
 
-link:05_vulkan_integration.adoc[Next: Vulkan Integration]
+xref:05_vulkan_integration.adoc[Next: Vulkan Integration]

en/Building_a_Simple_Engine/Camera_Transformations/06_conclusion.adoc

@@ -52,4 +52,4 @@ A well-designed camera system is essential for any 3D application. It serves as
 
 Remember that the code provided in this chapter is a starting point. Feel free to modify and extend it to suit your specific needs and application requirements.
 
-link:../Engine_Architecture/conclusion.adoc[Previous: Engine Architecture] | link:../Lighting_Materials/01_introduction.adoc[Next: Lighting & Materials]
+xref:../Engine_Architecture/conclusion.adoc[Previous: Engine Architecture] | xref:../Lighting_Materials/01_introduction.adoc[Next: Lighting & Materials]

en/Building_a_Simple_Engine/Engine_Architecture/02_architectural_patterns.adoc

@@ -23,7 +23,7 @@ image::../../../images/layered_architecture_diagram.png[Layered Architecture Dia
 * Easier to understand and maintain
 * Can replace or modify individual layers without affecting others
 
-For detailed information and implementation examples, see the link:../Appendix/appendix.adoc#layered-architecture[Appendix: Layered Architecture].
+For detailed information and implementation examples, see the xref:../Appendix/appendix.adoc#layered-architecture[Appendix: Layered Architecture].
 
 ==== link:https://www.youtube.com/watch?v=rX0ItVEVjHc[Data-Oriented Design]
 
@@ -36,7 +36,7 @@ image::../../../images/data_oriented_design_diagram.svg[Data-Oriented Design Dia
 * More efficient memory usage
 * Easier to parallelize
 
-For detailed information and implementation examples, see the link:../Appendix/appendix.adoc#data-oriented-design[Appendix: Data-Oriented Design].
+For detailed information and implementation examples, see the xref:../Appendix/appendix.adoc#data-oriented-design[Appendix: Data-Oriented Design].
 
 ==== link:https://gameprogrammingpatterns.com/service-locator.html[Service Locator Pattern]
 
@@ -49,7 +49,7 @@ image::../../../images/service_locator_pattern_diagram.svg[Service Locator Patte
 * Allows for easy service replacement
 * Facilitates testing with mock services
 
-For detailed information and implementation examples, see the link:../Appendix/appendix.adoc#service-locator-pattern[Appendix: Service Locator Pattern].
+For detailed information and implementation examples, see the xref:../Appendix/appendix.adoc#service-locator-pattern[Appendix: Service Locator Pattern].
 
 === link:https://gameprogrammingpatterns.com/component.html[Component-Based Architecture]
 
@@ -164,8 +164,8 @@ While other architectural patterns have their merits, component-based architectu
 
 === Conclusion
 
-We've provided a brief overview of common architectural patterns, with a focus on Component-Based Architecture which we'll use throughout this tutorial. For more detailed information about other architectural patterns, including implementation examples and comparative analysis, see the link:../Appendix/appendix.adoc[Appendix: Detailed Architectural Patterns].
+We've provided a brief overview of common architectural patterns, with a focus on Component-Based Architecture which we'll use throughout this tutorial. For more detailed information about other architectural patterns, including implementation examples and comparative analysis, see the xref:../Appendix/appendix.adoc[Appendix: Detailed Architectural Patterns].
 
 In the next section, we'll dive deeper into component systems and how to implement them effectively in your engine.
 
-link:01_introduction.adoc[Previous: Introduction] | link:03_component_systems.adoc[Next: Component Systems]
+xref:01_introduction.adoc[Previous: Introduction] | xref:03_component_systems.adoc[Next: Component Systems]

en/Building_a_Simple_Engine/Engine_Architecture/05_rendering_pipeline.adoc

@@ -529,10 +529,10 @@ Proper synchronization is crucial in Vulkan because:
 
 The vulkan tutorial includes a more detailed discussion of synchronization, the proper uses of the primitives described above.
 
-* link:../../03_Drawing_a_triangle/03_Drawing/02_Rendering_and_presentation.adoc[Synchronization]
-* link:../../03_Drawing_a_triangle/03_Drawing/03_Frames_in_flight.adoc[Frames In Flight]
-* link:../../11_Compute_Shader.adoc[Compute Shader]
-* link:../../17_Multithreading.adoc[Multithreading]
+* xref:../../03_Drawing_a_triangle/03_Drawing/02_Rendering_and_presentation.adoc[Synchronization]
+* xref:../../03_Drawing_a_triangle/03_Drawing/03_Frames_in_flight.adoc[Frames In Flight]
+* xref:../../11_Compute_Shader.adoc[Compute Shader]
+* xref:../../17_Multithreading.adoc[Multithreading]
 
 
 ===== Pipeline Barriers

en/Building_a_Simple_Engine/Engine_Architecture/conclusion.adoc

@@ -36,7 +36,7 @@ The architectural foundation we've established in this chapter will support ever
 
 Active implementation proves far more valuable than passive reading when learning engine architecture. Build the code examples as you encounter them, but don't stop there—experiment with variations to understand how different approaches affect your engine's behavior. This experimentation develops the intuitive understanding that separates competent engine developers from those who merely copy implementations.
 
-The architectural concepts we've covered provide a foundation, but production engines require additional sophistication. The link:../Appendix/appendix.adoc[Appendix] explores advanced rendering techniques and architectural patterns that build on these fundamentals, helping you understand how simple patterns scale to handle complex real-world requirements.
+The architectural concepts we've covered provide a foundation, but production engines require additional sophistication. The xref:../Appendix/appendix.adoc[Appendix] explores advanced rendering techniques and architectural patterns that build on these fundamentals, helping you understand how simple patterns scale to handle complex real-world requirements.
 
 Studying existing open-source engines like link:https://github.com/TheCherno/Hazel[Hazel] or examining the architectural decisions in established frameworks like link:https://github.com/LWJGL/lwjgl3[LWJGL] provides valuable perspective on how these concepts apply in practice. Look for patterns we've discussed and notice how different engines make different trade-offs based on their specific goals and constraints.
 
@@ -50,4 +50,4 @@ Building a rendering engine is a challenging but rewarding endeavor. By applying
 
 Good luck with your engine development journey!
 
-link:06_event_systems.adoc[Previous: Event Systems] | link:../Camera_Transformations/01_introduction.adoc[Next: Camera Transformations]
+xref:06_event_systems.adoc[Previous: Event Systems] | xref:../Camera_Transformations/01_introduction.adoc[Next: Camera Transformations]

en/Building_a_Simple_Engine/Loading_Models/01_introduction.adoc

@@ -22,12 +22,12 @@ Throughout this implementation, we'll structure our code with engine-level think
 
 This chapter builds on the foundation established in the main Vulkan tutorial, particularly Chapter 16 (Multiple Objects), as we'll extend those concepts to handle more complex scene organization and asset management. The multiple objects chapter introduced the basic concepts of rendering different geometry, which we'll now scale up to handle complete 3D models with materials and animations.
 
-You'll need solid familiarity with core Vulkan concepts that form the backbone of our model loading system. link:../../03_Drawing_a_triangle/03_Drawing/01_Command_buffers.adoc[Command buffers] become more complex when handling multiple models with different materials, as we'll need to manage descriptor sets and push constants efficiently. Understanding link:../../03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.adoc[graphics pipelines] is crucial since different materials might require different pipeline configurations.
+You'll need solid familiarity with core Vulkan concepts that form the backbone of our model loading system. xref:../../03_Drawing_a_triangle/03_Drawing/01_Command_buffers.adoc[Command buffers] become more complex when handling multiple models with different materials, as we'll need to manage descriptor sets and push constants efficiently. Understanding xref:../../03_Drawing_a_triangle/02_Graphics_pipeline_basics/00_Introduction.adoc[graphics pipelines] is crucial since different materials might require different pipeline configurations.
 
-Experience with link:../../04_Vertex_buffers/00_Vertex_input_description.adoc[vertex] and link:../../04_Vertex_buffers/03_Index_buffer.adoc[index buffers] translates directly to model loading, where glTF files contain vertex data in specific formats that we'll need to parse and upload to GPU buffers. link:../../05_Uniform_buffers/00_Descriptor_set_layout_and_buffer.adoc[Uniform buffers] knowledge becomes essential as we'll use them for transformation matrices, lighting information, and material properties.
+Experience with xref:../../04_Vertex_buffers/00_Vertex_input_description.adoc[vertex] and xref:../../04_Vertex_buffers/03_Index_buffer.adoc[index buffers] translates directly to model loading, where glTF files contain vertex data in specific formats that we'll need to parse and upload to GPU buffers. xref:../../05_Uniform_buffers/00_Descriptor_set_layout_and_buffer.adoc[Uniform buffers] knowledge becomes essential as we'll use them for transformation matrices, lighting information, and material properties.
 
-link:../../06_Texture_mapping/00_Images.adoc[Texture mapping] skills are particularly important since glTF models often include multiple textures per material (diffuse, normal, metallic-roughness, etc.), and we'll need to load and bind these textures efficiently.
+xref:../../06_Texture_mapping/00_Images.adoc[Texture mapping] skills are particularly important since glTF models often include multiple textures per material (diffuse, normal, metallic-roughness, etc.), and we'll need to load and bind these textures efficiently.
 
-Finally, basic 3D math understanding (matrices, vectors, quaternions) is crucial for handling model transformations, animations, and scene hierarchies. If you need a refresher, see the link:../../Building_a_Simple_Engine/Camera_Transformations/02_math_foundations.adoc[Camera Transformations chapter] for detailed coverage of these mathematical concepts.
+Finally, basic 3D math understanding (matrices, vectors, quaternions) is crucial for handling model transformations, animations, and scene hierarchies. If you need a refresher, see the xref:../../Building_a_Simple_Engine/Camera_Transformations/02_math_foundations.adoc[Camera Transformations chapter] for detailed coverage of these mathematical concepts.
 
-link:../GUI/06_conclusion.adoc[Previous: GUI] | link:02_project_setup.adoc[Next: Setting Up the Project]
+xref:../GUI/06_conclusion.adoc[Previous: GUI] | xref:02_project_setup.adoc[Next: Setting Up the Project]

en/Building_a_Simple_Engine/Loading_Models/05_pbr_rendering.adoc

@@ -6,7 +6,7 @@
 
 === Building on PBR Knowledge
 
-In the link:../Lighting_Materials/01_introduction.adoc[Lighting & Materials chapter], we explored the fundamentals of Physically Based Rendering (PBR), including its core principles, the BRDF, and material properties. Now, we'll apply that knowledge to implement a PBR pipeline for the glTF models we've loaded.
+In the xref:../Lighting_Materials/01_introduction.adoc[Lighting & Materials chapter], we explored the fundamentals of Physically Based Rendering (PBR), including its core principles, the BRDF, and material properties. Now, we'll apply that knowledge to implement a PBR pipeline for the glTF models we've loaded.
 
 As we learned in the link:../../15_GLTF_KTX2_Migration.html[glTF and KTX2 Migration chapter], glTF uses PBR with the metallic-roughness workflow for its material system. This aligns perfectly with the PBR concepts we've already covered, making it straightforward to render our glTF models with physically accurate lighting.
 
@@ -61,7 +61,7 @@ This uniform buffer includes:
 
 [NOTE]
 ====
-We introduced push constants earlier in link:../Lighting_Materials/03_push_constants.adoc[push constants]; here we focus on how the same mechanism carries glTF metallic‑roughness material knobs efficiently per draw.
+We introduced push constants earlier in xref:../Lighting_Materials/03_push_constants.adoc[push constants]; here we focus on how the same mechanism carries glTF metallic‑roughness material knobs efficiently per draw.
 ====
 
 We'll use link:https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#descriptorsets-pushconstant[push constants] to pass material properties to the shader:
@@ -571,4 +571,4 @@ In the next chapter, we'll explore how to render multiple objects with different
 
 If you want to dive deeper into lighting and materials, refer back to the Lighting & Materials chapter, where we explored the theory behind PBR in detail.
 
-link:04_loading_gltf.adoc[Previous: Loading a glTF Model] | link:06_multiple_objects.adoc[Next: Rendering Multiple Objects]
+xref:04_loading_gltf.adoc[Previous: Loading a glTF Model] | xref:06_multiple_objects.adoc[Next: Rendering Multiple Objects]

en/Building_a_Simple_Engine/Mobile_Development/06_conclusion.adoc

@@ -266,4 +266,4 @@ link:../../attachments/simple_engine/37_mobile_optimizations.cpp[Mobile Optimiza
 link:../../attachments/simple_engine/38_tbr_optimizations.cpp[TBR Optimizations C{pp} code]
 link:../../attachments/simple_engine/39_mobile_extensions.cpp[Mobile Extensions C{pp} code]
 
-link:05_vulkan_extensions.adoc[Previous: Vulkan Extensions for Mobile] | link:../index.html[Back to Building a Simple Engine]
+xref:05_vulkan_extensions.adoc[Previous: Vulkan Extensions for Mobile] | link:../index.html[Back to Building a Simple Engine]