Skip to content

Commit a1f2add

Browse files
authored
Merge pull request #3792 from keveleigh/fix-docs-build
Fix docs build
2 parents eee7de7 + c6b7b7c commit a1f2add

File tree

2 files changed

+14
-14
lines changed

2 files changed

+14
-14
lines changed

Documentation/SpatialAwareness/ConfiguringSpatialAwarenessMeshObserver.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -40,15 +40,15 @@ The observer shape defines the type of volume that the mesh observer will use wh
4040

4141
#### Axis Aligned Cube
4242

43-
An axis aligned cube volume is a rectangular shape that stays aligned with the axes of the world coordinate system, as determened at application startup.
43+
An axis aligned cube volume is a rectangular shape that stays aligned with the axes of the world coordinate system, as determined at application startup.
4444

4545
#### User Aligned Cube
4646

4747
A user aligned cube volume is a rectangular shape that rotates to align with the users local coordinate system.
4848

4949
### Observation Extents
5050

51-
The observation extents define the distance from the observation point that meshes will be observed. When the [Observer Shape](#observer-shape) is set to Sphere, the X value of the extents will be used as the radius of the sphere.
51+
The observation extents define the distance from the observation point that meshes will be observed. When the [Observer Shape](#observer-shape) is set to sphere, the X value of the extents will be used as the radius of the sphere.
5252

5353
## Physics Settings
5454

@@ -64,27 +64,27 @@ Specifies whether or not the mesh observer will recalculate the normals of the m
6464

6565
## Level of Detail Settings
6666

67-
![Mesh Observer Level of Detail Settings](../../External/ReadMeImages/MeshObserverLevelOfDetailSettings.png)
67+
![Mesh Observer Level of Detail Settings](../../External/ReadMeImages/SpatialAwareness/MeshObserverLevelOfDetailSettings.png)
6868

6969
### Level of Detail
7070

7171
Specifies the level of detail (LOD) of the spatial mesh data. Currently defined values are Coarse, Fine and Custom.
7272

73-
The Coarse LOD generally place a smaller impact on application performance and are an excellent choice for navigation and plane finding.
73+
The Coarse LOD generally places a smaller impact on application performance and are an excellent choice for navigation and plane finding.
7474

75-
The Fine LOD generally exact a higher performance impact on application performance and are a great option for occlusion meshes.
75+
The Fine LOD generally exacts a higher performance impact on application performance and are a great option for occlusion meshes.
7676

77-
The Custom LOD require the application to specify the [Triangles / Cubic Meter](#triangles-per-cubic-meter) value and allows applications to tune the accuracy vs. performance impact of the spatial mesh observer.
77+
The Custom LOD requires the application to specify the [Triangles / Cubic Meter](#triangles-per-cubic-meter) value and allows applications to tune the accuracy vs. performance impact of the spatial mesh observer.
7878

79-
> Note: It is not guaranteed that all Triangles/Cubic Meter values are honored by all platforms. Experimentation and profiling is highlu recommended when using a custom LOD.
79+
> Note: It is not guaranteed that all Triangles/Cubic Meter values are honored by all platforms. Experimentation and profiling is highly recommended when using a custom LOD.
8080
8181
### Triangles per Cubic Meter
8282

83-
When using the Custom [Level of Detail](#level-of-detail), specifies the requested value for the triangle density for the spatial mesh.
83+
When using the custom [Level of Detail](#level-of-detail), specifies the requested value for the triangle density for the spatial mesh.
8484

8585
## Display Settings
8686

87-
![Mesh Observer Display Settings](../../External/ReadMeImages/MeshObserverDisplaySettings.png)
87+
![Mesh Observer Display Settings](../../External/ReadMeImages/SpatialAwareness/MeshObserverDisplaySettings.png)
8888

8989
*Mesh Observer Display Settings*
9090

@@ -110,5 +110,5 @@ Indicates the material to be used to cause the spatial mesh to occlude holograms
110110
- [IMixedRealitySpatialAwarenessObserver API documentation](xref:Microsoft.MixedReality.Toolkit.SpatialAwareness.IMixedRealitySpatialAwarenessObserver)
111111
- [IMixedRealitySpatialAwarenessMeshObserver API documentation](xref:Microsoft.MixedReality.Toolkit.SpatialAwareness.IMixedRealitySpatialAwarenessMeshObserver)
112112
- [BaseSpatialObserver API documentation](xref:Microsoft.MixedReality.Toolkit.SpatialAwareness.BaseSpatialObserver)
113-
- [Spatial Awareness System](SpatialAwarenessSystemGettingStarted.md)
113+
- [Spatial Awareness System](SpatialAwarenessGettingStarted.md)
114114
- [Using Spatial Awareness in an Application](../TODO.md)

Documentation/SpatialAwareness/SpatialAwarenessGettingStarted.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ between holograms and the real-world.
1010
Adding support for spatial awareness requires two key components of the Mixed Reality Toolkit: the
1111
spatial awareness system and a supported platform provider.
1212

13-
1. [Enable](enable-spatial-awareness) the spatial awareness system
14-
2. [Register](register-observers) and [configure](configure-observers) one or more spatial observers
15-
3. [Build and deploy](build-and-deploy) to a platform that supports spatial awareness
13+
1. [Enable](#enable-spatial-awareness) the spatial awareness system
14+
2. [Register](#register-observers) and [configure](#configure-observers) one or more spatial observers
15+
3. [Build and deploy](#build-and-deploy) to a platform that supports spatial awareness
1616

1717
### Enable Spatial Awareness
1818

@@ -77,7 +77,7 @@ Once the spatial awareness system is configured with the desired observer(s), th
7777
and deployed to the target platform.
7878

7979
> Some platforms, including Microsoft HoloLens, provide support for remote execution from within Unity.
80-
This feature enables rapid development and testing without requring the build and deploy step. Be sure to do final acceptance testing using an built and deployed version of the application, running
80+
This feature enables rapid development and testing without requiring the build and deploy step. Be sure to do final acceptance testing using an built and deployed version of the application, running
8181

8282

8383
## See Also

0 commit comments

Comments
 (0)