From 6f3b63649781d7be170f97d169479ddfc570bdec Mon Sep 17 00:00:00 2001
From: ImranHabib <47118050+joinimran@users.noreply.github.com>
Date: Sat, 17 Aug 2019 10:35:03 +0500
Subject: [PATCH] Terminology Correction

Terminology Correction
---
 .../deployment/update/windows-analytics-FAQ-troubleshooting.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/update/windows-analytics-FAQ-troubleshooting.md b/windows/deployment/update/windows-analytics-FAQ-troubleshooting.md
index 32a276b7f1..8ba5c114c5 100644
--- a/windows/deployment/update/windows-analytics-FAQ-troubleshooting.md
+++ b/windows/deployment/update/windows-analytics-FAQ-troubleshooting.md
@@ -55,7 +55,7 @@ If you've followed the steps in the [Enrolling devices in Windows Analytics](win
 
 ### Devices not appearing in Upgrade Readiness
 
-In Log Analytics, go to **Solutions** and verify that you are subscribed to the Windows Analytics solutions you intend to use.
+In Log Analytics workspace, go to **Solutions** and verify that you are subscribed to the Windows Analytics solutions you intend to use.
 
 Even though devices can take 2-3 days after enrollment to show up due to latency in the system, you can now verify the status of your devices within a few hours of running the deployment script as described in [You can now check on the status of your computers within hours of running the deployment script](https://techcommunity.microsoft.com/t5/Windows-Analytics-Blog/You-can-now-check-on-the-status-of-your-computers-within-hours/ba-p/187213) on the Tech Community Blog.