From 4dd5ef73a94b538489116ecd673360052f2c1a38 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:37:09 -0700
Subject: [PATCH 01/28] Update LAB_02a_Manage_Subscriptions_and_RBAC.md

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

diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md
index 2e6a2aec..8745960a 100644
--- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md
+++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md
@@ -141,7 +141,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro
 
 1. In the Azure portal, navigate back to the **az104-02-mg1** management group and display its **details**.
 
-1. Click **Access control (IAM)**, click **+ Add** followed by **Role assignment**, and assign the **Support Request Contributor (Custom)** role to the newly created user account.
+1. Click **Access control (IAM)**, click **+ Add** followed by **Add role assignment**, and assign the **Support Request Contributor (Custom)** role to the newly created user account.
 
 1. Open an **InPrivate** browser window and sign in to the [Azure portal](https://portal.azure.com) using the newly created user account. When prompted to update the password, change the password for the user.
 

From 384a09869835183a9a27708feef0bf1a34379f16 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:42:12 -0700
Subject: [PATCH 02/28] Update LAB_02b-Manage_Governance_via_Azure_Policy.md

---
 Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
index bf35a18e..46ad3082 100644
--- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
+++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
@@ -61,7 +61,7 @@ In this task, you will create and assign a tag to an Azure resource group via th
 
     **Note**: note what resource group the storage account is in, you'll need it later in the lab.
 
-1. On the resource group blade, click **Tags**.
+1. On the resource group blade, click **Click here to add tags**.
 
 1. Create a tag with the following settings and Apply your change:
 

From ad39fb2717e52c1d857dba5e8cf2dacb0ceb7139 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:49:10 -0700
Subject: [PATCH 03/28] Update LAB_02b-Manage_Governance_via_Azure_Policy.md

---
 Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
index bf35a18e..5dc47fda 100644
--- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
+++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
@@ -212,7 +212,7 @@ In this task, we will use a different policy definition to remediate any non-com
 
 1. In the list of storage accounts, select the resource group corresponding to the storage account you created in the last task of this lab. Select **Tags** and click **Delete** (Trash can to the right) to the **Role:Infra** tag and press **Apply**. 
 
-1. Click **Delete**, when prompted for the confirmation, in the **Delete storage account** blade, type the name of the storage account to confirm and click **Delete**. 
+1. Click **Overview** and click **Delete** on the top of the storage account blade. When prompted for the confirmation, in the **Delete storage account** blade, type the name of the storage account to confirm and click **Delete**. 
 
 #### Review
 

From 1be7fd6dbc839ad0db73bea43a75e9fc2780e5a2 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:50:51 -0700
Subject: [PATCH 04/28] Update
 LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md

---
 .../LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
index e5548b22..6bc65016 100644
--- a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
+++ b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
@@ -35,7 +35,7 @@ In this task, you will use the Azure portal to create resource groups and create
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. In the Azure portal, search for and select **Disks**, click **+ Add, + Create, or + New**, and specify the following settings:
+1. In the Azure portal, search for and select **Disks**, click **+ Create** and specify the following settings:
 
     |Setting|Value|
     |---|---|

From 2ae793f55efe499ac52c41b0219eda4010c56132 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:52:14 -0700
Subject: [PATCH 05/28] Update
 LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md

---
 .../LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
index e5548b22..f8a241e1 100644
--- a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
+++ b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md
@@ -74,7 +74,7 @@ In this task, we will move the disk resource you created in the previous task to
 
 In this task, you will apply a resource lock to an Azure resource group containing a disk resource.
 
-1. In the Azure portal, search for and select **Disks**, click **+ Add, + Create, or + New**, and specify the following settings:
+1. In the Azure portal, search for and select **Disks**, click **+ Create** and specify the following settings:
 
     |Setting|Value|
     |---|---|

From 7588924ac1641be39375795e431205de226a2df5 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 12:53:34 -0700
Subject: [PATCH 06/28] Update
 LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md

---
 .../LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md    | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md b/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md
index 51bdd207..dce5ea23 100644
--- a/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md
+++ b/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md
@@ -62,8 +62,6 @@ In this task, you will create an Azure disk resource by using an Azure Resource
 
 1. In the Azure portal, search for and select **Deploy a custom template**.
 
-1. Click **Template deployment (deploy using custom templates)** found under the **Marketplace** group.
-
 1. On the **Custom deployment** blade, click **Build your own template in the editor**.
 
 1. On the **Edit template** blade, click **Load file** and upload the **template.json** file you downloaded in the previous task.

From b4d2780a62fd74dbc85635ea3a1b99feff846e2e Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:10:21 -0700
Subject: [PATCH 07/28] Update LAB_06-Implement_Network_Traffic_Management.md

---
 .../Labs/LAB_06-Implement_Network_Traffic_Management.md         | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
index cd26350f..ac3d073e 100644
--- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
+++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
@@ -412,8 +412,6 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
     | Name | any unique name |
     | Public IP address | **Create new** |
     | Public IP address name | **az104-06-pip4** |
-    | Availability zone | **No Zone** |
-    | Add a public IPv6 address | **No** |
 
 1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment.
 

From f94a7b39fec48991318b6f67be45d9bd5189ee49 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:25:59 -0700
Subject: [PATCH 08/28] Update LAB_07-Manage_Azure_Storage.md

---
 Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
index 6ead2a48..e729182d 100644
--- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
+++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
@@ -91,7 +91,7 @@ In this task, you will create and configure an Azure Storage account.
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Resource group | the name of a **new** resource group **az104-07-rg1** |
     | Storage account name | any globally unique name between 3 and 24 in length consisting of letters and digits |
-    | Location | the name of an Azure region where you can create an Azure Storage account  |
+    | Region | the name of an Azure region where you can create an Azure Storage account  |
     | Performance | **Standard** |
     | Redundancy | **Geo-redundant storage (GRS)** |
 

From 8750d841e22e050244a30fffaccfee51615130f6 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:31:05 -0700
Subject: [PATCH 09/28] Update LAB_07-Manage_Azure_Storage.md

---
 Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
index 6ead2a48..f859d064 100644
--- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
+++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
@@ -203,7 +203,7 @@ In this task, you will configure authentication and authorization for Azure Stor
 
 1. On the **az104-07-container** blade, click **Access Control (IAM)**.
 
-1. In the **Add** section, click **Add a role assignment**.
+1. On the **Check access** tab, click **Add role assignment**.
 
 1. On the **Add role assignment** blade, specify the following settings:
 

From ed59ce8f4adcee16dc10afd6fae75a2a7a3bae76 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:32:32 -0700
Subject: [PATCH 10/28] Update LAB_07-Manage_Azure_Storage.md

---
 Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
index 6ead2a48..6eae7d7b 100644
--- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
+++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
@@ -213,7 +213,7 @@ In this task, you will configure authentication and authorization for Azure Stor
     | Assign access to | **User, group, or service principal** |
     | Members | the name of your user account |
 
-1. Click 'Review+Assign' and then 'Review+ assign', and return to the **Overview** blade of the **az104-07-container** container and verify that you can change the Authentication method to (Switch to Azure AD User Account).
+1. Click **Review + Assign** and then **Review + assign**, and return to the **Overview** blade of the **az104-07-container** container and verify that you can change the Authentication method to (Switch to Azure AD User Account).
 
     > **Note**: It might take about 5 minutes for the change to take effect.
 

From ef40bf3098fd2af8106677f4ea1894a3b7ad7b7b Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:34:01 -0700
Subject: [PATCH 11/28] Update LAB_07-Manage_Azure_Storage.md

---
 Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
index 6ead2a48..4d3f842b 100644
--- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
+++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md
@@ -277,7 +277,7 @@ In this task, you will configure network access for Azure Storage.
 
     > **Note**: This is expected, since you are connecting from your client IP address.
 
-1. Close the InPrivate mode browser window, return to the browser window showing the **licenses/LICENSE** blade of the Azure Storage container.
+1. Close the InPrivate mode browser window, return to the browser window showing the **Networking** blade of the Azure Storage account.
 
 1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal.
 

From 37cd19cee1ed773d45ac44abc39ac3a4a57bac3b Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:35:52 -0700
Subject: [PATCH 12/28] Update LAB_08-Manage_Virtual_Machines.md

---
 Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
index 28a7653a..b782f8e4 100644
--- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
+++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
@@ -52,7 +52,7 @@ In this task, you will deploy Azure virtual machines into different availability
     | Region | select one of the regions that support availability zones and where you can provision Azure virtual machines |
     | Availability options | **Availability zone** |
     | Availability zone | **1** |
-    | Image | **Windows Server 2019 Datacenter - Gen1/Gen2** |
+    | Image | **Windows Server 2019 Datacenter - Gen2** |
     | Azure Spot instance | **No** |
     | Size | **Standard D2s v3** |
     | Username | **Student** |

From dff8df0fbb96fe9858050537eb91b2869d663bdc Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:47:47 -0700
Subject: [PATCH 13/28] Update LAB_08-Manage_Virtual_Machines.md

---
 Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
index 28a7653a..2b37dcef 100644
--- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
+++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
@@ -283,7 +283,7 @@ In this task you will scale compute for Azure virtual machines by changing their
 
     >**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal.
 
-1. On the **Edit template** blade, in the section displaying the content of the template, replace line **50** (`"dataDisks": [ ]` line) with the following code :
+1. On the **Edit template** blade, in the section displaying the content of the template, replace line **51** (`"dataDisks": [ ]` line) with the following code :
 
    ```json
                     "dataDisks": [

From a0f31b3c4ef9e64b3bb95cfcbbd06312cacb06bc Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 13:52:05 -0700
Subject: [PATCH 14/28] Update LAB_09a-Implement_Web_Apps.md

---
 Instructions/Labs/LAB_09a-Implement_Web_Apps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md
index 1551fd1f..3b166616 100644
--- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md
+++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md
@@ -40,7 +40,7 @@ In this task, you will create an Azure web app.
 
 1. In the Azure portal, search for and select **App services**, and, on the **App Services** blade, click **+ Create**.
 
-1. On the **Basics** tab of the **Web App** blade, specify the following settings (leave others with their default values):
+1. On the **Basics** tab of the **Create Web App** blade, specify the following settings (leave others with their default values):
 
     | Setting | Value |
     | --- | ---|

From 2135ee85c46c2fe48964d74266c34c4512d36dd7 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:04:05 -0700
Subject: [PATCH 15/28] Update LAB_10-Implement_Data_Protection.md

---
 Instructions/Labs/LAB_10-Implement_Data_Protection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_10-Implement_Data_Protection.md b/Instructions/Labs/LAB_10-Implement_Data_Protection.md
index d8f583c0..6f95e763 100644
--- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md
+++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md
@@ -102,7 +102,7 @@ In this task, you will create a recovery services vault.
 
 1. Back on the **az104-10-rsv1 - Properties** blade, click the **Update** link under **Security Settings** label.
 
-1. On the **Security Settings** blade, note that **Soft Delete (For Azure Virtual Machines)** is **Enabled**.
+1. On the **Security Settings** blade, note that **Soft Delete (For workload running in Azure)** is **Enabled**.
 
 1. Close the **Security Settings** blade and, back on the **az104-10-rsv1** Recovery Services vault blade, click **Overview**.
 

From 051be46955b7a17ac03d09790ee1c1998a8e901c Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:07:30 -0700
Subject: [PATCH 16/28] Update LAB_10-Implement_Data_Protection.md

---
 Instructions/Labs/LAB_10-Implement_Data_Protection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_10-Implement_Data_Protection.md b/Instructions/Labs/LAB_10-Implement_Data_Protection.md
index d8f583c0..b0457a34 100644
--- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md
+++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md
@@ -143,7 +143,7 @@ In this task, you will implement Azure virtual-machine level backup.
 
 1. Navigate back to the **az104-10-rsv1** Recovery Services vault blade, in the **Protected items** section, click **Backup items**, and then click the **Azure virtual machines** entry.
 
-1. On the **Backup Items (Azure Virtual Machine)** blade of **az104-10-vm0**, review the values of the **Backup Pre-Check** and **Last Backup Status** entries.
+1. On the **Backup Items (Azure Virtual Machine)** blade click **az104-10-vm0**, and review the values of the **Backup Pre-Check** and **Last Backup Status** entries.
 
 1. On the **az104-10-vm0** Backup Item blade, click **Backup now**, accept the default value in the **Retain Backup Till** drop-down list, and click **OK**.
 

From ce9f363fb79160a5fd69f047beb84bfe8c28eeef Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:09:39 -0700
Subject: [PATCH 17/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..c7763ffd 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -104,7 +104,7 @@ In this task, you will create and configure an Azure Log Analytics workspace and
 
     | Settings | Value |
     | --- | --- |
-    | Name | any unique name |
+    | Automation account name | any unique name |
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Resource group | **az104-11-rg1** |
     | Location | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) |

From d0e34da9b31a6809027cecafe5eb58c6cbbedf54 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:10:48 -0700
Subject: [PATCH 18/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..6b2350ac 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -107,7 +107,7 @@ In this task, you will create and configure an Azure Log Analytics workspace and
     | Name | any unique name |
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Resource group | **az104-11-rg1** |
-    | Location | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) |
+    | Region | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) |
 
     >**Note**: Make sure that you specify the Azure region based on the [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings)
 

From fa6e6e27a667cd311d4f39b6124c3007c9e6209b Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:14:36 -0700
Subject: [PATCH 19/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..b8810959 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -210,7 +210,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
     | Aggregation granularity (Period) | **1 minute** |
     | Frequency of evaluation | **Every 1 Minute** |
 
-1. On the **Create alert rule** blade, in the **Action group** section, click **Add action groups** and then click the **+ Create action group** button.
+1. Click **Next: Actions >**, on the **Create an alert rule** blade, in the **Action group** section, click the **+ Create action group** button.
 
 1. On the **Basics** tab of the **Create action group** blade, specify the following settings (leave others with their default values) and select **Next: Notifications >**:
 

From 7adcaeb07626599ef630a21f71ce8165c53ea481 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:16:35 -0700
Subject: [PATCH 20/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..4e3cfb9b 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -221,7 +221,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
     | Action group name | **az104-11-ag1** |
     | Display name | **az104-11-ag1** |
 
-1. On the **Notifications** tab of the **Create action group** blade, in the **Notification type** drop-down list, select **Email/SMS/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon.
+1. On the **Notifications** tab of the **Create an action group** blade, in the **Notification type** drop-down list, select **Email/SMS message/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon.
 
 1. On the **Email/SMS/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create action group** blade, select **Next: Actions  >**.
 

From 80da9f65893bd07d5173efc331725d452de94431 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:18:08 -0700
Subject: [PATCH 21/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..734339b2 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -223,7 +223,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
 
 1. On the **Notifications** tab of the **Create action group** blade, in the **Notification type** drop-down list, select **Email/SMS/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon.
 
-1. On the **Email/SMS/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create action group** blade, select **Next: Actions  >**.
+1. On the **Email/SMS message/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create an action group** blade, select **Next: Actions  >**.
 
 1. On the **Actions** tab of the **Create action group** blade, review items available in the **Action type** drop-down list without making any changes and select **Review + create**.
 

From d3292104b06d5a2bfaffd94480d2168d42ace8d3 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:23:06 -0700
Subject: [PATCH 22/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..ea9a319c 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -229,7 +229,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
 
 1. On the **Review + create** tab of the **Create action group** blade, select **Create**.
 
-1. Back on the **Create alert rule** blade, in the **Alert rule details** section, specify the following settings (leave others with their default values):
+1. Back on the **Create alert rule** blade, click **Next: Details >**, and in the **Alert rule details** section, specify the following settings (leave others with their default values):
 
     | Settings | Value |
     | --- | --- |

From 246c40fe98c27df77dc5aff4b3ea4a1f3060b501 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:24:09 -0700
Subject: [PATCH 23/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..772d4e5f 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -234,7 +234,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
     | Settings | Value |
     | --- | --- |
     | Alert rule name | **CPU Percentage above the test threshold** |
-    | Description | **CPU Percentage above the test threshold** |
+    | Alert rule description | **CPU Percentage above the test threshold** |
     | Severity | **Sev 3** |
     | Enable rule upon creation | **Yes** |
 

From 12c00dec55250a3c14a80a7e3de14143529f4dcc Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:25:00 -0700
Subject: [PATCH 24/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..442046f4 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -236,7 +236,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
     | Alert rule name | **CPU Percentage above the test threshold** |
     | Description | **CPU Percentage above the test threshold** |
     | Severity | **Sev 3** |
-    | Enable rule upon creation | **Yes** |
+    | Enable upon creation | **Yes** |
 
 1. Click **Create alert rule**.
 

From ddd5ad913a0d60d5223de223ce80de4a46b8dd2b Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:26:49 -0700
Subject: [PATCH 25/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..7ab291a7 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -238,7 +238,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
     | Severity | **Sev 3** |
     | Enable rule upon creation | **Yes** |
 
-1. Click **Create alert rule**.
+1. Click **Review + create** and on the **Review + create** tab click **Create**.
 
     >**Note**: It can take up to 10 minutes for a metric alert rule to become active.
 

From 395aba3af1377a742ac54cfce657e537feaa83c3 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:29:03 -0700
Subject: [PATCH 26/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..a4d49da6 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -278,7 +278,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
 
     >**Note**: You might need to click **Get Started** if this is the first time you access Log Analytics.
 
-1. If necessary, click **Select scope**, on the **Select a scope** blade, select the **Recent** tab, select **az104-11-vm0**, and click **Apply**.
+1. If necessary, click **Select scope**, on the **Select a scope** blade, select the **Recent** tab, select **az104-11-rg0**, and click **Apply**.
 
 1. In the query window, paste the following query, click **Run**, and review the resulting chart:
 

From 75f56ba7fe923fa350ac8af83f91e3d5b15e1a07 Mon Sep 17 00:00:00 2001
From: Mark Beasley <87342636+gmbeasley@users.noreply.github.com>
Date: Fri, 28 Jan 2022 14:30:08 -0700
Subject: [PATCH 27/28] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 80f2ced3..b14286a6 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -292,7 +292,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
    | render timechart
    ```
 
-1. Click **Queries** in the toolbar, on the **Queries** pane, locate the **Track VM availability** tile, click the **Run** command button in the tile, and review the results.
+1. Click **Queries** in the toolbar, on the **Queries** pane, locate the **Track VM availability** tile and double-click it to fill the query window, click the **Run** command button in the tile, and review the results.
 
 1. On the **New Query 1** tab, select the **Tables** header, and review the list of tables in the **Virtual machines** section.
 

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 28/28] 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**.