edits

windows/deployment/update/update-compliance-v2-enable.md

@@ -65,7 +65,8 @@ Update Compliance is offered as an Azure Marketplace application that's linked t
 1. Select **Create** to add the solution. You'll receive a notification when the Updates Compliance solution has been successfully created.
 
 > [!Note]
-> You can only map one tenant to one Log Analytics workspace. Mapping one tenant to multiple workspaces isn't supported.
+> - You can only map one tenant to one Log Analytics workspace. Mapping one tenant to multiple workspaces isn't supported.
+> - If you change the Log Analytics workspace for Update Compliance, stale data will be displayed for about 24 hours until the new workspace is fully onboarded.
 
 ### <a name="bkmk_id"></a> Get the Commercial ID for the Update Compliance solution
 
@@ -80,7 +81,7 @@ The **Commercial ID** directs your clients to the Update Compliance solution in
 1. The **Commercial Id Key** is listed in the text box with an option to copy the ID. The **Commercial Id Key** is commonly referred to as the `CommercialID` or **Commercial ID** in Update Compliance.
 
    > [!Warning]
-   > Regenerate a Commercial ID only if your original ID can no longer be used. Regenerating a Commercial ID requires you to deploy the new commercial ID to your computers in order to continue to collect data and so can result in data loss.
+   > Regenerate a Commercial ID only if your original ID can no longer be used. Regenerating a Commercial ID requires you to deploy the new commercial ID to your computers in order to continue to collect data and can result in data loss.
 
 
 ## Next steps

windows/deployment/update/update-compliance-v2-schema.md

@@ -37,3 +37,8 @@ The table below summarizes the different tables that are part of the Update Comp
 | [**UCServiceUpdateStatus**](update-compliance-v2-schema-ucserviceupdatestatus.md) | Service record  | Update Event that comes directly from the service-side. The event has only service-side information for one device (client), and one update, in one deployment. This event has certain fields removed from it in favor of being able to show data in near real-time.  |
 | [**UCUpdateAlert**](update-compliance-v2-schema-ucupdatealert.md) | Service and device records  |  Alert for both client and service update. Contains information that needs attention, relative to one device (client), one update, and one deployment (if relevant). Certain fields may be blank depending on the UpdateAlert's AlertType field; for example, ServiceUpdateAlert will not necessarily contain client-side statuses.  |
 | [**UCDeviceAlert**](update-compliance-v2-schema-ucdevicealert.md)| Service and device record  |  These alerts are activated as a result of an issue that is device-specific. It isn't specific to the combination of a specific update and a specific device. Like UpdateAlerts, the AlertType indicates where the Alert comes from (ServiceDeviceAlert, ClientDeviceAlert). For example, an EndOfService alert is a ClientDeviceAlert, as a build no longer being serviced (EOS) is a client-wide state. Meanwhile, DeviceRegistrationIssues in WUfB DS will be a ServiceDeviceAlert, as it's a device-wide state in the service to not be correctly registered.  |
+
+## Next steps
+
+- [Update Compliance overview](update-compliance-v2-overview.md)
+- [Use Update Compliance](update-compliance-v2-use.md)

windows/deployment/update/update-compliance-v2-use.md

@@ -49,9 +49,9 @@ The data powering Update Compliance is refreshed every 24 hours, and refreshes w
 
 | Data Type | Data upload rate from device | Data Latency |
 |--|--|--|
-|WaaSUpdateStatus | Once per day |4 hours |
-|WaaSInsiderStatus| Once per day |4 hours |
-|WaaSDeploymentStatus|Every update event (Download, install, etc.)|24-36 hours |
+|UCClient | Once per day |4 hours |
+|UCClientUpdateStatus|Every update event (Download, install, etc.)|24-36 hours |
+|UCServiceUpdateStatus| Every update event (Download, install, etc.)|24-36 hours |
 |WUDOAggregatedStatus|On update event, aggregated over time|24-36 hours |
 |WUDOStatus|Once per day|12 hours |