Additional edits.

Author: TimShererWithAquent

articles/lab-services/class-type-ethical-hacking.md

@@ -15,9 +15,7 @@ ms.date: 03/04/2024
 
 This article shows you how to set up a class that focuses on the forensics side of ethical hacking with Azure Lab Services. In an ethical hacking class, students can learn modern techniques for defending against vulnerabilities. Penetration testing, a practice that the ethical hacking community uses, occurs when someone attempts to gain access to the system or network to demonstrate vulnerabilities that a malicious attacker might exploit.
 
-[!INCLUDE [preview note](./includes/lab-services-new-update-focused-article.md)]
-
-Each student gets a Windows host virtual machine (VM) that has two nested virtual machines: one VM with Metasploitable3 image and another VM with the Kali Linux image. Use the Metasploitable VM for exploiting purposes. The Kali VM provides access to the tools you need to run forensic tasks.
+Each student gets a Windows host virtual machine (VM) that has two nested virtual machines: one VM with Metasploitable3 image and another VM with the Kali Linux image. Use the Metasploitable VM to try exploitation tasks. The Kali VM provides access to the tools you need to run forensic tasks.
 
 ## Prerequisites
 
@@ -33,6 +31,8 @@ Each student gets a Windows host virtual machine (VM) that has two nested virtua
 | Virtual machine (VM) size | Medium (Nested Virtualization) |
 | VM image | Windows 11 |
 
+[!INCLUDE [preview note](./includes/lab-services-new-update-focused-article.md)]
+
 ## Configure your template
 
 [!INCLUDE [configure template vm](./includes/lab-services-class-type-template-vm.md)]
@@ -61,7 +61,7 @@ To configure the template VM, complete the following tasks:
 
 Kali is a Linux distribution that includes tools for penetration testing and security auditing.
 
-The Rapid7 Metasploitable image is an image purposely configured with security vulnerabilities. Use this image to test and find issues. The following instructions show you how to use a precreated Metasploitable image. However, if you need a newer version of the Metasploitable image, see [https://github.com/rapid7/metasploitable3](https://github.com/rapid7/metasploitable3).
+The Rapid7 Metasploitable image is an image purposely configured with security vulnerabilities. Use this image to test and find issues. The following instructions show you how to set up a particular Metasploitable image. If you need a newer version of the Metasploitable, see [https://github.com/rapid7/metasploitable3](https://github.com/rapid7/metasploitable3).
 
 - To install Kali Linux and Metasploitable on the template VM, run the following command:
 
@@ -109,7 +109,7 @@ To install the Metasploitable nested VM on the template VM:
    1. Select **Download Metasploitable Now**.
    1. When the download finishes, extract the zip file, and remember the location of the *Metasploitable.vmdk* file.
 
-1. Convert the extracted vmdk file to a Hyper-V vhdx file with StarWind V2V Converter.
+1. Convert the extracted *.vmdk* file to a Hyper-V *.vhdx* file with StarWind V2V Converter.
 
    1. Download and install [StarWind V2V Converter](https://www.starwindsoftware.com/starwind-v2v-converter#download).
    1. Start **StarWind V2V Converter**.

articles/lab-services/how-to-enable-nested-virtualization-template-vm-using-script.md

@@ -34,53 +34,53 @@ For concepts, considerations, and recommendations about nested virtualization, s
 To enable nested virtualization on the template VM, first connect to the VM by using a remote desktop (RDP) client. You can then apply the configuration changes by either running a PowerShell script or using Windows tools.
 
 > [!IMPORTANT]
-> It is recommend to use nested virtualization with Windows 11 to take advantage of the 'Default Switch' created when you install Hyper-V on a Windows client OS.  Nested virtualization on Windows Server OSes should be used when additional control over the network settings is required.
+> We recommend that you use nested virtualization with Windows 11. You can take advantage of the 'Default Switch' created when you install Hyper-V on a Windows client OS. You should use nested virtualization on Windows Server operating systems when you require additional control over the network settings.
 
 # [PowerShell](#tab/powershell)
 
 You can use a PowerShell script to set up nested virtualization on a template VM in Azure Lab Services. The following steps guide you through how to use the [Lab Services Hyper-V scripts](https://github.com/Azure/LabServices/tree/main/ClassTypes/PowerShell/HyperV). The script is intended for Windows 11.
 
 1. Follow these steps to [connect to and update the template machine](./how-to-create-manage-template.md#update-a-template-vm).
 
-1. Launch **PowerShell** in **Administrator** mode.
+1. Launch **PowerShell** as an Administrator.
 
 1. You might have to change the execution policy to successfully run the script. Run the following command:
 
     ```powershell
     Set-ExecutionPolicy bypass -force
     ```
 
-1. Download and run the script to enable the Hyper-V feature and tools.  
+1. Download and run the script to enable the Hyper-V feature and tools.
 
     ```powershell
     Invoke-WebRequest 'https://aka.ms/azlabs/scripts/hyperV-powershell' -Outfile SetupForNestedVirtualization.ps1
     .\SetupForNestedVirtualization.ps1
     ```
 
     > [!NOTE]
-    > The script might require you to restart the VM. If so, stop and start the template VM from the [Azure Lab Services website](https://labs.azure.com) and re-run the script until **Script completed** is seen in the output.
+    > The script might require you to restart the VM. If so, stop and start the template VM from the [Azure Lab Services website](https://labs.azure.com) and re-run the script until you see **Script completed** in the output.
 
 1. Don't forget to reset the execution policy.
 
     ```powershell
     Set-ExecutionPolicy default -force
     ```
 
-The template VM is now configured for use with nested virtualization and you can [create VMs](/windows-server/virtualization/hyper-v/get-started/create-a-virtual-machine-in-hyper-v?tabs=hyper-v-manager) inside it. Use the switch specified by the script when creating new Hyper-V VMs.
+The template VM is now configured for use with nested virtualization. You can [create VMs](/windows-server/virtualization/hyper-v/get-started/create-a-virtual-machine-in-hyper-v?tabs=hyper-v-manager) inside it. Use the switch specified by the script when creating new Hyper-V VMs.
 
 # [Windows tools](#tab/windows)
 
-You can set up nested virtualization on a template VM in Azure Lab Services using Windows features and tools directly. The following steps describe how to manually set up a Lab Services machine template with Hyper-V. Steps are intended for Windows 11.
+You can set up nested virtualization on a template VM in Azure Lab Services by using Windows features and tools directly. The following steps describe how to manually set up a Lab Services machine template with Hyper-V. These steps are intended for Windows 11.
 
 1. Open the **Settings** page.
 1. Select **Apps**.
 1. Select **Optional features**.
 1. Select **More Windows features** under the **Related features** section.
 1. The **Windows features** pop-up appears. Check the **Hyper-V** feature and select **OK**.
 1. Wait for the Hyper-V feature to be installed. When prompted to restart the VM, select **Don't restart**.
-1. Go to the [Azure Lab Services website](https://labs.azure.com) to stop and restart the template VM.
+1. To start and stop the template VM, go to the [Azure Lab Services website](https://labs.azure.com).
 
-The template VM is now configured to use nested virtualization and you can [create VMs](/windows-server/virtualization/hyper-v/get-started/create-a-virtual-machine-in-hyper-v?tabs=hyper-v-manager) inside it. Use 'Default Switch' when creating new nested VMs with Hyper-V.
+The template VM is now configured to use nested virtualization.  You can [create VMs](/windows-server/virtualization/hyper-v/get-started/create-a-virtual-machine-in-hyper-v?tabs=hyper-v-manager) inside it. Use Default Switch when you create new nested VMs with Hyper-V.
 
 ---
 
@@ -156,22 +156,22 @@ We recommend that you set Hyper-V VMs [automatic shutdown action set to shutdown
 
 ### Hyper-V is too slow
 
-Increase the number vCPUs and memory that is assigned to the Hyper-V VM in Hyper-V Manager. The total number of vCPUs can't exceed the number of cores of the host VM (lab VM). If you're using variable memory, the default option, increase the minimum amount of memory assigned to the VM. The maximum amount of assigned memory, if using variable memory, can exceed the amount of memory of the host VM. This approach allows greater flexibility when having to complete intensive operations on just one of the Hyper-V VMs.
+Increase the number vCPUs and memory that is assigned to the Hyper-V VM in Hyper-V Manager. The total number of vCPUs can't exceed the number of cores of the host VM (lab VM). If you're using variable memory, the default option, increase the minimum amount of memory assigned to the VM. The maximum amount of assigned memory, if you use variable memory, can exceed the amount of memory of the host VM. This approach allows greater flexibility when having to complete intensive operations on just one of the Hyper-V VMs.
 
 If you're using the **Medium (Nested Virtualization)** VM size for the lab, consider using the **Large (Nested Virtualization)** VM size instead to have more compute resources for each lab VM.
 
 ### Internet connectivity isn't working for nested VMs
 
 - Verify that you followed the previous steps for enabling nested virtualization. Consider using the PowerShell script option.
 
-- Check if the host VM (lab VM) has the DHCP role installed if you are using Windows Server.
+- Check if the host VM (lab VM) has the DHCP role installed if you're using Windows Server.
 
-  Running a lab VM as a DHCP server is an *unsupported* scenario. See [Can I deploy a DHCP server in a virtual network?](/azure/virtual-network/virtual-networks-faq) for details. Changing the settings of the lab VM can cause issues with other lab VMs.
+  Running a lab VM as a DHCP server isn't supported. See [Can I deploy a DHCP server in a virtual network?](/azure/virtual-network/virtual-networks-faq). Changing the settings of the lab VM can cause issues with other lab VMs.
 
 - Check the network adapter settings for the Hyper-V VM.
 
   - Set the IP address of the DNS server and DHCP server to [168.63.129.16](/azure/virtual-network/what-is-ip-address-168-63-129-16).
-  - If the guest VM IPv4 address is set manually, verify it is in the range of the NAT network connected to the Hyper-V switch.
+  - If the guest VM IPv4 address is set manually, verify that it's in the range of the NAT network connected to the Hyper-V switch.
   - Try enabling Hyper-V [DHCP guard](/archive/blogs/virtual_pc_guy/hyper-v-networkingdhcp-guard) and [Router guard](/archive/blogs/virtual_pc_guy/hyper-v-networkingrouter-guard).
 
     ```powershell
@@ -183,7 +183,7 @@ If you're using the **Medium (Nested Virtualization)** VM size for the lab, cons
 
 ### Can't start Hyper-V VMs
 
-You might choose to create a non-admin user when creating your lab. To be able to start or stop Hyper-V VMs, the non-admin user must be added to **Hyper-V Administrators** group. For more information about Hyper-V and non-admin users, see [Non-admin user](concept-nested-virtualization-template-vm.md#non-admin-user).
+You might choose to create a non-admin user when you create a lab. To be able to start or stop Hyper-V VMs, you must add such a user to the **Hyper-V Administrators** group. For more information about Hyper-V and non-admin users, see [Non-admin user](concept-nested-virtualization-template-vm.md#non-admin-user).
   
 ## Related content