From 28f46a7844a3e4b93a6d69f93049a7edffa7a6de Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Tue, 30 Jan 2024 09:58:44 -0800
Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md

---
 .../Lab/LAB_05-Implement_Intersite_Connectivity.md           | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md
index d426187f..bf686b80 100644
--- a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
+++ b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
@@ -234,9 +234,8 @@ Congratulations on completing the lab. Here are the main takeaways for this lab.
 + Virtual network peering enables you to seamlessly connect two or more virtual networks in Azure.
 + Peered virtual networks appear as one for connectivity purposes.
 + The traffic between virtual machines in peered virtual networks uses the Microsoft backbone infrastructure.
-+ System defined routes are automatically created for each subnet in a virtual network.
-+ User-defined routes override or add to the default system routes. For example, a user-defined route could enable Azure Virtual Appliances to handle the traffic between a subnet and the internet.
-+ Route tables contain the networking map that defines the network traffic from one place to another. 
++ System defined routes are automatically created for each subnet in a virtual network. User-defined routes override or add to the default system routes. 
++ Azure Network Watcher provides a suite of tools to monitor, diagnose, and view metrics and logs for Azure IaaS resources.
 
 
 ## Learn more with self-paced training