TOC fix

Author: jankrassnigg

pages/docs/effects/decals/decals-overview.md

@@ -6,7 +6,7 @@ Decals are a way to project textures onto surfaces in your scene. They're useful
 
 EZ provides different types of decals for various use cases:
 
-* **[Decals](decals.md)** - Standard projected decals
+* **[Decals](projected-decals.md)** - Standard projected decals
 * **[Mesh Decals](mesh-decals.md)** - Decals that use mesh geometry
 
 ## See Also

pages/docs/effects/decals/mesh-decals.md

@@ -4,7 +4,7 @@
 
 ![Mesh Decals](../media/mesh-decals.jpg)
 
-Unlike regular [decals](decals.md) which project a texture onto geometry, mesh decals:
+Unlike regular [decals](projected-decals.md) which project a texture onto geometry, mesh decals:
 
 * Follow the mesh geometry exactly without projection distortion
 * Support multiple decal textures per mesh (up to 8 slots)
@@ -43,5 +43,5 @@ The `DepthBias` material parameter (default: 1.0) controls how far the decal geo
 
 ## See Also
 
-* [Decals](decals.md)
+* [Projected Decals](projected-decals.md)
 * [Meshes](../../graphics/meshes/meshes-overview.md)

pages/docs/effects/decals/decals.md …/docs/effects/decals/projected-decals.mdpages/docs/effects/decals/decals.md renamed to pages/docs/effects/decals/projected-decals.md pages/docs/effects/decals/decals.md renamed to pages/docs/effects/decals/projected-decals.md

@@ -1,4 +1,4 @@
-# Decals
+# Projected Decals
 
 ![Decals](../media/decals-overview.jpg)
 
@@ -59,10 +59,8 @@ If disabled, the decal will completely overwrite the normal of the underlying ge
 
 **ApplyToDynamic:** By default, decals apply to *static geometry* but not to *dynamic geometry*. If it is desired for a decal to be projected onto a dynamic object, this property should be used to select exactly to which dynamic object the decal should be applied to. Note that decals can only be applied to a single dynamic game object. If the selected object turns out to be *static*, though, the decal will be invisible.
 
-## Mesh Decals
-
-In addition to projected decals, there are also [mesh decals](mesh-decals.md). Mesh decals map decal textures directly onto mesh geometry rather than projecting them. This is useful when decals need to follow the mesh topology precisely without projection distortion.
-
 ## See Also
 
+* [Decals Overview](decals-overview.md)
+* [Mesh Decals](mesh-decals.md)
 * [Particle Effects](../particle-effects/particle-effects-overview.md)

pages/docs/effects/decals/toc.txt

@@ -0,0 +1,3 @@
+decals-overview.md
+projected-decals.md
+mesh-decals.md

pages/docs/effects/particle-effects/particle-effect-component.md

@@ -17,7 +17,7 @@ The *particle effect component* is used to instantiate and control particle effe
 
 **RandomSeed:** If set to zero, the effect will use random values and look slightly different every time. If set to any other value, the effect will look identical every time it is restarted.
 
-**SpawnDirection:** The direction along which the effect should be spawned (in local space). The default is 'positive Z' which means 'up', but to align this with other things, such as [decals](../decals/decals.md) or [lights](../../graphics/lighting/lighting-overview.md), it can be useful to use a different axis. Note that interactions with [surfaces](../../materials/surfaces.md) (e.g. an impact effect that is spawned when a bullet hits a wall) are always spawned such that the spawned prefab's positive X axis aligns with the surface interaction axis (e.g. it's normal). For such cases it therefore makes sense to spawn a particle effect along 'positive X'.
+**SpawnDirection:** The direction along which the effect should be spawned (in local space). The default is 'positive Z' which means 'up', but to align this with other things, such as [decals](../decals/projected-decals.md) or [lights](../../graphics/lighting/lighting-overview.md), it can be useful to use a different axis. Note that interactions with [surfaces](../../materials/surfaces.md) (e.g. an impact effect that is spawned when a bullet hits a wall) are always spawned such that the spawned prefab's positive X axis aligns with the surface interaction axis (e.g. it's normal). For such cases it therefore makes sense to spawn a particle effect along 'positive X'.
 
 **IgnoreOwnerRotation:** By default the *SpawnDirection* is local to the owning game object, meaning when the owning object is tipped over, the effect will also spawn sideways. For some effects it can be desireable to ignore the rotation of the owner, and always spawn in *global space*, though. For instance, when an effect has a strong directionality, such as debris flying away in a cone, it may look best when it is always spawned upwards.
 

pages/docs/materials/surfaces.md

@@ -38,7 +38,7 @@ Interactions are triggered by different systems. The [physics engine](../physics
 
 ### Spawning Prefabs
 
-All surface interactions ultimately spawn [prefabs](../prefabs/prefabs-overview.md). So if you want to have different footstep sounds when walking over stone, sand and mud, you need three prefabs, each playing a different sound. However, since they are prefabs, your creativity is not limited to playing a sound. Your "sand footstep effect" may contain spawning a small dust [particle effect](../effects/particle-effects/particle-effects-overview.md). And the "mud footstep effect" could additionally spawn a footprint [decal](../effects/decals/decals.md).
+All surface interactions ultimately spawn [prefabs](../prefabs/prefabs-overview.md). So if you want to have different footstep sounds when walking over stone, sand and mud, you need three prefabs, each playing a different sound. However, since they are prefabs, your creativity is not limited to playing a sound. Your "sand footstep effect" may contain spawning a small dust [particle effect](../effects/particle-effects/particle-effects-overview.md). And the "mud footstep effect" could additionally spawn a footprint [decal](../effects/decals/projected-decals.md).
 
 The following options allow you to adjust how prefabs are spawned:
 

pages/docs/scenes/scene-editing.md

@@ -102,7 +102,7 @@ Once your scene starts to become bigger, you may want to use [scene layers](scen
 
 ## Next Steps
 
-Now that you are familiar with how to create, edit and test a basic scene, there are many other things to explore. [Decals](../effects/decals/decals.md) and [particle effects](../effects/particle-effects/particle-effects-overview.md) can make your scene more interesting. Proper [sounds](../sound/sound-overview.md) add a lot of atmosphere. And finally, by writing [custom code](../custom-code/custom-code-overview.md), either in C++ or through scripting, you will bring your own game idea to life.
+Now that you are familiar with how to create, edit and test a basic scene, there are many other things to explore. [Decals](../effects/decals/projected-decals.md) and [particle effects](../effects/particle-effects/particle-effects-overview.md) can make your scene more interesting. Proper [sounds](../sound/sound-overview.md) add a lot of atmosphere. And finally, by writing [custom code](../custom-code/custom-code-overview.md), either in C++ or through scripting, you will bring your own game idea to life.
 
 ## See Also
 

pages/docs/toc.md

@@ -140,7 +140,7 @@
 ## [Cloth Sheet Component](effects/cloth-sheet-component.md)
 ## Decals
 ### [Decals Overview](effects/decals/decals-overview.md)
-### [Decals](effects/decals/decals.md)
+### [Projected Decals](effects/decals/projected-decals.md)
 ### [Mesh Decals](effects/decals/mesh-decals.md)
 ## [Fog](effects/fog.md)
 ## [Lensflare Component](effects/lensflare-component.md)

pages/docs/toc.txt

@@ -26,7 +26,7 @@ runtime
 ---
 debugging
 performance
-Shipping
+shipping
 tools
 ---
 appendix