changes

Author: v-thepet

articles/devtest-labs/devtest-lab-reference-architecture.md

@@ -25,7 +25,7 @@ This DevTest Labs enterprise reference architecture has the following components
 
 - VMs and other software-as-a-service (SaaS), infrastructure-as-a-service (IaaS), and PaaS resources.
 
-  DevTest Labs instances contain VMs and other Azure resources like PaaS environments and VM artifacts. Artifacts are tools, actions, or software to add to lab VMs. 
+  DevTest Labs instances contain VMs and other Azure resources like PaaS environments and VM artifacts. Artifacts are actions to take or tools and software to add to lab VMs.
 
 - [Azure Active Directory (Azure AD)](/azure/active-directory/fundamentals/active-directory-whatis) for identity management.
 
@@ -63,15 +63,15 @@ DevTest Labs has no built-in quotas or limits, but other Azure resources that la
   Two strategies can help you stay under resource group limits:
 
   - [All VMs go in the same resource group](resource-group-control.md). This strategy helps you meet the resource group limit, but it affects the resource-type-per-resource-group limit.
-  - [Use shared Public IPs](devtest-lab-shared-ip.md). If VMs are allowed to have public IP addresses, put all VMs of the same size and region into the same resource group. This configuration helps meet both resource group quotas and resource-type-per-resource-group quotas.
+  - [Use shared public IPs](devtest-lab-shared-ip.md). If VMs are allowed to have public IP addresses, put all VMs of the same size and region into the same resource group. This configuration helps meet both resource group quotas and resource-type-per-resource-group quotas.
 
 - Resources per resource group per resource type. The default limit for [resources per resource group per resource type is 800](../azure-resource-manager/management/azure-subscription-service-limits.md#resource-group-limits).  Putting all VMs in the same resource group hits this limit much sooner, especially if the VMs have many extra disks.
 
 - Storage accounts. Every lab in DevTest Labs comes with a storage account. The Azure quota for [number of storage accounts per region per subscription is 250](../azure-resource-manager/management/azure-subscription-service-limits.md#storage-limits). So the maximum number of DevTest Labs in one region is also 250.
 
 - Role assignments. A role assignment gives a user or principal access to a resource. Azure has a limit of [2,000 role assignments per subscription](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-rbac-limits).
 
-  By default, DevTest Labs creates a resource group for each VM. The VM creator gets *owner* permission for the VM and *reader* permission to the resource group. So each new VM uses two role assignments. Granting user permissions to the lab also uses role assignments.
+  By default, DevTest Labs creates a resource group for each lab VM. The VM creator gets *owner* permission for the VM and *reader* permission to the resource group. So each lab VM uses two role assignments. Granting user permissions to the lab also uses role assignments.
 
 - API reads/writes. You can automate Azure and DevTest Labs by using REST APIs, PowerShell, Azure CLI, and Azure SDK. Each Azure subscription allows up to [12,000 read requests and 1,200 write requests per hour](../azure-resource-manager/management/request-limits-and-throttling.md). By automating DevTest Labs, you might hit the limit on API requests.
 

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

@@ -112,18 +112,17 @@ 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 properties from the Azure portal
+### Get VM properties from the Azure portal
 
-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 is the easiest way to get the JSON VM description if you don't already have a lab VM of that type.
+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.
 
 1. In the [Azure portal](https://portal.azure.com), on the **Overview** page for your lab, select **Add** on the top toolbar.
 1. On the **Choose a base** page, select the VM type you want. Depending on lab settings, the VM base can be an Azure Marketplace image, a custom image, a formula, or an environment.
-1. On the **Create lab resource** page:
-   - Optionally, add artifacts and configure any other settings you want on the **Basic settings** and **Advanced settings** tabs.
-   - On the **Advanced settings** tab, select **View ARM template** at the bottom of the page.
-1. On the **View Azure Resource Manager template** page, review the JSON template for creating the VM. The **resources** section has the VM properties to use in the PowerShell script.
+1. On the **Create lab resource** page, optionally [add artifacts](add-artifact-vm.md) and configure any other settings you want on the **Basic settings** and **Advanced settings** tabs.
+1. On the **Advanced settings** tab, select **View ARM template** at the bottom of the page.
+1. On the **View Azure Resource Manager template** page, review the JSON template for creating the VM. The **resources** section has the VM properties.
 
-   For example, the following snippet shows the properties for a Windows Server 2022 Datacenter VM:
+   For example, the following `resources` section has the properties for a Windows Server 2022 Datacenter VM:
    ```json
      "resources": [
           {
@@ -164,7 +163,7 @@ Creating a VM in the Azure portal generates an Azure Resource Manager (ARM) temp
      ],
    ```
 
-1. Copy and save the template to use in future PowerShell automation, and transfer the needed properties to the PowerShell VM creation script.
+1. Copy and save the template to use in future PowerShell automation, and transfer the properties to the PowerShell VM creation script.
 
 
 
@@ -178,11 +177,11 @@ You can also call the DevTest Labs REST API to get the properties of existing la
    - Under **labResourceGroup**, enter the lab resource group name.
    - Under **subscriptionId**, select the lab's Azure subscription.
 1. Select **Run**. 
-1. In the **Response** section under **Body**, view the properties for all the VMs in the lab.
+1. In the **Response** section under **Body**, view the properties for all the existing VMs in the lab.
 
 ## Set VM expiration date
 
-In training, demo, and trial scenarios, you can avoid unnecessary costs by deleting VMs automatically after a certain time. You can set the VM `expirationDate` property when you create a VM. The PowerShell VM creation script earlier in this article sets an expiration date under `properties`:
+In training, demo, and trial scenarios, you can avoid unnecessary costs by deleting VMs automatically on a certain date. You can set the VM `expirationDate` property when you create a VM. The PowerShell VM creation script earlier in this article sets an expiration date under `properties`:
 
 ```json
           "expirationDate"          = "2022-12-01"
@@ -220,4 +219,4 @@ Set-AzResource -ResourceId $VmResourceId -Properties $VmProperties -Force
 
 ## Next steps
 
-See the following content: [Azure PowerShell documentation for Azure DevTest Labs](/powershell/module/az.devtestlabs/)
+[Az.DevTestLabs PowerShell reference](/powershell/module/az.devtestlabs/)

articles/devtest-labs/encrypt-storage.md

@@ -76,7 +76,7 @@ The following rule sets a 90-day expiration specifically for artifact results:
 
 Azure Storage automatically encrypts all data in the lab storage account. Azure Storage encryption protects your data and helps meet organizational security and compliance commitments. For more information, see [Azure Storage encryption for data at rest](../storage/common/storage-service-encryption.md).
 
-Azure Storage encrypts lab data with a Microsoft-managed key. Optionally, you can manage encryption with your own keys. If you choose to manage lab storage account encryption with your own keys, you can specify a customer-managed key with Azure Key Vault to use for encrypting and decrypting data.
+Azure Storage encrypts lab data with a Microsoft-managed key. Optionally, you can manage encryption with your own keys. If you choose to manage lab storage account encryption with your own key, you can use Azure Key Vault to  specify a customer-managed key for encrypting and decrypting data.
 
 For more information and instructions on configuring customer-managed keys for Azure Storage encryption, see: