touchups

Author: v-thepet

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

@@ -14,9 +14,9 @@ ms.date: 04/02/2025
 
 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.
 
-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.
+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.
 
-Decomposing a deployment into 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).
+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)]  
 
@@ -31,15 +31,15 @@ The Azure Resource Group project template in Visual Studio makes it easy to deve
 - Adds the `_artifactsLocation` and `_artifactsLocationSasToken` parameters to the main template file.
 - Inserts the location and Shared Access Signature (SaS) token into the parameters file.
 
-The following nested template example shows a Git repository folder with a subfolder, *nestedtemplates*, that contains the nested template files *NestOne.json* and *NestOne.parameters.json*. You can add more than one nested template subfolder, but at only one level of nesting.
+The following screenshot shows the project structure in Visual Studio. The Git repository folder has a subfolder, *nestedtemplates*, that contains the nested template files *NestOne.json* and *NestOne.parameters.json*. You can add more than one nested template subfolder, but at only one level of nesting.
 
 :::image type="content" source="media/deploy-nested-template-environments/visual-studio-project-structure.png" alt-text="Screenshot that shows the nested template project structure in Visual Studio.":::
 
 ## 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 template code builds the URI for the secondary templates 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 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.
 
 ```json
 

articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md

@@ -29,7 +29,7 @@ In this article, you learn how to create an Azure DevTest Labs virtual machine (
 - A VHD file uploaded to the Azure Storage account for the lab. To upload a VHD file:
 
   1. Go to your lab storage account in the Azure portal and select **Upload**.
-  1. Browse to and select the VHD file, select the **uploads** container or create a new container named **uploads**, and then select **Upload**.
+  1. Browse to and select the VHD file, select the **uploads** container or create a new container named **uploads** for the file, and then select **Upload**.
 
   You can also upload a VHD file by following the instructions in any of these articles:
 
@@ -39,7 +39,7 @@ In this article, you learn how to create an Azure DevTest Labs virtual machine (
 
 ## Create a custom image
 
-The following Azure PowerShell steps create a DevTest Labs custom image from a VHD file by using a deployment template from the public [DevTest Labs template repository](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd).
+The following Azure PowerShell steps create a DevTest Labs custom image from an uploaded VHD file by using a deployment template from the public [DevTest Labs template repository](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd).
 
 1. After you sign in to Azure, select the subscription you want to use by running `Select-AzSubscription`. Replace the `<subscription ID>` placeholder with your subscription ID.
 
@@ -69,15 +69,15 @@ The following Azure PowerShell steps create a DevTest Labs custom image from a V
    $parameters = @{existingLabName="$($lab.Name)"; existingVhdUri=$vhdUri; imageOsType='windows'; isVhdSysPrepped=$false; imageName=$customImageName; imageDescription=$customImageDescription}
    ```
 
-1. Use [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment) to create the custom image by using a template according to the parameters.
+1. Run [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment) to create the custom image by using a template according to the parameters.
 
    ```powershell
    New-AzResourceGroupDeployment -ResourceGroupName $lab.ResourceGroupName -Name CreateCustomImage -TemplateUri 'https://raw.githubusercontent.com/Azure/azure-devtestlab/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd/azuredeploy.json' -TemplateParameterObject $parameters
    ```
 
 ## Use a PowerShell script
 
-You can combine the preceding steps to produce the following PowerShell script that creates a custom image from a VHD file. To use the script, replace the parameter values under the `# Values to change` comment with your own values.
+You can combine the preceding steps to produce an Azure PowerShell script that creates a custom image from a VHD file. To use the script, replace the parameter values under the `# Values to change` comment with your own values.
 
 ```powershell
 # Values to change

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

@@ -15,13 +15,18 @@ ms.date: 04/02/2025
 
 Azure DevTest Labs supports changing the size of a lab virtual machine (VM), based on changing needs for CPU, network, or disk performance. This article describes how to resize a lab VM.
 
-To resize a VM, you must be a lab administrator or an owner of the VM. If the lab sets an [allowed VM sizes](devtest-lab-set-lab-policy.md#set-allowed-virtual-machine-sizes) policy, you can resize the VM only to sizes that the policy permits.
+## Prerequisites
+
+- To resize a VM, you must be a lab administrator or an owner of the VM.
+- If the lab sets an [allowed VM sizes](devtest-lab-set-lab-policy.md#set-allowed-virtual-machine-sizes) policy, you can resize the VM only to sizes that the policy permits.
+
+## Stop the VM
 
 To avoid losing work, stop the VM before you resize it. To stop a VM, disconnect from it, and select **Stop** on the top toolbar of the VM's **Overview** page in the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
 
 :::image type="content" source="./media/devtest-lab-resize-vm/stop-vm.png" alt-text="Screenshot that shows selecting Stop on the Overview page for a VM.":::
 
-To resize a VM:
+## 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.":::
@@ -34,8 +39,10 @@ You can check the status of the resize operation in the **Notifications** window
 :::image type="content" source="./media/devtest-lab-resize-vm/resize-status.png" alt-text="Screenshot of the Notifications window that shows resizing status.":::
 
 >[!NOTE]
->If the resize operation fails with an error that **Resizing virtual machines with shared IP configuration is not supported**, you need to add and associate a Public IP address to the VM. For more information, see [Associate a public IP address to a virtual machine](/azure/virtual-network/ip-services/associate-public-ip-address-vm).
+>If the resize operation fails with an error that **Resizing virtual machines with shared IP configuration is not supported**, you need to add and associate a Public IP address to the VM before you can resize it. For more information, see [Associate a public IP address to a virtual machine](/azure/virtual-network/ip-services/associate-public-ip-address-vm).
+
+When the resize operation finishes, you can start the VM by selecting **Start** from the VM **Overview** page top toolbar, and then connect to the VM by selecting **Connect** in the toolbar.
 
-When the resize finishes, you can start the VM by selecting **Start** from the VM **Overview** page top toolbar, and then connect to the VM by selecting **Connect** in the toolbar.
+## Related content
 
 For more information about the resize feature for Azure VMs, see [Resize virtual machines](https://azure.microsoft.com/blog/resize-virtual-machines/).

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

@@ -61,22 +61,22 @@ 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 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 for the plan named `main.tfplan`. You can review the file to ensure that the plan is exactly what you want to apply.
 
 ```console
 terraform plan -out main.tfplan
 ```
 
 ## Apply the Terraform execution plan
 
-Run [terraform apply](https://www.terraform.io/docs/commands/apply.html) to apply the execution plan to your cloud infrastructure. The example `terraform apply` command assumes you previously ran `terraform plan -out main.tfplan`.
-
-If you specify a different filename for the `-out` parameter in `terraform_plan`, use that filename in the call to `terraform apply`. If you don't use the `-out` parameter in `terraform_plan`, call `terraform apply` without any parameters.
+Run [terraform apply](https://www.terraform.io/docs/commands/apply.html) to apply the execution plan to your cloud infrastructure. The following `terraform apply` command assumes you previously ran `terraform plan -out main.tfplan`.
 
 ```console
 terraform apply main.tfplan
 ```
 
+If you specify a different filename for the `-out` parameter in `terraform_plan`, use that filename in the call to `terraform apply`. If you don't use the `-out` parameter in `terraform_plan`, call `terraform apply` without any parameters.
+
 ## Verify the results
 
 There are several ways to verify the results of the Terraform deployment. If you have Azure CLI available, you can use [az lab vm list](/cli/azure/lab/vm#az-lab-vm-list) to get the names of the resource group and lab that Terraform created.