From fd789902d8c6e3176003ea778c1fce1a9e0bb0db Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Mon, 31 Jan 2022 07:05:10 -0800
Subject: [PATCH] Update LAB_06-Implement_Network_Traffic_Management.md

---
 .../Labs/LAB_06-Implement_Network_Traffic_Management.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
index cd26350f..dcb46d03 100644
--- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
+++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
@@ -178,7 +178,7 @@ In this task, you will test transitivity of virtual network peering by using Net
 
 1. In the Azure portal, search for and select **Network Watcher**.
 
-1. On the **Network Watcher** blade, expand the listing of Azure regions and verify that the service is enabled in the Azure into which you deployed resources in the first task of this lab.
+1. On the **Network Watcher** blade, expand the listing of Azure regions and verify the service is enabled in region you are using. 
 
 1. On the **Network Watcher** blade, navigate to the **Connection troubleshoot**.