Merge pull request #6901 from keveleigh/header-casing-4

Header capitalization phase 4

Author: David Kline

Documentation/README_NearMenu.md

@@ -1,4 +1,4 @@
-# Near Menu
+# Near menu
 
 ![Near Menu](../Documentation/Images/NearMenu/MRTK_UX_NearMenu.png)
 

Documentation/README_ObjectCollection.md

@@ -21,11 +21,11 @@ To create a collection, create an empty GameObject and assign one of the Object
 
 ![Object collection](../Documentation/Images/ObjectCollection/MRTK_ObjectCollectionScript.png)
 
-## `GridObjectCollection` Content Alignment
+## `GridObjectCollection` content alignment
 
 The content in a GridObjectCollection can be aligned so that the parent object is anchored to the top/middle/bottom and left/center/right of the collection. Use the **anchor** property to specify content alignment.
 
-## `GridObjectCollection` Layout Order
+## `GridObjectCollection` layout order
 
 Use the **Layout** field to specify the row / column order that children are laid out:
 

Documentation/README_Slate.md

@@ -16,7 +16,7 @@ A slate control is composed of the following elements:
 
 <img src="../Documentation/Images/Slate/MRTK_Slate_Structure.png" width="650">
 
-## Bounding Box
+## Bounding box
 
 A slate control contains a bounding box script for scaling and rotating. For more information on bounding box, please see the [Bounding box](README_BoundingBox.md) page.
 

Documentation/README_Sliders.md

@@ -9,7 +9,7 @@ Sliders are UI components that allow you to continuously change a value by movin
 You can find examples in the **SliderExample** scene under:
 [MixedRealityToolkit.Examples/Demos/UX/Slider/Scenes/](/Assets/MixedRealityToolkit.Examples/Demos/UX/Slider/Scenes)
 
-## How to use Sliders
+## How to use sliders
 
 Drag and drop the **PinchSlider** prefab into the scene hierarchy. If you want to modify or create your own slider, remember to do the following:
 
@@ -23,7 +23,7 @@ We also recommend using the following hierarchy
   - TrackVisuals - Containing the track and any other visuals
   - OtherVisuals - Containing any other visuals
 
-## Slider Events
+## Slider events
 
 Sliders expose the following events:
 
@@ -33,7 +33,7 @@ Sliders expose the following events:
 - OnHoverEntered - Called when the user's hand / controller hovers over the slider, using either near or far interaction.
 - OnHoverExited - Called when the user's hand / controller is no longer near the slider.
 
-## Configuring Slider Bound and Axis
+## Configuring slider bound and axis
 
 You can directly move the starting and end points of the slider by moving the handles in the Scene:
 

Documentation/README_Solver.md

@@ -49,7 +49,7 @@ The *Tracked Target Type* property of the [`SolverHandler`](xref:Microsoft.Mixed
 ![Solver](Images/Solver/TrackedObjectType-Example.gif)  
 *Example of various properties associated with each TrackedTargetType*
 
-## How to chain Solvers
+## How to chain solvers
 
 It is possible to add multiple `Solver` components to the same GameObject thus chaining their algorithms. The `SolverHandler` components handles updating all solvers on the same GameObject. By default the `SolverHandler` calls `GetComponents<Solver>()` on Start which will return the Solvers in the order that they appear in the inspector.
 
@@ -58,7 +58,7 @@ Furthermore, setting the *Updated Linked Transform* property to true will instru
 > [!NOTE]
 > Developers can modify the order of execution of Solvers by setting the `SolverHandler.Solvers` property directly.
 
-## How to create a new Solver
+## How to create a new solver
 
 All solvers must inherit from the abstract base class, [`Solver`](xref:Microsoft.MixedReality.Toolkit.Utilities.Solvers.Solver). The primary requirements of a Solver extension involves overriding the `SolverUpdate` method. In this method, developers should update the inherited `GoalPosition`, `GoalRotation` and `GoalScale` properties to the desired values. Furthermore, it is generally valuable to leverage `SolverHandler.TransformTarget` as the frame of reference desired by the consumer.
 
@@ -85,7 +85,7 @@ public class InFront : Solver
 
 ## Solver implementation guides
 
-### Common Solver properties
+### Common solver properties
 
 Every Solver component has a core-set of identical properties that control the core Solver behavior.
 
@@ -159,7 +159,7 @@ Conversely, a [`SurfaceMagnetism`](xref:Microsoft.MixedReality.Toolkit.Utilities
 
 Finally, surfaces farther than the `MaxRaycastDistance` property setting will be ignored by the `SurfaceMagnetism` raycasts.
 
-### Hand Menu with HandConstraint and HandConstraintPalmUp
+### Hand menu with HandConstraint and HandConstraintPalmUp
 
 ![Hand Menu UX Example](Images/Solver/MRTK_UX_HandMenu.png)
 
@@ -180,11 +180,11 @@ Please see the tool tips available for each [`HandConstraint`](xref:Microsoft.Mi
     * *OnFirstHandDetected*: occurs when the hand tracking state changes from no hands in view, to the first hand in view.
     * *OnLastHandLost*: occurs when the hand tracking state changes from at least one hand in view, to no hands in view.
 
-## Experimental Solvers
+## Experimental solvers
 
 These solvers are available in MRTK but are currently experimental. Their APIs and functionality are subject to change. Furthermore, their robustness and quality may be lower than standard features.
 
-### Directional Indicator
+### Directional indicator
 
 The [`DirectionalIndicator`](xref:Microsoft.MixedReality.Toolkit.Experimental.Utilities.DirectionalIndicator) class is a tag-along component that orients itself to the direction of a desired point in space.
 

Documentation/README_TextPrefab.md

@@ -1,4 +1,4 @@
-# Text Prefab
+# Text prefab
 These prefabs are optimized for the rendering quality in Windows Mixed Reality. For more information, please read the guideline [Text in Unity](https://docs.microsoft.com/windows/mixed-reality/text-in-unity) on Microsoft Windows Dev Center.
 
 #### [3DTextPrefab.prefab](https://github.com/microsoft/MixedRealityToolkit-Unity/tree/mrtk_development/Assets/MixedRealityToolkit.SDK/StandardAssets/Prefabs/Text)

Documentation/ReleaseNotes.md

@@ -1,4 +1,4 @@
-# Microsoft Mixed Reality Toolkit Release Notes
+# Microsoft Mixed Reality Toolkit release notes
 
 - [Version 2.2.0](#version-220)
 - [Version 2.1.0](#version-210)

Documentation/Rendering/MaterialInstance.md

@@ -1,4 +1,4 @@
-# Material Instance
+# Material instance
 
 The [`MaterialInstance`](xref:Microsoft.MixedReality.Toolkit.Rendering.MaterialInstance) behavior aides in tracking instance material lifetime and automatically destroys instanced materials for the user. This utility component can be used as a replacement to [Renderer.material]("https://docs.unity3d.com/ScriptReference/Renderer-material.html") or 
 [Renderer.materials]("https://docs.unity3d.com/ScriptReference/Renderer-materials.html").
@@ -92,6 +92,6 @@ public class MyBehaviour : MonoBehaviour,  IMaterialInstanceOwner
 
 For more information please see the example usage demonstrated within the [`ClippingPrimitive`](xref:Microsoft.MixedReality.Toolkit.Utilities.ClippingPrimitive) behavior.
 
-## See Also
+## See also
 
 * [MRTK Standard Shader](../README_MRTKStandardShader.md)

Documentation/SceneSystem/SceneSystemContentLoading.md

@@ -1,8 +1,8 @@
-# Content Scene Loading
+# Content scene loading
 
-All content load operations are asynchronous, and by default all content loading is additive. Manager and lighting scenes are never affected by content loading operations. For information about monitoring load progress and scene activation, see [Monitoring Content Loading.](SceneSystemLoadProgress.md)
+All content load operations are asynchronous, and by default all content loading is additive. Manager and lighting scenes are never affected by content loading operations. For information about monitoring load progress and scene activation, see [Monitoring Content Loading](SceneSystemLoadProgress.md).
 
-## Loading Content
+## Loading content
 
 To load content scenes use the `LoadContent` method:
 
@@ -16,7 +16,7 @@ await sceneSystem.LoadContent("MyContentScene");
 await sceneSystem.LoadContent(new string[] { "MyContentScene1", "MyContentScene2", "MyContentScene3" });
 ```
 
-## Single Scene Loading
+## Single scene loading
 
 The equivalent of a single scene load can be achieved via the optional `mode` argument. `LoadSceneMode.Single` will first unload all loaded content scenes before proceeding with the load.
 
@@ -33,7 +33,7 @@ await sceneSystem.LoadContent("ContentScene3");
 await sceneSystem.LoadContent("SingleContentScene", LoadSceneMode.Single);
 ```
 
-## Next / Previous Scene Loading
+## Next / previous scene loading
 
 Content can be singly loaded in order of build index. This is useful for showcase applications that take users through a set of demonstration scenes one-by-one.
 
@@ -73,7 +73,7 @@ if (prevSceneRequested)
 }
 ```
 
-## Loading by Tag
+## Loading by tag
 
 ![MRTK_SceneSystemLoadingByTag](../Images/SceneSystem/MRTK_SceneSystemLoadingByTag.png)
 
@@ -124,7 +124,7 @@ Trees | Vegetation | •
 
 ---
 
-## Editor Behavior
+## Editor behavior
 
 You can perform all these operations in editor and in play mode by using the Scene System's [service inspector.](../MixedRealityConfigurationGuide.md#editor-utilities) In edit mode scene loads will be instantaneous, while in play mode you can observe loading progress and use [activation tokens.](SceneSystemLoadProgress.md)
 

Documentation/SceneSystem/SceneSystemLightingScenes.md

@@ -1,4 +1,4 @@
-# Lighting Scene Operations
+# Lighting scene operations
 
 The default lighting scene defined in your profile is loaded on startup. That lighting scene remains loaded until `SetLightingScene` is called.
 
@@ -8,7 +8,7 @@ IMixedRealitySceneSystem sceneSystem = MixedRealityToolkit.Instance.GetService<I
 sceneSystem.SetLightingScene("MorningLighting");
 ```
 
-## Lighting Setting Transitions
+## Lighting setting transitions
 
 `transitionType` controls the style of the transition to new lighting scene.