fixes

Author: v-thepet

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

@@ -5,23 +5,25 @@ ms.topic: how-to
 ms.date: 01/23/2022
 ---
 
-# Deploy DevTest Labs environments with nested ARM templates
+# Deploy DevTest Labs environments by using nested templates
 
-This article shows an example of nesting Azure Resource Manager (ARM) templates to deploy an Azure DevTest Labs environment. A nested deployment runs secondary ARM templates from within a main ARM template. Decomposing a deployment into a set of targeted, purpose-specific templates provides testing, reuse, and readability benefits. For general information and code samples using nested templates, see [Using linked and nested templates when deploying Azure resources](../azure-resource-manager/templates/linked-templates.md).
+This article shows an example of nesting Azure Resource Manager (ARM) templates to deploy an Azure DevTest Labs environment. DevTest Labs environments contain multiple infrastructure-as-a-service (IaaS) virtual machines (VMs) with platform-as-a-service (PaaS) resources installed. You can provision PaaS resources and VMs by using ARM templates.
+
+A nested deployment runs secondary ARM templates from within a main template. 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 [Using linked and nested templates when deploying Azure resources](../azure-resource-manager/templates/linked-templates.md).
 
 ## Deploy nested templates with Visual Studio
 
-You can create ARM templates from scratch, but Visual Studio has an Azure Resource Group project template that makes it easy to develop and debug templates. When you add a nested deployment resource to the main *azuredeploy.json* ARM template, Visual Studio adds the following items to make the template more flexible:
+The Azure Resource Group project template in Visual Studio makes it easy to develop and debug ARM templates. When you add a nested template to the main *azuredeploy.json* template file, Visual Studio adds the following items to make the template more flexible:
 
-- The subfolder with the secondary template and parameters files
-- Variable names within the main template file
-- Two key parameters that DevTest Labs uses for the storage location for new files, `_artifactsLocation` and `_artifactsLocationSasToken`
+- A subfolder with the secondary template and parameters files
+- Variable names in the main template file
+- Two key parameters, `_artifactsLocation` and `_artifactsLocationSasToken`, which DevTest Labs uses for its file storage location.
 
-In DevTest Labs, you store ARM templates in a Git repository that you link to the lab. When you use a template to create a new environment, the files move into an Azure Storage container in the lab. DevTest Labs identifies the `_artifactsLocation` and `_artifactsLocationSasToken` values, copies the subfolders to the storage container, and automatically inserts the location and Shared Access Signature (SaS) token into the parameters files.
+In DevTest Labs, you store ARM templates in a Git repository that you link to the lab. When you use one of the linked repository templates to create a new environment, the deployment copies the template files into an Azure Storage container in the lab. When you add a nested template resource to the repository and main template file, Visual Studio identifies the `_artifactsLocation` and `_artifactsLocationSasToken` values, copies the subfolders to the storage container, and inserts the location and Shared Access Signature (SaS) token into the parameters files.
 
 ## Nested template folder structure
 
-The Git repository folder for the following template example has a subfolder, *nestedtemplates*, with the nested template files *NestOne.json* and *NestOne.parameters.json*. The *azuredeploy.json* main template file builds the URI for the secondary templates by using the artifacts location, nested template folder, and nested template filename. The URI for the parameters file uses the artifacts location, nested template folder, and nested template parameters file. You can add more subfolders in the primary folder, but only a single level.
+In the following template example, the Git repository folder has a subfolder, *nestedtemplates*, with the nested template files *NestOne.json* and *NestOne.parameters.json*. The *azuredeploy.json* main template file builds the URI for the secondary templates by using the artifacts location, nested template folder, and nested template filename. The URI for the parameters file is the artifacts location, nested template folder, and nested template parameters file. You can add more nested template subfolders to the primary folder at the same nesting level.
 
 The following screenshot shows the project structure in Visual Studio: 
 

articles/devtest-labs/devtest-lab-add-devtest-user.md

@@ -6,9 +6,9 @@ ms.date: 01/21/2022
 ms.custom: devx-track-azurepowershell
 ---
 
-# Azure DevTest Labs owners, contributors, and users
+# Add lab owners, contributors, and users in Azure DevTest Labs 
 
-This article describes the three built-in Azure DevTest Labs roles: *Owner*, *Contributor*, and *DevTest Labs User*, and how to add users with these roles to labs. DevTest Labs uses Azure [role-based access control](../role-based-access-control/overview.md) (Azure RBAC) to define roles that have only the necessary access to do certain lab tasks. This article describes the tasks each role can do, and how to add users to lab roles by using the Azure portal or an Azure PowerShell script.
+Azure DevTest Labs uses Azure [role-based access control](../role-based-access-control/overview.md) (Azure RBAC) to define roles that have only the access necessary to do specific lab tasks. DevTest Labs has three built-in roles: *Owner*, *Contributor*, and *DevTest Labs User*. This article describes the tasks each role can do, and how to add members to lab roles by using the Azure portal or an Azure PowerShell script.
 
 ## Actions each role can take
 
@@ -39,7 +39,7 @@ Artifact tasks:
 
 ### Contributor
 
-The lab Contributor role can take all the same actions as lab Owner, except it can't add users to labs.
+The lab Contributor role can take all the same actions as lab Owner, except can't add users to labs.
 
 ### DevTest Labs User
 
@@ -56,7 +56,7 @@ The DevTest Labs User role can take the following actions in DevTest Labs:
 
 ## Add Owners, Contributors, or DevTest Labs Users
 
-A lab Owner can add members to lab roles by using the Azure portal or an Azure PowerShell script. The user to add can be an external user with a valid [Microsoft account (MSA)](./devtest-lab-faq.yml).
+A lab owner can add members to lab roles by using the Azure portal or an Azure PowerShell script. The user to add can be an external user with a valid [Microsoft account (MSA)](./devtest-lab-faq.yml).
 
 Azure permissions propagate from parent scope to child scope. Owners of an Azure subscription that contains labs are automatically owners of the subscription's DevTest Labs service, the labs, and the VMs and other resources they contain. Subscription owners can add Owners, Contributors, and DevTest Labs Users to labs in the subscription.
 
@@ -65,10 +65,12 @@ Azure permissions propagate from parent scope to child scope. Owners of an Azure
 
 ### Prerequisites
 
+To add members to a lab:
+
 - You must be an Owner of the lab, either directly or by inheritance as a subscription owner.
 - Sign in to the [Azure portal](https://portal.azure.com) as an [Owner](../role-based-access-control/built-in-roles.md#owner) or [User Access Administrator](../role-based-access-control/built-in-roles.md#user-access-administrator).
 
-### Add a member to a lab by using the Azure portal
+### Add a lab user by using the Azure portal
 
 - To add a user at the subscription level, open the subscription page.
 - To add a user at the lab level, open the resource group that has the lab, and select the lab from the list of resources.
@@ -79,7 +81,7 @@ Azure permissions propagate from parent scope to child scope. Owners of an Azure
 
    ![Screenshot that shows an access control (IAM) page with the Add role assignment menu open.](media/devtest-lab-add-devtest-user/add-role-assignment-menu-generic.png)
 
-1. On the **Add Role Assignment** page, select the **Owner**, **Contributor**, or **User** role, and then select **Next**.
+1. On the **Add Role Assignment** page, select the **Owner**, **Contributor**, or **DevTest Labs User** role, and then select **Next**.
 
    ![Screenshot that shows the Add role assignment page with the Role tab selected.](media/devtest-lab-add-devtest-user/add-role-assignment-role-generic.png)
 
@@ -89,6 +91,7 @@ Azure permissions propagate from parent scope to child scope. Owners of an Azure
 
 1. Select **Review + assign**, and after reviewing the details, select **Review + assign** again.
 
+<a name="add-an-external-user-to-a-lab-using-powershell"></a>
 ### Add a DevTest Labs User to a lab by using Azure PowerShell
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]