review cx

Author: v-thepet

articles/devtest-labs/TOC.yml

@@ -139,7 +139,7 @@
       href: devtest-lab-store-secrets-in-key-vault.md
     - name: Attach and detach data disks
       href: devtest-lab-attach-detach-data-disk.md
-    - name: Start VMs using Automation runbooks
+    - name: Define start order for lab VMs
       href: start-machines-use-automation-runbooks.md
     - name: Import virtual machines from another lab
       href: import-virtual-machines-from-another-lab.md

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

@@ -2,7 +2,7 @@
 title: Create a lab virtual machine by using Azure PowerShell
 description: Learn how to use Azure PowerShell to create and manage virtual machines in Azure DevTest Labs.
 ms.topic: how-to
-ms.date: 03/16/2022
+ms.date: 03/17/2022
 ms.custom: devx-track-azurepowershell
 ---
 
@@ -112,7 +112,7 @@ Save the preceding script in a file named *Create-LabVirtualMachine.ps1*. Run th
 
 This section shows how to get the specific properties for the type of VM you want to create. You can get the properties from an Azure Resource Manager (ARM) template in the Azure portal, or by calling the DevTest Labs Azure REST API.
 
-### Get VM properties from the Azure portal
+### Use the Azure portal to get VM properties
 
 Creating a VM in the Azure portal generates an Azure Resource Manager (ARM) template that shows the VM's properties. Once you choose a VM base, you can see the ARM template and get the properties without actually creating the VM. This method is the easiest way to get the JSON VM description if you don't already have a lab VM of that type.
 
@@ -167,7 +167,7 @@ Creating a VM in the Azure portal generates an Azure Resource Manager (ARM) temp
 
 
 
-### Get VM properties by using the DevTest Labs Azure REST API
+### Use the DevTest Labs Azure REST API to get VM properties
 
 You can also call the DevTest Labs REST API to get the properties of existing lab VMs. You can use those properties to create more lab VMs of the same types.
 

articles/devtest-labs/start-machines-use-automation-runbooks.md

@@ -1,20 +1,20 @@
 ---
-title: Start machines in sequence with an Azure Automation runbook
+title: Define VM start order with Azure Automation
 description: Learn how to start virtual machines in a specific order by using Azure Automation runbooks in Azure DevTest Labs.
 ms.topic: how-to
-ms.date: 03/15/2022
+ms.date: 03/17/2022
 ms.custom: devx-track-azurepowershell
 ---
 
-# Start DevTest Labs VMs in sequence with an Azure Automation runbook
+# Define the startup order for DevTest Lab VMs with Azure Automation
 
 This article explains how to start up DevTest Labs virtual machines (VMs) in a specific order by using a PowerShell runbook in Azure Automation. The PowerShell script uses tags on lab VMs, so you can change the startup order without having to change the script.
 
 The DevTest Labs [autostart](devtest-lab-set-lab-policy.md#set-autostart) feature can configure lab VMs to start automatically at a specified time. However, sometimes you might want lab VMs to start in a specific sequence. For example, if a jumpbox VM in a lab is the access point to the other VMs, the jumpbox VM must start before the other VMs.
 
 ## Prerequisites
 
-- Apply the tag **StartupOrder** to all lab VMs with an appropriate startup value, 0 through 10. Designate any machines that don't need starting as -1.
+- [Create and apply a tag](devtest-lab-add-tag.md) called **StartupOrder** to all lab VMs with an appropriate startup value, 0 through 10. Designate any machines that don't need starting as -1.
 
 - Create an Azure Automation account by following instructions in [Create a standalone Azure Automation account](/azure/automation/automation-create-standalone-account). Choose the **Run As Accounts** option when you create the account.
 
@@ -24,7 +24,7 @@ The DevTest Labs [autostart](devtest-lab-set-lab-policy.md#set-autostart) featur
 1. On the **Runbooks** page, select **Create a runbook**.
 1. Follow the instructions in [Create an Automation PowerShell runbook using managed identity](../automation/learn/powershell-runbook-managed-identity.md) to create a PowerShell runbook. Populate the runbook with the following PowerShell script.
 
-### PowerShell script
+## Prepare the PowerShell script
 
 The following script takes the subscription name and the lab name as parameters. The script gets all the VMs in the lab and parses their tag information to create a list of VM names and their startup order. The script walks through the list in order and starts the VMs.
 
@@ -128,7 +128,7 @@ While ($current -le 10) {
 }
 ```
 
-## Alternatives
+## Run the PowerShell script
 
 - To run this script daily, [create a schedule](../automation/shared-resources/schedules.md#create-a-schedule) in the Automation Account, and [link the schedule to the runbook](../automation/shared-resources/schedules.md#link-a-schedule-to-a-runbook).