Additional edits.

Author: TimShererWithAquent

articles/lab-services/class-type-networking-gns3.md

@@ -8,14 +8,14 @@ author: RoseHJM
 ms.author: rosemalcolm
 ms.topic: how-to
 ms.date: 03/06/2024
-#customer intent: As an instructor, I want to create lab virtual machines with GNS3 so that students can start to learn about networking with GNS3 in a standard configuration.
+#customer intent: As an educator, I want to create lab virtual machines with GNS3 so that students can learn about networking with GNS3 in a standard configuration.
 ---
 
 # Set up a lab to teach a networking class with GNS3 in Azure Lab Services
 
 This article shows you how to set up a class to emulate, configure, test, and troubleshoot networks with GNS3 software in Azure Lab Services.
 
-This article has two sections. The first section covers how to create the lab. The second section covers how to create the template machine with nested virtualization enabled and with GNS3 installed and configured.
+This article has two sections. The first section covers how to create the lab. The second section covers how to configure the template machine with nested virtualization enabled and with GNS3 installed and configured.
 
 ## Prerequisites
 
@@ -59,15 +59,15 @@ If you create a lab template VM with an account without administrator privileges
 
 1. To install GNS3 on Windows, follow the detailed instructions on [the GNS3 website](https://docs.gns3.com/docs/getting-started/installation/windows).
 
-1. Make sure to select **GNS3 VM** in the **Choose Components** page:
+    1. Make sure to select **GNS3 VM** in the **Choose Components** page:
 
-    :::image type="content" source="./media/class-type-networking-gns3/gns3-select-vm.png" alt-text="Screenshot that shows the Choose Components page in the GNS3 installation wizard, with the GNS3 VM option selected." lightbox="./media/class-type-networking-gns3/gns3-select-vm.png":::
+        :::image type="content" source="./media/class-type-networking-gns3/gns3-select-vm.png" alt-text="Screenshot that shows the Choose Components page in the GNS3 installation wizard, with the GNS3 VM option selected." lightbox="./media/class-type-networking-gns3/gns3-select-vm.png":::
 
-1. On the **GNS3 VM** page, select the **Hyper-V** option:
+    1. On the **GNS3 VM** page, select the **Hyper-V** option:
 
-    :::image type="content" source="./media/class-type-networking-gns3/gns3-vm-hyper-v.png" alt-text="Screenshot that shows the GNS3 VM page in the GNS3 installation wizard, with the Hyper-V option selected." lightbox="./media/class-type-networking-gns3/gns3-vm-hyper-v.png":::
+        :::image type="content" source="./media/class-type-networking-gns3/gns3-vm-hyper-v.png" alt-text="Screenshot that shows the GNS3 VM page in the GNS3 installation wizard, with the Hyper-V option selected." lightbox="./media/class-type-networking-gns3/gns3-vm-hyper-v.png":::
 
-    When you select the Hyper-V option, the installer downloads the PowerShell script and VHD files to create the GNS3 VM in the Hyper-V manager.
+        When you select the Hyper-V option, the installer downloads the PowerShell script and VHD files to create the GNS3 VM in the Hyper-V manager.
 
 1. Continue the installation with the default values.
 
@@ -82,11 +82,11 @@ To create the GNS 3 VM:
 
 1. Connect to the template VM by using Remote Desktop.
 
-1. Extract all files in the *GNS3.VM.Hyper-V.2.2.17.zip* file. If the template VM has a non-admin account for lab users, extract the files in a location accessible to the non-admin account.
+1. Extract all files in the *GNS3.VM.Hyper-V.2.2.x.zip* file. If the template VM has a non-admin account for lab users, extract the files in a location accessible to the non-admin account.
 
 1. Right-select the *create-vm.ps1* PowerShell script, and then select **Run with PowerShell**.
 
-1. When the `Execution Policy Change` request shows, enter **Y** to execute the script.
+1. When the `Execution Policy Change` request appears, enter **Y** to execute the script.
 
     :::image type="content" source="./media/class-type-networking-gns3/powershell-execution-policy-change.png" alt-text="Screenshot that shows the PowerShell command line, asking for an Execution Policy change." lightbox="./media/class-type-networking-gns3/powershell-execution-policy-change.png":::
 
@@ -120,13 +120,13 @@ After you install GNS3 and add the GNS3 VM, configure GNS 3 to use the Hyper-V v
 
 Next, you can add appliances for the class. To install appliances from the GNS3 marketplace, follow the detailed steps from [the GNS3 documentation](https://docs.gns3.com/docs/using-gns3/beginners/install-from-marketplace).
 
-If the template VM has a non-admin account for lab users, install the appliances to a location accessible to the account. Optionally, you can set the preferences for the admin and non-admin user to look for appliances and projects in a location accessible by both users.
+If the template VM has a non-admin account for lab users, install the appliances to a location accessible to the account. Optionally, you can set the preferences for the administrator and non-admin user to look for appliances and projects in a location accessible by both users.
 
 ### Prepare to publish template
 
-Now that you set up the template virtual machine, verify the following key points before you publish the template:
+After you set up the template virtual machine, verify the following key points before you publish the template:
 
-- Make sure that the GNS3 VM is shut down or turned off. Publishing while the VM is still running, corrupts the virtual machine.
+- Make sure that the GNS3 VM is shut down or turned off. Publishing while the VM is still running corrupts the virtual machine.
 - Stop GNS3. Publishing while GNS3 is running can lead to unintended side effects.
 - Clean up any installation files or other unnecessary files from the template VM.
 

articles/lab-services/connect-virtual-machine-windows-rdp.md

@@ -8,7 +8,7 @@ author: RoseHJM
 ms.author: rosemalcolm
 ms.topic: how-to
 ms.date: 03/06/2024
-#customer intent: As a learner, I want to connect to virtual machines in a lab by using RDP in order to use the lab resources. 
+#customer intent: As a student, I want to connect to virtual machines in a lab by using RDP in order to use the lab resources. 
 ---
 
 # Connect to a VM using Remote Desktop Protocol on Windows
@@ -43,7 +43,7 @@ To connect to a lab VM in Azure Lab Services:
 
 The RDP client software has various settings for optimizing your connection experience. The default settings optimize your experience based on your network connection. Typically, you don't need to change the default settings.
 
-Learn more about the [RDP client's **Experience** settings](/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts#client-experience-settings).
+Learn more about the [RDP client's Experience settings](/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts#client-experience-settings).
 
 If you're using a Linux lab VM with a graphical desktop and the RDP client, the following settings might help to optimize performance:
 

articles/lab-services/how-to-access-lab-virtual-machine.md

@@ -13,7 +13,7 @@ ms.date: 03/06/2024
 
 # Access a lab virtual machine in Azure Lab Services
 
-This article describes how you can access your lab virtual machines (VMs) in Azure Lab Services. Use Teams, Canvas, or the Azure Lab Services website to view, start, stop, and connect to a lab virtual machine.
+This article shows you how to access your lab virtual machines (VMs) in Azure Lab Services. Use Teams, Canvas, or the Azure Lab Services website to view, start, stop, and connect to a lab virtual machine.
 
 ## Prerequisites
 
@@ -65,7 +65,7 @@ To access your lab in Teams:
 
     :::image type="content" source="./media/how-to-access-lab-virtual-machine/teams-view-lab.png" alt-text="Screenshot of lab in Teams after you publish it." lightbox="./media/how-to-access-lab-virtual-machine/teams-view-lab.png":::
 
-    You might see a message that the lab isn't available. This error can occur when the lab isn't published yet, or if the Teams membership information still needs to synchronize.
+    You might see a message that the lab isn't available. This error can occur when the lab isn't published yet or if the Teams membership information still needs to synchronize.
 
 # [Canvas](#tab/canvas)
 
@@ -91,20 +91,20 @@ When you access your lab, either through the Azure Lab Services website, Microso
 
 For each lab VM, you can view the following information:
 
-- Lab name: this name is assigned by the lab creator.
-- Operating system: an icon represents the operating system of the lab VM.
-- Quota hours: a progress bar shows your assigned and consumed quota hours. Learn more about the [quota hours](#view-quota-hours).
-- Lab VM status: indicates whether the lab VM is starting, running, or stopped.
+- Lab name. The lab creator assigns this name.
+- Operating system. An icon represents the operating system of the lab VM.
+- Quota hours. A progress bar shows your assigned and consumed quota hours. Learn more about the [quota hours](#view-quota-hours).
+- Lab VM status. Indicates whether the lab VM is starting, running, or stopped.
 
 You can also perform specific actions on the lab VM:
 
-- Start or stop the lab VM: learn more about [starting and stopping a lab VM](#start-or-stop-the-lab-vm).
-- Connect to the lab VM: select the computer icon to connect to the lab VM with remote desktop or SSH. Learn more about [connecting to the lab VM](./connect-virtual-machine.md).
-- Redeploy or reimage the lab VM: learn more how you [redeploy or reimage the lab VM](./how-to-reset-and-redeploy-vm.md) when you experience problems.
+- Start or stop the lab VM. Learn more about [starting and stopping a lab VM](#start-or-stop-the-lab-vm).
+- Connect to the lab VM. Select the computer icon to connect to the lab VM with remote desktop or SSH. Learn more about [connecting to the lab VM](./connect-virtual-machine.md).
+- Redeploy or reimage the lab VM. Learn more how you can [redeploy or reimage the lab VM](./how-to-reset-and-redeploy-vm.md) when you experience problems.
 
 ## View quota hours
 
-Quota hours are the extra time allotted to you outside of the [scheduled time](./classroom-labs-concepts.md#schedule) for the lab. For example, the time outside of classroom time, to complete homework.
+Quota hours are the extra time allotted to you outside of the [scheduled time](./classroom-labs-concepts.md#schedule) for the lab. For example, the time outside of classroom time to complete homework.
 
 On the lab VM tile, you can view your consumption of [quota hours](how-to-manage-lab-users.md#set-quotas-for-users) in the progress bar. The progress bar color and the message give an indication of the usage:
 

articles/lab-services/how-to-request-capacity-increase.md

@@ -8,12 +8,12 @@ ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
 ms.date: 03/06/2024
-#customer intent: As a subscription owner for labs, I want to learn how to request an increase in cores available for my subscription in order to meet my lab needs.
+#customer intent: As an administrator and subscription owner, I want to learn how to request an increase in cores available for my subscription in order to meet my lab needs.
 ---
 
 # Request a core limit increase
 
-This article describes how to submit a support request to increase the number of cores for Azure Lab Services in your Azure subscription. First, collect the necessary information for the request.
+This article describes how you can submit a support request to increase the number of cores for Azure Lab Services in your Azure subscription. First, collect the necessary information for the request.
 
 When you reach the cores limit for your subscription, you can request a core limit increase to continue using Azure Lab Services. An increase is sometimes called an *increase in capacity* or a *quota increase*. The request process allows the Azure Lab Services team to ensure that your subscription isn't involved in any cases of fraud or unintentional, sudden large-scale deployments.
 
@@ -23,7 +23,7 @@ When you reach the cores limit for your subscription, you can request a core lim
 
 ## Prepare to submit a request
 
-Before you create a support request for a core limit increase, you need to gather additional information, such as the number and size of cores and the Azure regions. You might also have to do some preparation before you create the request.
+Before you create a support request for a core limit increase, gather necessary information, such as the number and size of cores and the Azure regions. You might also have to do some preparation before you create the request.
 
 ## [Lab plan](#tab/Labplans/)
 
@@ -37,11 +37,11 @@ Before you calculate the number of extra cores that you need, verify the capacit
 
 ### Determine the regions for your labs
 
-Azure Lab Services resources can exist in many regions. You can choose to deploy resources in multiple regions close to the lab users. For more information about Azure regions, how they relate to global geographies, and which services are available in each region, see [Azure global infrastructure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
+Azure Lab Services resources can exist in different regions. You can choose to deploy resources in multiple regions close to the lab users. For more information about Azure regions, how they relate to global geographies, and which services are available in each region, see [Azure global infrastructure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
 
 ### Determine the number of VM cores in your request
 
-In your support request, provide the *total* number of cores. This total includes both your existing number of cores and the cores you want to add.
+In your support request, provide the *total* number of cores. This total includes both your existing cores and the cores you want to add.
 
 Azure Lab Services groups VM sizes together in size groups:
 
@@ -53,11 +53,7 @@ Azure Lab Services groups VM sizes together in size groups:
 
 You request VM cores for a specific Azure region. When you select the region in the support request, you can view your current usage and current limit per size group.
 
-To determine the total number of cores for your request, use this equation:
-
-```output
-total VM cores = (current # cores for the size group) + ((# cores for the selected VM size) * (# VMs))`
-```
+To determine the total number of cores for your request, use this equation: `total VM cores = (current # cores for the size group) + ((# cores for the selected VM size) * (# VMs))`
 
 For example, you need more capacity for 20 *Medium* VMs. You already have the following VMs:
 
@@ -67,19 +63,19 @@ For example, you need more capacity for 20 *Medium* VMs. You already have the fo
 | Medium    | 4            | 20    | 80          |
 | Small GPU | 6            | 5     | 30          |
 
-The current #cores for the Small/Medium/Large size group is `20 (Small) + 80 (Medium) = 100 cores`. You don't count the *Small GPU* cores because they're in a different size group.
+The current number of cores for the Small/Medium/Large size group is `20 (Small) + 80 (Medium) = 100 cores`. You don't count the *Small GPU* cores because they're in a different size group.
 
 The total number of VM cores for 20 more Medium VMs is `100 + (4 cores per Medium VM) * 20 = 180 cores`.
 
 ## [Lab account](#tab/LabAccounts/)
 
 ### Determine the regions for your labs
 
-Azure Lab Services resources can exist in many regions. You can choose to deploy resources in multiple regions close to the lab users. For more information about Azure regions, how they relate to global geographies, and which services are available in each region, see [Azure global infrastructure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
+Azure Lab Services resources can exist in different regions. You can choose to deploy resources in multiple regions close to the lab users. For more information about Azure regions, how they relate to global geographies, and which services are available in each region, see [Azure global infrastructure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
 
 ### Determine the number of VM cores in your request
 
-In your support request, you need to provide the number of *extra* VM cores. Each VM size has a number of VM cores. Azure Lab Services groups VM sizes together in size groups. You request VM cores for a specific size group.
+In your support request, provide the number of *additional* VM cores. Each VM size has a number of VM cores. Azure Lab Services groups VM sizes together in size groups. You request VM cores for a specific size group.
 
 - Small / Medium / Large cores
 - Medium (Nested Virtualization) / Large (Nested Virtualization) cores
@@ -119,7 +115,7 @@ You can follow these steps to request a core limit increase:
 
 ## Make core limit increase request
 
-When you request a core limit increase, supply information to help the Azure Lab Services team evaluate and act on your request as quickly as possible. The more information you can supply and the earlier you supply it, the quicker the Azure Lab Services team can process your request.
+When you request a core limit increase, supply information to help the Azure Lab Services team evaluate and act on your request as quickly as possible. The more information you supply and the earlier you supply it, the quicker the Azure Lab Services team can process your request.
 
 Depending on whether you use lab accounts or lab plans, you need to provide different information on the **Quota details** page.
 
@@ -133,7 +129,7 @@ Depending on whether you use lab accounts or lab plans, you need to provide diff
 | **Region** | Select the region in the [Azure geography](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=lab-services) where you want the extra cores. |
 | **Does your virtual network reside in the same region as above?** | Select *Yes*, *No*, or *N/A*, depending on whether you use [advanced networking](./how-to-connect-peer-virtual-network.md) and have virtual networks in the region you selected. |
 | **Virtual machine size** | Select the virtual machine size that you require for the new cores. |
-| **Requested total core limit** | Enter the total number of cores you require. This number includes your existing cores + the number of extra cores you're requesting. To learn how to calculate the total number of cores, see [Determine the total number of cores in your request](#prepare-to-submit-a-request). |
+| **Requested total core limit** | Enter the total number of cores you require. This number includes your existing cores and the number of extra cores you're requesting. To learn how to calculate the total number of cores, see [Determine the total number of cores in your request](#prepare-to-submit-a-request). |
 
 #### [Lab account](#tab/LabAccounts/)
 
@@ -147,7 +143,7 @@ Depending on whether you use lab accounts or lab plans, you need to provide diff
 | **Virtual network regions** | Select one or more alternate regions in the [Azure geography](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=lab-services) where you might host virtual networks for [advanced networking](./how-to-connect-peer-virtual-network.md). |
 | **Virtual machine size** | Select the VM size for which you need more capacity. |
 | **Requested additional core limit** | Enter the number of extra cores for your subscription. |
-| **What is the lab account name?** | Only applies if you're adding cores to an existing lab. Select the lab account name. |
+| **What is the lab account name?** | Select the lab account name. This option only applies if you're adding cores to an existing lab. |
 | **What's the month-by-month usage plan for the requested cores?** | Enter the rate at which you want to add the extra cores, on a monthly basis. |
 | **Additional details** | Provide more information to make it easier for the Azure Lab Services team to process your request. For example, you could include your preferred date for the new cores to be available or if you plan to use GPU VM sizes. |
 

articles/lab-services/includes/lab-services-request-capacity-best-practices.md

@@ -1,8 +1,6 @@
 ---
 ms.service: lab-services
 ms.topic: include
-author: ntrogh
-ms.author: nicktrog
 ms.date: 12/01/2022
 ---