Edits/consistency

devices/hololens/TOC.md

@@ -30,8 +30,8 @@
 # Navigating Windows Holographic
 ## [Start menu and mixed reality home](holographic-home.md)
 ## [Use your voice with HoloLens](hololens-cortana.md)
-## [Find and save files](holographic-data.md)
-## [Create, share, and view photos and video](holographic-photos-and-videos.md)
+## [Find, open, and save files](holographic-data.md)
+## [Create mixed reality photos and videos](holographic-photos-and-videos.md)
 
 # User management and access management
 ## [Manage user identity and sign-in for HoloLens](hololens-identity.md)
@@ -47,7 +47,7 @@
 ## [Connect to Bluetooth and USB-C devices](hololens-connect-devices.md)
 ## [Use the HoloLens (1st gen) clicker](hololens1-clicker.md)
 ## [Connect to a network](hololens-network.md)
-## [Use HoloLens offline](hololens-offline.md)
+## [Manage connection endpoints for HoloLens](hololens-offline.md)
 
 # Hologram optics and placement in space
 ## [Improve visual quality and comfort](hololens-calibration.md)
@@ -58,11 +58,11 @@
 ## [Update HoloLens](hololens-update-hololens.md)
 ## [Restart, reset, or recover HoloLens](hololens-recovery.md)
 ## [Troubleshoot HoloLens issues](hololens-troubleshooting.md)
-## [Known issues](hololens-known-issues.md)
+## [Known issues for HoloLens](hololens-known-issues.md)
 ## [Frequently asked questions](hololens-faq.md)
 ## [Frequently asked security questions](hololens-faq-security.md)
 ## [Status of the HoloLens services](hololens-status.md)
-## [SCEP Whitepaper](scep-whitepaper.md)
+## [SCEP whitepaper](scep-whitepaper.md)
 
 # [HoloLens release notes](hololens-release-notes.md)
 # [Give us feedback](hololens-feedback.md)

devices/hololens/hololens-known-issues.md

@@ -1,5 +1,5 @@
 ---
-title: HoloLens known issues
+title: Known issues for HoloLens
 description: This is the list of known issues that may affect HoloLens developers.
 keywords: troubleshoot, known issue, help
 author: mattzmsft
@@ -13,7 +13,7 @@ appliesto:
 - HoloLens 1
 ---
 
-# HoloLens known issues
+# Known issues for HoloLens
 
 This is the current list of known issues for HoloLens that affect developers. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future HoloLens software updates.
 
@@ -70,7 +70,7 @@ Our team is currently working on a fix. In the meantime, you can use the followi
 
 1. Select **Build** > **Build Solution**.
 1. Open a Command Prompt Window and cd to the folder that contains the compiled .exe file (for example, C:\MyProjects\HoloLensDeploymentFix\bin\Debug)
-1. Run the executable and provide the device's IP address as a command-line argument. (If connected using USB, you can use 127.0.0.1, otherwise use the device’s Wi-Fi IP address.)  For example, "HoloLensDeploymentFix 127.0.0.1"
+1. Run the executable and provide the device's IP address as a command-line argument. (If connected using USB, you can use 127.0.0.1, otherwise use the device's Wi-Fi IP address.)  For example, "HoloLensDeploymentFix 127.0.0.1"
 
 1. After the tool has exited without any messages (this should only take a few seconds), you will now be able to deploy and debug from Visual Studio 2017 or newer.  Continued use of the tool is not necessary.
 
@@ -84,9 +84,9 @@ We will provide further updates as they become available.
 You may experience issues when trying to launch the Microsoft Store and apps on HoloLens. We've determined that the issue occurs when background app updates deploy a newer version of framework packages in specific sequences while one or more of their dependent apps are still running. In this case,  an automatic app update delivered a new version of the .NET Native Framework (version 10.0.25531 to 10.0.27413) caused the apps that are running to not correctly update for all running apps consuming the prior version of the framework.  The flow for framework update is as follows: 
 
 1. The new framework package is downloaded from the store and installed
-1. All apps using the older framework are ‘updated’ to use the newer version
+1. All apps using the older framework are 'updated' to use the newer version
 
-If step 2 is interrupted before completion then any apps for which the newer framework wasn’t registered will fail to launch from the start menu.  We believe any app on HoloLens could be affected by this issue.
+If step 2 is interrupted before completion then any apps for which the newer framework wasn't registered will fail to launch from the start menu.  We believe any app on HoloLens could be affected by this issue.
 
 Some users have reported that closing hung apps and launching other apps such as Feedback Hub, 3D Viewer or Photos resolves the issue for them—however, this does not work 100% of the time.
 
@@ -112,10 +112,10 @@ If you would not like to take the update, we have released a new version of the
 If your device is still unable to load apps, you can sideload a version of the .NET Native Framework and Runtime through the download center by following these steps:
 
 1. Please download [this zip file](https://download.microsoft.com/download/8/5/C/85C23745-794C-419D-B8D7-115FBCCD6DA7/netfx_1.7.zip) from the Microsoft Download Center. Unzipping will produce two files.  Microsoft.NET.Native.Runtime.1.7.appx and Microsoft.NET.Native.Framework.1.7.appx
-1. Please verify that your device is dev unlocked.  If you haven’t done that before the instructions to do that are [here](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
+1. Please verify that your device is dev unlocked.  If you haven't done that before the instructions to do that are [here](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
 1. You then want to get into the Windows Device Portal. Our recommendation is to do this over USB and you would do that by typing http://127.0.0.1:10080 into your browser.
-1. After you have the Windows Device Portal up we need you to “side load” the two files that you downloaded. To do that you need to go down the left side bar until you get to the **Apps** section and select **Apps**.
-1. You will then see a screen that is similar to the below.  You want to go to the section that says **Install App** and browse to where you unzipped those two APPX files. You can only do one at a time, so after you select the first one, then click on “Go” under the Deploy section. Then do this for the second APPX file.
+1. After you have the Windows Device Portal up we need you to "side load" the two files that you downloaded. To do that you need to go down the left side bar until you get to the **Apps** section and select **Apps**.
+1. You will then see a screen that is similar to the below.  You want to go to the section that says **Install App** and browse to where you unzipped those two APPX files. You can only do one at a time, so after you select the first one, then click on "Go" under the Deploy section. Then do this for the second APPX file.
 
    ![Windows Device Portal to Install Side-Loaded app](images/20190322-DevicePortal.png)
 1. At this point we believe your applications should start working again and that you can also get to the Store.

devices/hololens/hololens-offline.md

@@ -5,9 +5,9 @@ keywords: hololens, offline, OOBE
 audience: ITPro
 ms.date: 07/01/2019
 ms.assetid: b86f603c-d25f-409b-b055-4bbc6edcd301
-author: v-miegge
-ms.author: v-miegge
-manager: v-miegge
+author: Teresa-Motiv
+ms.author: v-tea
+manager: jarrettr
 ms.topic: article
 ms.prod: hololens
 ms.sitesec: library
@@ -17,9 +17,9 @@ appliesto:
 - HoloLens 2
 ---
 
-# Manage connection endpoints for HoloLens 
+# Manage connection endpoints for HoloLens
 
-Some HoloLens components, apps, and related services transfer data to Microsoft network endpoints. This article lists different endpoints and URLs that need to be whitelisted in your network configuratiion (e.g. proxy or firewall) for those components to be functional.    
+Some HoloLens components, apps, and related services transfer data to Microsoft network endpoints. This article lists different endpoints and URLs that need to be whitelisted in your network configuration (e.g. proxy or firewall) for those components to be functional.    
 
 ## Near-offline setup
 

devices/hololens/scep-whitepaper.md

@@ -16,15 +16,15 @@ appliesto:
 - HoloLens 2
 ---
 
-# SCEP Whitepaper
+# SCEP whitepaper
 
 ## High Level
 
 ### How the SCEP Challenge PW is secured
 
-We work around the weakness of the SCEP protocol by generating custom challenges in Intune itself. The challenge string we create is signed/encrypted, and contains the information we’ve configured in Intune for certificate issuance into the challenge blob. This means the blob used as the challenge string contains the expected CSR information like the Subject Name, Subject Alternative Name, and other attributes.
+We work around the weakness of the SCEP protocol by generating custom challenges in Intune itself. The challenge string we create is signed/encrypted, and contains the information we've configured in Intune for certificate issuance into the challenge blob. This means the blob used as the challenge string contains the expected CSR information like the Subject Name, Subject Alternative Name, and other attributes.
 
-We then pass that to the device and then the device generates it’s CSR and passes it, and the blob to the SCEP URL it received in the MDM profile. On NDES servers running the Intune SCEP module we perform a custom challenge validation that validates the signature on the blob, decrypts the challenge blob itself, compare it to the CSR received, and then determine if we should issue the cert.  If any portion of this check fails then the certificate request is rejected.
+We then pass that to the device and then the device generates it's CSR and passes it, and the blob to the SCEP URL it received in the MDM profile. On NDES servers running the Intune SCEP module we perform a custom challenge validation that validates the signature on the blob, decrypts the challenge blob itself, compare it to the CSR received, and then determine if we should issue the cert.  If any portion of this check fails then the certificate request is rejected.
 
 ## Behind the scenes
 
@@ -72,6 +72,6 @@ We then pass that to the device and then the device generates it’s CSR and pas
 
     1. 1st time configuration of the connector: Authentication to AAD during the initial connector setup.
 
-    1. Connector checks in with Intune, and will process and any cert revocation transactions (i.e, if the Intune tenant admin issues a remote wipe – full or partial,  also If a user unenrolls their device from Intune), reporting on issued certs, renewing the connectors’ SC_Online_Issuing  certificate from Intune.  Also note: the NDES Intune connector has shared PKCS cert functionality (if you decide to issue PKCS/PFX based certs) so the connector checks to Intune for PKCS cert requests even though there won’t be any requests to process.  We are splitting that functionality out, so this connector just handles SCEP, but no ETA yet.
+    1. Connector checks in with Intune, and will process and any cert revocation transactions (i.e, if the Intune tenant admin issues a remote wipe – full or partial,  also If a user unenrolls their device from Intune), reporting on issued certs, renewing the connectors' SC_Online_Issuing  certificate from Intune.  Also note: the NDES Intune connector has shared PKCS cert functionality (if you decide to issue PKCS/PFX based certs) so the connector checks to Intune for PKCS cert requests even though there won't be any requests to process.  We are splitting that functionality out, so this connector just handles SCEP, but no ETA yet.
 
 1. [Here](https://docs.microsoft.com/intune/intune-endpoints#microsoft-intune-certificate-connector) is a reference for Intune NDES connector network communications.