From ab48ae4cf9cd68d14a567a21ffe0053a735bca43 Mon Sep 17 00:00:00 2001
From: Serling1225 <91347931+serling1962@users.noreply.github.com>
Date: Tue, 19 Nov 2024 08:51:19 -0600
Subject: [PATCH] Update LAB_10_Microsoft Sentinel.md

---
 Instructions/Labs/LAB_10_Microsoft Sentinel.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Instructions/Labs/LAB_10_Microsoft Sentinel.md b/Instructions/Labs/LAB_10_Microsoft Sentinel.md
index 00c5c6bb..87e9fce2 100644
--- a/Instructions/Labs/LAB_10_Microsoft Sentinel.md	
+++ b/Instructions/Labs/LAB_10_Microsoft Sentinel.md	
@@ -9,7 +9,7 @@ lab:
 
 ## Lab scenario
 
-**Note:** **Azure Sentinel** is renamed to **Microsoft Sentinel** 
+**Note:** **Microsoft Sentinel** is renamed to **Microsoft Sentinel** 
 
 You have been asked to create a proof of concept of Microsoft Sentinel-based threat detection and response. Specifically, you want to:
 
@@ -64,7 +64,7 @@ In this task, you will on-board Microsoft Sentinel and connect the Log Analytics
 
 4. On the **Add Microsoft Sentinel to a workspace** blade, select the Log Analytics workspace you created in the Azure Monitor lab and click **Add**.
 
-    >**Note**: Microsoft Sentinel has very specific requirements for workspaces. For example, workspaces created by Microsoft Defender for Cloud can not be used. Read more at [Quickstart: On-board Microsoft Sentinel](https://docs.microsoft.com/en-us/azure/sentinel/quickstart-onboard)
+    >**Note**: Microsoft Sentinel has very specific requirements for workspaces. For example, workspaces created by Microsoft Defender for Cloud can not be used. Read more at [Quickstart: On-board Microsoft Sentinel](https://docs.microsoft.com/en-us/microsoft/sentinel/quickstart-onboard)
 	
 #### Task 2: Configure Microsoft Sentinel to use the Azure Activity data connector.