fixed some errors

windows/deployment/update/update-compliance-get-started.md

@@ -13,6 +13,9 @@ ms.localizationpriority: medium
 ---
 
 # Get started with Update Compliance
+This topic explains the steps necessary to configure your environment for Windows Analytics: Update Compliance.
+
+Steps are provided in sections that follow the recommended setup process:
 
 1. Ensure you meet the [Update Compliance prerequisites](#update-compliance-prerequisites).
 2. [Add Update Compliance to your Azure subscription](#add-update-compliance-to-your-azure-subscription).
@@ -24,7 +27,7 @@ Before you begin the process to add Update Compliance to your Azure subscription
 1.	Update Compliance works only with Windows 10 Professional, Education, and Enterprise editions. Update Compliance only provides data for the standard Desktop Windows 10 version and is not currently compatible with Windows Server, Surface Hub, IoT, etc. 
 2.	Update Compliance provides detailed deployment data for devices on the Semi-Annual Channel and the Long-term Servicing Channel. Update Compliance will show Windows Insider Preview devices, but currently will not provide detailed deployment information for them.
 3.	Update Compliance requires at least the Basic level of diagnostic data and a Commercial ID to be enabled on the device. 
-4.	To [show device names](**TODO**: Add device names how-to in FAQ) in Windows Analytics after Windows 10, version 1803, you must opt in.    
+4.	To show device names for versions of Windows 10 starting with 1803 in Windows Analytics you must opt in. For details about this, see the "AllowDeviceNameinTelemetry (in Windows 10)" entry in the table in the [Distributing policies at scale](windows-analytics-get-started#distributing-policies-at-scale) section of [Enrolling devices in Windows Analytics](windows-analytics-get-started).
 5.	To use the Windows Defender Status, devices must be E3-licensed and have Cloud Protection enabled. E5-licensed devices will not appear here. For E5 devices, you should use [Windows Defender ATP](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/windows-defender-advanced-threat-protection) instead. For more information on Windows 10 Enterprise licensing, see [Windows 10 Enterprise: FAQ for IT Professionals](https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-enterprise-faq-itpro).
 
 ## Add Update Compliance to your Azure subscription

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

@@ -23,7 +23,7 @@ Update Compliance is a [Windows Analytics solution](https://docs.microsoft.com/e
 * See the status of Windows Defender Antivirus signatures and threats.
 * Check bandwidth savings incurred across multiple content types by using [Delivery Optimization](waas-delivery-optimization).
 
-Update Compliance is offered through the Azure portal, and is available free for devices that meet the [prerequisites](**TODO**: Add prerequisites link).
+Update Compliance is offered through the Azure portal, and is available free for devices that meet the [prerequisites](update-compliance-get-started#update-compliance-prerequisites).
 
 Update Compliance uses Windows 10 and Windows Defender Antivirus diagnostic data for all of its reporting. It collects system data including update deployment progress, [Windows Update for Business](waas-manage-updates-wufb) configuration data, Windows Defender Antivirus data, and Delivery Optimization usage data, and then sends this data to a secure cloud to be stored for analysis and usage in [Azure Log Analytics](https://docs.microsoft.com/en-us/azure/log-analytics/query-language/get-started-analytics-portal).
 

windows/deployment/update/update-compliance-need-attention.md

@@ -10,10 +10,10 @@ ms.author: jaimeo
 ms.date: 10/04/2018
 ---
 
-# Need Attention!
+# Needs attention!
 ![Needs attention section](images/UC_workspace_needs_attention.png)
 
-The **Needs attention** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section. 
+The **Needs attention!** section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. The summary tile for this section counts the number of devices that have issues, while the blades within break down the issues encountered. Finally, a [list of queries](#list-of-queries) blade in this section contains queries that provide values but do not fit within any other main section. 
 
 >[!NOTE]
 >The summary tile counts the number of devices that have issues, while the blades within the section break down the issues encountered. A single device can have more than one issue, so these numbers might not add up.

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

@@ -20,29 +20,30 @@ In this section you'll learn how to use Update Compliance to monitor your device
 Update Compliance: 
 - Provides detailed deployment data for Windows 10 security, quality, and feature updates.
 - Reports when devices have issues related to updates that need attention.
-- Shows Windows Defender AV status information for devices that use it and meet the [prerequisites](**TODO**: add prerequisites link here).
+- Shows Windows Defender AV status information for devices that use it and meet the [prerequisites](update-compliance-get-started#update-compliance-prerequisites).
 - Shows bandwidth usage and savings for devices that are configured to use [Delivery Optimization](https://docs.microsoft.com/en-us/windows/deployment/update/waas-delivery-optimization).
 - Provides all of the above data in [Log Analytics](#using-log-analytics), which affords additional querying and export capabilities.
 
 ## The Update Compliance Tile
-After Update Compliance has successfully been [added to your Azure subscription](**TODO**: Link to adding to azure subscription), you’ll see this tile:
+After Update Compliance has successfully been [added to your Azure subscription](update-compliance-get-started#add-update-compliance-to-your-azure-subscription), you’ll see this tile:
 
-![Update Compliance Tile no data](images/UC_tile_assessing.png)
+![Update Compliance tile no data](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 Windows Analytics](windows-analytics-get-started). 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)
+![Update Compliance tile with data](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)
 
 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. 
 
-### Overview Blade
+### Overview blade
 
-![The Overview Blade](images/UC_overview_blade.png)
+![The Overview blade](images/UC_workspace_overview_blade.png)
 
 Update Compliance’s overview blade summarizes all the data Update Compliance provides. It functions as a hub from which you can navigate to different sections. The total number of devices detected by Update Compliance is reported in the title of this blade. What follows is a distribution for all devices as to whether they are up to date on:
 * Security updates: A device is up to date on quality updates whenever it has the latest applicable quality update installed. Quality updates are monthly cumulative updates that are specific to a version of Windows 10.
@@ -55,8 +56,8 @@ The following is a breakdown of the different sections available in Update Compl
 * [Need Attention!](update-compliance-need-attention.md) - This section is the default section when arriving to your Update Compliance workspace. It provides a summary of the different issues devices are facing relative to Windows 10 updates.
 * [Security Update Status](update-compliance-security-update-status.md) - This section lists the percentage of devices that are on the latest security update released for the version of Windows 10 it is running. Selecting this section provides blades that summarize the overall status of security updates across all devices and a summary of their deployment progress towards the latest two security updates. 
 * [Feature Update Status](update-compliance-feature-update-status.md) - This section lists the percentage of devices that are on the latest feature update that is applicable to a given device. Selecting this section provides blades that summarize the overall feature update status across all devices and a summary of deployment status for different versions of Windows 10 in your environment.
-* [Windows Defender AV Status](update-compliance-wd-av-status.md) - This section lists the percentage of devices running Windows Defender Antivirus that are not sufficiently protected. Selecting this section provides a summary of signature and threat status across all devices that are running Windows Defender Antivirus. This section is not applicable to devices not running Windows Defender Antivirus or devices that do not meet the [prerequisites](**TODO**: Prerequisites link here) to be assessed. 
-* [Delivery Optimization Status](update-compliance-do-status.md) - This section summarizes bandwidth savings incurred by utilizing Delivery Optimization in your environment. It provides a breakdown of Delivery Optimization configuration across devices, and summarizes bandwidth savings and utilization across multiple content types.
+* [Windows Defender AV Status](update-compliance-wd-av-status.md) - This section lists the percentage of devices running Windows Defender Antivirus that are not sufficiently protected. Selecting this section provides a summary of signature and threat status across all devices that are running Windows Defender Antivirus. This section is not applicable to devices not running Windows Defender Antivirus or devices that do not meet the [prerequisites](update-compliance-get-started#update-compliance-prerequisites) to be assessed. 
+* [Delivery Optimization Status](update-compliance-delivery-optimization.md) - This section summarizes bandwidth savings incurred by utilizing Delivery Optimization in your environment. It provides a breakdown of Delivery Optimization configuration across devices, and summarizes bandwidth savings and utilization across multiple content types.
 
 
 ## Update Compliance data latency

windows/deployment/update/update-compliance-wd-av-status.md

@@ -19,13 +19,17 @@ The Windows Defender AV Status section deals with data concerning signature and
 >[!NOTE]
 >Update Compliance's Windows Defender Antivirus status is compatible with E3, B, F1, VL Professional and below licenses. Devices with an E5 license are not shown here; devices with an E5 license can be monitored using the [Windows Defender ATP portal](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-endpoints-windows-defender-advanced-threat-protection). If you'd like to learn more about Windows 10 licensing, see the [Windows 10 product licensing options](https://www.microsoft.com/en-us/Licensing/product-licensing/windows10.aspx). 
 
-The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Clicking any of these statuses will navigate you to a Log Search view containing the query. 
+# Windows Defender AV Status sections
+The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Selecting any of these statuses will navigate you to a Log Search view containing the query. 
 
-The **Threat Status** blade shows the number of devices (of those that have encountered threats) that were and were not remediated successfully. It also provides a detailed count. Selecting either of these takes you to the respective query in Log Search for further investigation. 
+The **Threat Status** blade shows, among devices that have encountered threats, how many were and were not remediated successfully. It also provides a detailed count. Selecting either of these will take you to the respective query in Log Search for further investigation. 
 
-Here are some important terms to consider when utilizing the Windows Defender AV Status section of Update Compliance:
-* **Signature out of date** devices are devices with signature older than 14 days.
-* **No real-time protection** devices are devices who are using Windows Defender AV but have turned off Real-time protection.
+Here are some important terms to consider when using the Windows Defender AV Status section of Update Compliance:
+* **Signature out of date** devices are devices with a signature older than 14 days.
+* **No real-time protection** devices are devices that are using Windows Defender AV but have turned off real-time protection.
 * **Recently disappeared** devices are devices that were previously seen by Windows Defender AV and are no longer seen in the past 7 days.
 * **Remediation failed** devices are devices where Windows Defender AV failed to remediate the threat. This could be due to a number of reasons, including a full disk, network error, operation aborted, etc. Manual intervention might be needed from IT team.
 * **Not assessed** devices are devices where either a non-Microsoft AV solution is used or it has been more than 7 days since the device recently disappeared.
+
+## Windows Defender data latency
+Because of the way Windows Defender is associated with the rest of Windows device data, Defender data for new devices might take much longer to appear than other data types. This process could take up to 28 days.