final touchups

Author: v-thepet

articles/devtest-labs/deploy-nested-template-environments.md

@@ -12,19 +12,19 @@ ms.date: 04/02/2025
 
 #  Nested templates in DevTest Labs environments
 
-Azure DevTest Labs *environments* consist of multiple infrastructure-as-a-service (IaaS) virtual machines (VMs) with platform-as-a-service (PaaS) resources installed. You can provision these PaaS and IaaS resources by using Azure Resource Manager (ARM) templates.
+Azure DevTest Labs *environments* consist of multiple infrastructure-as-a-service (IaaS) virtual machines (VMs) with platform-as-a-service (PaaS) resources installed. You can provision DevTest Labs environments by using Azure Resource Manager (ARM) templates.
 
-You can decompose a deployment into a set of targeted, purpose-specific templates to provide testing, reuse, and readability benefits. A *nested deployment* runs secondary ARM templates from within a main template. This article shows an example of using nested templates to deploy a DevTest Labs environment.
+This article describes using *nested templates* to deploy a DevTest Labs environment. A nested deployment runs secondary ARM templates from within a main template. Using a set of targeted, purpose-specific templates provides testing, reuse, and readability benefits. 
 
 For general information about nested templates, including code samples, see [Use linked and nested templates when deploying Azure resources](/azure/azure-resource-manager/templates/linked-templates).
 
 [!INCLUDE [direct-azure-deployment-environments](includes/direct-azure-deployment-environments.md)]  
 
 ## Nested template deployment with Visual Studio
 
-In DevTest Labs, you can store ARM templates in a Git repository that you link to a lab. When you use a linked repository template to create a new DevTest Labs environment, the deployment copies the template files into the lab's Azure Storage container.
+The Azure Resource Group project template in Visual Studio makes it easy to develop and debug nested templates. In DevTest Labs, you can store ARM templates in a Git repository linked to a lab. When you use a repository template to create an environment, DevTest Labs copies the template files into the lab's Azure Storage container.
 
-The Azure Resource Group project template in Visual Studio makes it easy to develop and debug nested templates. When you add a nested template file to the lab repository and add nested template code to the main *azuredeploy.json* template file, Visual Studio automatically takes the following actions:
+When you add a nested template to a lab repository and main *azuredeploy.json* template file, Visual Studio automatically takes the following actions:
 
 - Adds a subfolder for the secondary template and parameters files, and copies the subfolder to the lab storage container.
 - Adds variables for the nested template folder and files to the `variables` section of the main template file.
@@ -37,9 +37,9 @@ The following screenshot shows the project structure in Visual Studio. The Git r
 
 ## Nested deployment example
 
-The following example *azuredeploy.json* main template file shows the code for a nested deployment. The main template file links to the nested templates.
+The following example *azuredeploy.json* main template file shows the code for a nested deployment. The main template file defines links to the nested template.
 
-The template code builds the URI for the secondary templates link by concatenating the artifacts location, nested template folder, nested template filename, and artifacts Shared Access Signature (SaS) token location. The URI for the secondary parameters file uses the artifacts location, nested template folder, nested parameter filename, and artifacts SaS token location.
+The link URI for the secondary template concatenates the artifacts location, nested template folder, nested template filename, and artifacts Shared Access Signature (SaS) token location. The URI for the secondary parameters file uses the artifacts location, nested template folder, nested parameter filename, and artifacts SaS token location.
 
 ```json
 

articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md

@@ -10,7 +10,7 @@ ms.custom: UpdateFrequency2
 #customer intent: As a lab administrator, I want to create custom images from existing VMs so I can make the custom images available to lab users as bases for creating more VMs.
 ---
 
-# Create a custom image from a VM
+# Create a custom image from a VM in DevTest Labs
 
 In this article, you learn how to create a custom image from a provisioned Azure DevTest Labs virtual machine (VM). The custom image includes the OS disk, attached data disks, and any artifacts associated with the VM. Lab users can use the custom image to create identical provisioned lab VMs.
 

articles/devtest-labs/devtest-lab-resize-vm.md

@@ -29,9 +29,11 @@ To avoid losing work, stop the VM before you resize it. To stop a VM, disconnect
 ## Resize the VM
 
 1. On the VM's **Overview** page, select **Size** under **Settings** in the left navigation menu.
+
    :::image type="content" source="./media/devtest-lab-resize-vm/size-menu.png" alt-text="Screenshot that shows selecting Size in the VM's left navigation.":::
 
 1. On the **Select a VM size** screen, select a new size for your VM, and then select **Select**.
+
    :::image type="content" source="./media/devtest-lab-resize-vm/select-size.png" alt-text="Screenshot that shows selecting a V M size.":::
 
 You can check the status of the resize operation in the **Notifications** window.

articles/devtest-labs/quickstarts/create-lab-windows-vm-terraform.md

@@ -61,7 +61,7 @@ terraform init -upgrade
 
 Run [terraform plan](https://www.terraform.io/docs/commands/plan.html) to create an execution plan. The `terraform plan` command creates an execution plan, but doesn't execute it. Instead, it determines what actions are necessary to create the configuration specified in your configuration files.
 
-This pattern allows you to verify whether the execution plan matches your expectations before making any changes to actual resources. Use the optional `-out` parameter to specify an output file for the plan named `main.tfplan`. You can review the file to ensure that the plan is exactly what you want to apply.
+This pattern allows you to verify whether the execution plan matches your expectations before making any changes to actual resources. Use the optional `-out` parameter to specify an output file named `main.tfplan` for the plan. You can review the output file to ensure that the plan is exactly what you want to apply.
 
 ```console
 terraform plan -out main.tfplan