Add missing spaces to # in md files.

Unity-Technologies · Apr 7, 2017 · 9869a62 · 9869a62
1 parent 1d7e431
commit 9869a62
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 10 deletions.
diff --git a/Documentation/ConnectingSurfaces.md b/Documentation/ConnectingSurfaces.md
@@ -1,4 +1,4 @@
-#Connecting NavMesh Surfaces
+# Connecting NavMesh Surfaces
 
 ![Connecting surfaces example](Images/ConnectingSurfaces-Example.png)
 

diff --git a/Documentation/NavMeshLink.md b/Documentation/NavMeshLink.md
@@ -1,4 +1,4 @@
-#NavMeshLink
+# NavMeshLink
 
 ![NavMeshLink example](Images/NavMeshLink-Example.png)
 

diff --git a/Documentation/NavMeshModifier.md b/Documentation/NavMeshModifier.md
@@ -1,4 +1,4 @@
-#NavMeshModifier
+# NavMeshModifier
 
 ![NavMeshModifier example](Images/NavMeshModifier-Example.png)
 
@@ -10,7 +10,7 @@ The NavMesh Modifier affects the NavMesh generation process, this means the NavM
 
 Note: This component is a replacement for the old setting which could be enabled from the Navigation window Objects tab as well as the static flags dropdown on the GameObject. This component is available for baking at runtime, whereas the static flags are available in the editor only.
 
-##Parameters
+## Parameters
 * Ignore From Build – when checked, the object and all if its’ children are skipped from the build process.
 * Override Area Type – when checked the area type will be overridden for the game object containing the Modifier and all of it’s children.
 	* Area Type – new area type to apply

diff --git a/Documentation/NavMeshModifierVolume.md b/Documentation/NavMeshModifierVolume.md
@@ -1,4 +1,4 @@
-#NavMeshModifierVolume
+# NavMeshModifierVolume
 
 ![NavMeshModifierVolume example](Images/NavMeshModifierVolume-Example.png)
 

diff --git a/Documentation/NavMeshSurface.md b/Documentation/NavMeshSurface.md
@@ -1,4 +1,4 @@
-#NavMeshSurface
+# NavMeshSurface
 
 ![NavMeshSurface example](Images/NavMeshSurface-Example.png)
 
@@ -8,7 +8,7 @@ The preferred way to use the NavMeshSurface component is to create an empty Game
 
 The NavMeshSurface component can be also added to any game object. This is useful for cases where you want to use the Hierarchy to define which objects contribute to the NavMesh.
 
-##Parameters
+## Parameters
 * Agent Type – the agent type which will use this NavMesh Surface. The agent type is used for bake settings, as well as to match a NavMeshAgent to proper surface during pathfinding.
 * Collect Objects – defines on a high level which objects should be used for baking.
 	* All – use all active objects.
@@ -23,7 +23,7 @@ The main settings for the NavMesh Surface component allow you to filter the inpu
 
 Game Objects which have a NavMesh Agent or NavMesh Obstacle will be excluded from the baking process automatically. They are dynamic users of the navmesh – and hence should not contribute to the navmesh building.
 
-##Advanced Settings
+## Advanced Settings
 
 ![NavMeshSurface advanced](Images/NavMeshSurface-Advanced.png)
 

diff --git a/Documentation/README.md b/Documentation/README.md
@@ -1,4 +1,4 @@
-#High-level NavMesh Building Components
+# High-level NavMesh Building Components
 
 Here we introduce four high level components for the navigation system:
 
@@ -9,7 +9,7 @@ Here we introduce four high level components for the navigation system:
 
 These components comprise the high level controls for building and using NavMeshes at runtime as well as edit time.
 
-##Techniques and Patterns
+## Techniques and Patterns
 * [Connecting NavMesh Surfaces](ConnectingSurfaces.md) using the NavMeshLink compoenent.