From cd754edfd728a5cfba3ba3db1a40338dd6585d54 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Wed, 3 Jan 2024 07:16:50 -0800
Subject: [PATCH] Update LAB_11-Implement_Monitoring.md

---
 New Instructions/Lab/LAB_11-Implement_Monitoring.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/New Instructions/Lab/LAB_11-Implement_Monitoring.md b/New Instructions/Lab/LAB_11-Implement_Monitoring.md
index e36d23d8..0d0b682c 100644
--- a/New Instructions/Lab/LAB_11-Implement_Monitoring.md	
+++ b/New Instructions/Lab/LAB_11-Implement_Monitoring.md	
@@ -238,13 +238,9 @@ In this task, you will use Azure Monitor to query the data captured from the vir
 Congratulations on completing the lab. Here are the main takeaways for this lab. 
 
 + Alerts help you detect and address issues before users notice there might be a problem with your infrastructure or application.
-
 + You can alert on any metric or log data source in the Azure Monitor data platform.
-
 + An alert rule monitors your data and captures a signal that indicates something is happening on the specified resource.
-
 + An alert is triggered if the conditions of the alert rule are met. Several actions (email, SMS, push, voice) can be triggered.
-
 + Action groups include individuals that should be notified of an alert, so they can take action. 
 
 ## Cleanup your resources