Merge pull request #6104 from MicrosoftDocs/v-gmoor-fix-pr-6098-2

Fix low Acrolinx score and minor things after force-push

windows/client-management/mdm/policy-csp-networklistmanager.md

@@ -1,6 +1,6 @@
 ---
 title: Policy CSP - NetworkListManager
-description: The Policy CSP - NetworkListManager setting creates a new MDM policy that allows admins to configure a list of URIs of HTTPS endpoints that are considered secure.
+description: Policy CSP - NetworkListManager is a setting creates a new MDM policy. This setting allows admins to configure a list of URIs of HTTPS endpoints that are considered secure.
 ms.author: v-nsatapathy
 ms.topic: article
 ms.prod: w10
@@ -18,7 +18,7 @@ manager: dansimp
 <hr/>
 
 <!--Policies-->
-## NetworkListManager policies  
+## NetworkListManager policies 
 
 <dl>
   <dd>
@@ -61,16 +61,18 @@ manager: dansimp
 This policy setting provides the list of URLs (separated by Unicode character 0xF000) to endpoints accessible only within an enterprise's network. If any of the URLs can be resolved over HTTPS, the network would be considered authenticated.  
 
 When entering a list of TLS endpoints in Microsoft Endpoint Manager, you must follow this format, even in the UI:  
-```<![CDATA[https://nls.corp.contoso.com&#xF000;https://nls.corp.fabricam.com]]>```  
+
-- The HTTPS endpoint must not have any additional authentication checks, such as login or multifactor authentication.
+`<![CDATA[https://nls.corp.contoso.com&#xF000;https://nls.corp.fabricam.com]]>`
+
+- The HTTPS endpoint must not have any more authentication checks, such as login or multi-factor authentication.
+
 - The HTTPS endpoint must be an internal address not accessible from outside the corporate network.
-- The client must trust the server certificate, so the CA certificate that the HTTPS server certificate chains to must be present in the client machine's root certificate store.
+
+- The client must trust the server certificate. So the CA certificate that the HTTPS server certificate chains to must be present in the client machine's root certificate store.
+
 - A certificate should not be a public certificate.
 
 
-<hr/>
-
-
 <hr/>
 
 <!--Policy-->
@@ -99,7 +101,7 @@ When entering a list of TLS endpoints in Microsoft Endpoint Manager, you must fo
 
 <!--/Scope-->
 <!--Description-->
-This policy setting provides the string to be used to name the network authenticated against one of the endpoints listed in NetworkListManager/AllowedTlsAuthenticationEndpoints policy. If this setting is used for Trusted Network Detection in an Always On VPN profile, it must be the DNS suffix configured in the TrustedNetworkDetection attribute.
+This policy setting provides the string that is to be used to name a network. That network is authenticated against one of the endpoints that are listed in NetworkListManager/AllowedTlsAuthenticationEndpoints policy. If this setting is used for Trusted Network Detection in an _Always On_ VPN profile, it must be the DNS suffix that is configured in the TrustedNetworkDetection attribute.
 
 <hr/>
 

windows/deployment/update/update-compliance-using.md

@@ -26,7 +26,7 @@ ms.custom: seo-marvel-apr2020
 In this section you'll learn how to use Update Compliance to monitor your device's Windows updates and Microsoft Defender Antivirus status. To configure your environment for use with Update Compliance, refer to [Get started with Update Compliance](update-compliance-get-started.md).
 
 
-Update Compliance: 
+Update Compliance:
 - Provides detailed deployment monitoring for Windows client feature and quality updates.
 - Reports when devices need attention due to issues related to update deployment.
 - Shows bandwidth usage and savings for devices that are configured to use [Delivery Optimization](waas-delivery-optimization.md).
@@ -35,17 +35,17 @@ Update Compliance:
 ## The Update Compliance tile
 After Update Compliance is successfully [added to your Azure subscription](update-compliance-get-started.md#add-update-compliance-to-your-azure-subscription), you can navigate to your log analytics workspace, select your Update Compliance deployment in the **Solutions** section, and then select  **Summary** to see this tile:
 
-![Update Compliance tile no data.](images/UC_tile_assessing.png)
+:::image type="content" alt-text="Update Compliance tile no data." source="images/UC_tile_assessing.png":::
 
 When the solution is added, data is not immediately available. Data will begin to be collected after data is sent up that belongs to the Commercial ID associated with the device. This process assumes that Windows diagnostic data is enabled and data sharing is enabled as described in [Enrolling devices in Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance). After Microsoft has collected and processed any device data associated with your Commercial ID, the tile will be replaced with the following summary:
 
-![Update Compliance tile with data.](images/UC_tile_filled.png)
+:::image type="content" alt-text="Update Compliance tile with data." source="images/UC_tile_filled.png":::
 
 The summary details the total number of devices that Microsoft has received data from with your Commercial ID. It also provides the number of devices that need attention if any. Finally, it details the last point at which your Update Compliance workspace was refreshed.
 
 ## The Update Compliance workspace
 
-![Update Compliance workspace view.](images/UC_workspace_needs_attention.png)
+:::image type="content" alt-text="Update Compliance workspace view." source="images/UC_workspace_needs_attention.png" lightbox="images/UC_workspace_needs_attention.png":::
 
 When you select this tile, you will be redirected to the Update Compliance workspace. The workspace is organized with the Overview blade providing a hub from which to navigate to different reports of your devices' data.