Acrolinx feedback

Author: kegodin

articles/cognitive-services/Acoustics/unity-baking.md

@@ -202,7 +202,7 @@ You can bake your scene on your own PC. This can be useful for experimenting wit
 
 ### Minimum hardware requirements
 * An x86-64 processor with at least 8 cores and 32 GB of RAM
-* [Hyper-V enabled](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) to run Docker
+* [Hyper-V enabled](https://docs.microsoft.com/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v) to run Docker
 
 As an example, in our testing on an 8 core machine with Intel Xeon E5-1660 @ 3 GHz and 32 GB RAM -
 * A small scene with 100 probes can take about 2 hours for a coarse bake or 32 hours for a fine bake.

articles/cognitive-services/Acoustics/unity-quickstart.md

@@ -36,7 +36,7 @@ Import the sample package to a new Unity project.
 
 * Click on the **Import** button to integrate the Unity package into your project  
 
-    ![Screenshot of Unity Import Package diaglog](media/import-dialog.png)  
+    ![Screenshot of Unity Import Package dialog](media/import-dialog.png)  
 
 If you're importing the package into an existing project, see [Unity integration](unity-integration.md) for additional steps and notes.
 

articles/cognitive-services/Acoustics/unreal-integration.md

@@ -117,7 +117,7 @@ An example Wwise project is included with the samples download. We recommend loo
 
 * Then go to the Mixer Plug-in tab and add the project acoustics mixer plug-in to the bus
 
-    ![Screenshow of Wwise bus showing how to add the Project Acoustics Mixer Plugin](media/add-mixer-plugin.png)
+    ![Screenshot of Wwise bus showing how to add the Project Acoustics Mixer Plugin](media/add-mixer-plugin.png)
 
 ### Actor-mixer hierarchy setup
 * For performance reasons, Project Acoustics applies audio DSP to all sources simultaneously. This requires the plugin to operate as a mixer plugin. Wwise requires mixer plugins to be on the output bus, though the output bus usually carries the dry output signal. Project Acoustics requires the dry signal be routed through aux busses while the wet signal is carried on the `Project Acoustics Bus`. The following process supports gradual migration to this signal flow.
@@ -159,7 +159,7 @@ Unfortunately, other object-based spatializer plugins can't be supported at this
 
 * Now assign the baked acoustic data asset to the Acoustics Data slot on the Acoustics Space actor. Your scene now has acoustics!
 
-    ![Screenshot of Unreal editor s howing acoustics Asset assignment](media/acoustics-asset-assign.png)
+    ![Screenshot of Unreal editor showing acoustics Asset assignment](media/acoustics-asset-assign.png)
 
 * Now add an empty actor and do the following:
 

articles/cognitive-services/Acoustics/what-is-acoustics.md

@@ -37,14 +37,14 @@ Project Acoustics' key innovation is to couple acoustic simulation with traditio
 * **Bake:** An analysis step is run locally, which does voxelization and other geometric analysis on the scene based on selections above. Results are visualized in editor to verify scene setup. On bake submission, voxel data is sent off to Azure and you get back an acoustics game asset.
 * **Runtime:** Load the asset into your level, and you're ready to listen to acoustics in your level. Design the acoustics live in editor using granular per-source controls. The controls can also be driven from level scripting.
 
-## Runtime Platforms
+## Runtime platforms
 The Project Acoustics runtime plugins can currently be deployed to the following platforms:
 * Windows
 * MacOS
 * Android
 * Xbox One
 
-## Editor Platforms
+## Editor platforms
 The Project Acoustics editor plugin is available for the following platforms:
 * Windows
 * MacOS (Unity only)