From 0146fe1744ac9654a0b97c7941337d24d195c3c3 Mon Sep 17 00:00:00 2001
From: Charles Inglis <32555877+cinglis-msft@users.noreply.github.com>
Date: Mon, 30 Mar 2020 18:13:46 -0700
Subject: [PATCH] Update
 windows/deployment/update/update-compliance-get-started.md

Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
---
 windows/deployment/update/update-compliance-get-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/update/update-compliance-get-started.md b/windows/deployment/update/update-compliance-get-started.md
index a18c25596f..f43a487b2e 100644
--- a/windows/deployment/update/update-compliance-get-started.md
+++ b/windows/deployment/update/update-compliance-get-started.md
@@ -125,4 +125,4 @@ Allow Device Name in Telemetry is under the same node as Commercial ID and Allow
 Allow Device Name in Telemetry is under the [Policy Configuration Service Provider](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider) as [System/AllowTelemetry](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-system#system-allowtelemetry). 
 
 > [!NOTE]
->After enrolling your devices (by deploying your CommercialID and Windows Diagnostic Data settings), it might take 48-72 hours for the first data to appear in the solution. Until then, Update Compliance will indicate it is still assessing devices. 
+> After enrolling your devices (by deploying your CommercialID and Windows Diagnostic Data settings), it might take 48-72 hours for the first data to appear in the solution. Until then, Update Compliance will indicate it is still assessing devices.