From d8e2831b439a1434350ab662e5d96c0903b4fff0 Mon Sep 17 00:00:00 2001
From: Serling1225 <91347931+serling1962@users.noreply.github.com>
Date: Tue, 19 Nov 2024 08:49:06 -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 10f4eadc..00c5c6bb 100644
--- a/Instructions/Labs/LAB_10_Microsoft Sentinel.md	
+++ b/Instructions/Labs/LAB_10_Microsoft Sentinel.md	
@@ -48,7 +48,7 @@ In this exercise, you will complete the following tasks:
 - Task 5: Create a custom alert and configure the playbook as an automated response.
 - Task 6: Invoke an incident and review the associated actions.
 
-#### Task 1: On-board Azure Sentinel
+#### Task 1: On-board Microsoft Sentinel
 
 In this task, you will on-board Microsoft Sentinel and connect the Log Analytics workspace. 
 
@@ -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 Azure 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/azure/sentinel/quickstart-onboard)
 	
 #### Task 2: Configure Microsoft Sentinel to use the Azure Activity data connector.