From e89d6e5a19b09e92c752dc5343cbbdb8154851c3 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Thu, 20 Jun 2024 16:00:10 -0700
Subject: [PATCH] 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 d2a2e664..fca85e5f 100644
--- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
+++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
@@ -277,7 +277,7 @@ In this task, you scale the virtual machine scale set using a custom scale rule.
 
 1. Select **Go to resource** or search for and select the **vmss1** scale set.
 
-1. Choose **Scaling** from the menu on the left-hand side of the scale set window.
+1. Choose **Availability + Scaling** from the left side menu, then choose **Scaling**.
 
 >**Did you know?** You can **Manual scale** or **Custom autoscale**. In scale sets with a small number of VM instances, increasing or decreasing the instance count (Manual scale) may be best. In scale sets with a large number of VM instances, scaling based on metrics (Custom autoscale) may be more appropriate.