Fix reviewer feedback

Author: sdwheeler

articles/cosmos-db/how-to-container-copy.md

@@ -17,7 +17,7 @@ ms.reviewer: sidandrews
 
 This article describes how to create, monitor, and manage intra-account container copy jobs using Azure PowerShell or CLI commands.
 
-## Pre-requisites
+## Prerequisites
 
 * You may use the portal [Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) to run container copy commands. Alternately, you may run the commands locally; make sure you have [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps-msi) downloaded and installed on your machine.
 * Currently, container copy is only supported in [these regions](intra-account-container-copy.md#supported-regions). Make sure your account's write region belongs to this list.
@@ -33,7 +33,7 @@ az extension add --name cosmosdb-preview
 
 ## Set shell variables
 
-First, set all of the variables that each individual script will use.
+First, set all of the variables that each individual script uses.
 
 ```azurepowershell-interactive
 $resourceGroup = "<resource-group-name>"
@@ -116,7 +116,7 @@ az cosmosdb dts resume `
 ```
 
 ## Get support for container copy issues
-For issues related to intra-account container copy, please raise a New Support Request from the Azure Portal with the Problem Type as 'Data Migration' and Problem subtype as 'Intra-account container copy'.
+For issues related to intra-account container copy, please raise a **New Support Request** from the Azure portal. Set the **Problem Type** as 'Data Migration' and **Problem subtype** as 'Intra-account container copy'.
 
 
 ## Next steps

articles/cosmos-db/intra-account-container-copy.md

@@ -30,7 +30,7 @@ Intra-account container copy jobs can be [created and managed using CLI commands
 
 ## Get started
 
-To get started using container copy jobs, register for "Intra-account offline container copy (Cassandra & SQL)" preview from the ['Preview Features'](access-previews.md) list in the Azure portal. Once the registration is complete, the preview will be effective for all Cassandra and API for NoSQL accounts in the subscription.
+To get started using container copy jobs, register for "Intra-account offline container copy (Cassandra & SQL)" preview from the ['Preview Features'](access-previews.md) list in the Azure portal. Once the registration is complete, the preview is effective for all Cassandra and API for NoSQL accounts in the subscription.
 
 ## Overview of steps needed to do container copy
 
@@ -49,7 +49,7 @@ Intra-account container copy jobs perform offline data copy using the source con
 * The container copy jobs run on these instances.
 * A single job is executed across all instances at any time.
 * The instances are shared by all the container copy jobs running within the same account.
-* The platform may de-allocate the instances if they're idle for >15 mins.
+* The platform may deallocate the instances if they're idle for >15 mins.
 
 > [!NOTE]
 > We currently only support offline container copy jobs. So, we strongly recommend to stop performing any operations on the source container prior to beginning the container copy. Item deletions and updates done on the source container after beginning the copy job may not be captured. Hence, continuing to perform operations on the source container while the container job is in progress may result in additional or missing data on the target container.
@@ -78,15 +78,15 @@ Container copy jobs are currently supported on best-effort basis. We don't provi
 
 ### Can I create multiple container copy jobs within an account?
 
-Yes, you can create multiple jobs within the same account. The jobs will run consecutively. You can [list all the jobs](how-to-container-copy.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
+Yes, you can create multiple jobs within the same account. The jobs run consecutively. You can [list all the jobs](how-to-container-copy.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
 
 ### Can I copy an entire database within the Azure Cosmos DB account?
 
-You'll have to create a job for each container in the database.
+You must create a job for each container in the database.
 
 ### I have an Azure Cosmos DB account with multiple regions. In which region will the container copy job run?
 
-The container copy job will run in the write region. If there are accounts configured with multi-region writes, the job will run in one of the regions from the list.
+The container copy job runs in the write region. If there are accounts configured with multi-region writes, the job runs in one of the regions from the list.
 
 ### What happens to the container copy jobs when the account's write region changes?
 
@@ -95,8 +95,8 @@ The account's write region may change in the rare scenario of a region outage or
 ### Why is a new database *__datatransferstate* created in the account when I run container copy jobs? Am I being charged for this database?
 
 * *__datatransferstate* is a database that is created while running container copy jobs. This database is used by the platform to store the state and progress of the copy job.
-* The database uses manual provisioned throughput of 800 RUs. You'll be charged for this database.
-* Deleting this database will remove the container copy job history from the account. It can be safely deleted once all the jobs in the account have completed, if you no longer need the job history. The platform won't clean up the *__datatransferstate* database automatically.
+* The database uses manual provisioned throughput of 800 RUs. You are charged for this database.
+* Deleting this database removes the container copy job history from the account. It can be safely deleted once all the jobs in the account have completed, if you no longer need the job history. The platform doesn't clean up the *__datatransferstate* database automatically.
 
 ## Supported regions
 

articles/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md

@@ -17,12 +17,14 @@ ms.author: alkohli
 
 This article shows you how to enable Azure Arc on an existing Kubernetes cluster on your Azure Stack Edge Pro device.
 
-This procedure is intended for those who have reviewed the [Kubernetes workloads on Azure Stack Edge Pro device](azure-stack-edge-gpu-kubernetes-workload-management.md) and are familiar with the concepts of [What is Azure Arc-enabled Kubernetes (Preview)?](../azure-arc/kubernetes/overview.md).
+This procedure assumes that you have read and understood the following articles:
 
+- [Kubernetes workloads on Azure Stack Edge Pro device](azure-stack-edge-gpu-kubernetes-workload-management.md)
+- [What is Azure Arc-enabled Kubernetes (Preview)?](../azure-arc/kubernetes/overview.md)
 
 ## Prerequisites
 
-Before you can enable Azure Arc on Kubernetes cluster, make sure that you have completed the following prerequisites on your Azure Stack Edge Pro device and the client that you will use to access the device:
+Make sure that you've completed the following prerequisites on your Azure Stack Edge Pro device and the client that you use to access the device:
 
 ### For device
 
@@ -35,14 +37,14 @@ Before you can enable Azure Arc on Kubernetes cluster, make sure that you have c
 
 ### For client accessing the device
 
-1. You have a  Windows client system that will be used to access the Azure Stack Edge Pro device.
+1. You have a Windows client system that is used to access the Azure Stack Edge Pro device.
 
     - The client is running Windows PowerShell 5.0 or later. To download the latest version of Windows PowerShell, go to [Install Windows PowerShell](/powershell/scripting/install/installing-powershell-core-on-windows).
 
     - You can have any other client with a [Supported operating system](azure-stack-edge-gpu-system-requirements.md#supported-os-for-clients-connected-to-device) as well. This article describes the procedure when using a Windows client.
 
 
-1. You have completed the procedure described in [Access the Kubernetes cluster on Azure Stack Edge Pro device](azure-stack-edge-gpu-create-kubernetes-cluster.md). You have:
+1. You've completed the procedure described in [Access the Kubernetes cluster on Azure Stack Edge Pro device](azure-stack-edge-gpu-create-kubernetes-cluster.md). You have:
 
     - Installed `kubectl` on the client.
     - Make sure that the `kubectl` client version is skewed no more than one version from the Kubernetes master version running on your Azure Stack Edge Pro device.
@@ -56,9 +58,9 @@ Before you can enable Azure Arc on Kubernetes cluster, make sure that you have c
 
 ## Register Kubernetes resource providers
 
-Before you enable Azure Arc on the Kubernetes cluster, you will need to enable and register `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration` against your subscription.
+Before you enable Azure Arc on the Kubernetes cluster, you need to enable and register `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration` against your subscription.
 
-1. To enable a resource provider, in the Azure portal, go to the subscription that you are planning to use for the deployment. Go to **Resource Providers**.
+1. To enable a resource provider, in the Azure portal, go to the subscription that you're planning to use for the deployment. Go to **Resource Providers**.
 1. In the right-pane, search for the providers you want to add. In this example, `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration`.
 
     ![Register Kubernetes resource providers](media/azure-stack-edge-gpu-connect-powershell-interface/register-k8-resource-providers-1.png)
@@ -87,9 +89,9 @@ You can also register resource providers via the `az cli`. For more information,
 
     `az ad sp create-for-rbac --name "<Informative name for service principal>"`
 
-    For information on how to log into the `az cli`, [Start Cloud Shell in Azure portal](/azure/cloud-shell/quickstart). If using `az cli` on a local client to create the service principal, make sure that you are running version 2.25 or later.
+    For information on how to log into the `az cli`, [Start Cloud Shell in Azure portal](/azure/cloud-shell/quickstart). If using `az cli` on a local client to create the service principal, make sure that you're running version 2.25 or later.
 
-    Here is an example.
+    Here's an example.
 
     ```azurecli
     PS /home/user> az ad sp create-for-rbac --name "https://azure-arc-for-ase-k8s"
@@ -103,13 +105,13 @@ You can also register resource providers via the `az cli`. For more information,
     PS /home/user>
     ```
 
-1. Make a note of the `appID`, `name`, `password`, and `tenantID` as you will use this as input in the next command.
+1. Make a note of the `appID`, `name`, `password`, and `tenantID` as you'll use these values as input to the next command.
 
 1. After creating the new service principal, assign the `Kubernetes Cluster - Azure Arc Onboarding` role to the newly created principal. This is a built-in Azure role (use the role ID in the command) with limited permissions. Use the following command:
 
     `az role assignment create --role 34e09817-6cbe-4d01-b1a2-e0eac5743d41 --assignee <appId-from-service-principal> --scope /subscriptions/<SubscriptionID>/resourceGroups/<Resource-group-name>`
 
-    Here is an example.
+    Here's an example.
 
     ```azurecli
     PS /home/user> az role assignment create --role 34e09817-6cbe-4d01-b1a2-e0eac5743d41 --assignee xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx --scope /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/myaserg1
@@ -138,16 +140,16 @@ Follow these steps to configure the Kubernetes cluster for Azure Arc management:
 
     `Set-HcsKubernetesAzureArcAgent -SubscriptionId "<Your Azure Subscription Id>" -ResourceGroupName "<Resource Group Name>" -ResourceName "<Azure Arc resource name (shouldn't exist already)>" -Location "<Region associated with resource group>" -TenantId "<Tenant Id of service principal>" -ClientId "<App id of service principal>"`
 
-    When this command is run, there is a followup prompt to enter the `ClientSecret`. Provide the service principal password.
+    When this command is run, there's a follow-up prompt to enter the `ClientSecret`. Provide the service principal password.
 
-    Add the `CloudEnvironment` parameter if you are using a cloud other than Azure public. You can set this parameter to `AZUREPUBLICCLOUD`, `AZURECHINACLOUD`, `AZUREGERMANCLOUD`, and `AZUREUSGOVERNMENTCLOUD`.
+    Add the `CloudEnvironment` parameter if you're using a cloud other than Azure public. You can set this parameter to `AZUREPUBLICCLOUD`, `AZURECHINACLOUD`, `AZUREGERMANCLOUD`, and `AZUREUSGOVERNMENTCLOUD`.
 
     > [!NOTE]
     > - To deploy Azure Arc on your device, make sure that you are using a [Supported region for Azure Arc](https://azure.microsoft.com/global-infrastructure/services/?products=azure-arc).
     > - Use the `az account list-locations` command to figure out the exact location name to pass in the `Set-HcsKubernetesAzureArcAgent` cmdlet. Location names are typically formatted without any spaces.
     > - `ClientId` and `ClientSecret` are required.
 
-    Here is an example:
+    Here's an example:
 
     ```powershell
     [10.100.10.10]: PS>Set-HcsKubernetesAzureArcAgent -SubscriptionId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -ResourceGroupName "myaserg1" -ResourceName "myasetestresarc" -Location "westeurope" -TenantId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -ClientId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
@@ -171,7 +173,7 @@ Follow these steps to configure the Kubernetes cluster for Azure Arc management:
 
     `kubectl get deployments,pods -n azure-arc`
 
-    Here is a sample output that shows the Azure Arc agents that were deployed on your Kubernetes cluster in the `azure-arc` namespace.
+    Here's a sample output that shows the Azure Arc agents that were deployed on your Kubernetes cluster in the `azure-arc` namespace.
 
     ```powershell
     [10.128.44.240]: PS>kubectl get deployments,pods -n azure-arc

articles/devtest-labs/how-to-move-labs.md

@@ -1,5 +1,5 @@
 ---
-title: Move a DevTest lab to another region
+title: Move DevTest Labs to another region
 description: Shows you how to move a lab to another region.
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell
@@ -8,11 +8,11 @@ author: RoseHJM
 ms.date: 03/03/2022
 ---
 
-# Move a DevTest lab to another region
+# Move DevTest Labs to another region
 
 To move a lab, create a copy of an existing lab in another region.
 
-In this article, you'll learn how to:
+In this article, you learn how to:
 > [!div class="checklist"]
 > >
 > - Export an Azure Resource Manager (ARM) template of your lab.
@@ -21,13 +21,14 @@ In this article, you'll learn how to:
 > - Configure the new lab.
 > - Move data to the new  lab.
 > - Delete the resources in the source region.
+
 ## Prerequisites
 
 - Ensure that the services and features that your account uses are supported in the target region.
 
 - For preview features, ensure that your subscription is allowlisted for the target region.
 
-- DevTest Labs doesn't store or expose passwords from the exported ARM template. You will need to know the passwords/secrets for:
+- DevTest Labs doesn't store or expose passwords from the exported ARM template. You need to know the passwords/secrets for:
 
   - the VMs
   - the Stored Secrets
@@ -49,15 +50,15 @@ To get started, export and modify a Resource Manager template.
 
 ### Export an ARM template of your lab.
 
-Next, you'll export a JSON template contains settings that describe your lab.
+Next, you export a JSON template contains settings that describe your lab.
 
 To export a template by using Azure portal:
 
 1. Select **All resources**, and then select the resource group for the lab.
 
 1. Select **Export template**.
 
-1. Choose **Download** in the **Export template** blade.
+1. Choose **Download** in **Export template**.
 
 1. Locate the .zip file that you downloaded from the portal, and unzip that file to a folder of your choice.
 
@@ -95,7 +96,7 @@ To update the template by using Azure portal:
           "location": "centralus",
       ```
 
-   1. If you have "All virtual machines in one resource group" set in the "Lab settings", also update the following in the ARM template:
+   1. If you have "All virtual machines in one resource group" set in the "Lab settings", also update the following values in the ARM template:
 
       + Update the `apiVersion` of the `microsoft.devtestlab/labs` resource to `2018-10-15-preview`.
       + Add `vmCreationResourceGroupId` to the `properties` section.
@@ -193,7 +194,7 @@ Deploy the template to create a new lab in the target region.
    |**Resource group**|Select the resource group name you created in the last section. |
    |**Location**|Select a location for the lab. For example, **Central US**. |
    |**Lab Name**|Must be a different name. |
-   |**Vnet ID**|Must be the moved one, or the new one you just created. |
+   |**Vnet ID**|Must be the moved one, or the new one you created. |
 
 
 1. Select **Review + create**.
@@ -206,18 +207,18 @@ Deploy the template to create a new lab in the target region.
 
 While most Lab resources have been replicated under the new region using the ARM template, a few edits still need to be moved manually.
 
-1. Add the Compute Gallery back to the lab if there're any in the original one.
+1. Add the Compute Gallery back to the lab if there are any in the original one.
 1. Add the policies "Virtual machines per user", "Virtual machines per lab" and "Allowed Virtual machine sizes" back to the moved lab
 
 ### Swap the OS disks of the Compute VMs under the new VMs.
 
 Note the VMs under the new Lab have the same specs as the ones under the old Lab. The only difference is their OS Disks.
 
-1. Create an empty disks under the new region.
+1. Create an empty disk under the new region.
 
-   - Get the target Compute VM OS disk name under the new Lab.  You can fnd the Compute VM and its disk under the Resource group on the lab's Virtual Machine page.
+   - Get the target Compute VM OS disk name under the new Lab.  You can find the Compute VM and its disk under the Resource group on the lab's Virtual Machine page.
 
-   - Use [AzCopy](../storage/common/storage-use-azcopy-v10.md) to copy the old disk content into the new/empty disks in the new region. You can run the Powershell commands from your Dev Box or from the [Azure Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell).
+   - Use [AzCopy](../storage/common/storage-use-azcopy-v10.md) to copy the old disk content into the new/empty disks in the new region. You can run the PowerShell commands from your Dev Box or from the [Azure Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell).
 
      AzCopy is the preferred tool to move your data over. It's optimized for performance.  One way that it's faster, is that data is copied directly, so AzCopy doesn't use the network bandwidth of your computer. Use AzCopy at the command line or as part of a custom script. See [Get started with AzCopy](../storage/common/storage-use-azcopy-v10.md).
 
@@ -262,7 +263,7 @@ To remove a lab by using the Azure portal:
 
 ## Next steps
 
-In this article, you moved a DevTest lab from one region to another and cleaned up the source resources.  To learn more about moving resources between regions and disaster recovery in Azure, refer to:
+In this article, you moved DevTest Labs from one region to another and cleaned up the source resources.  To learn more about moving resources between regions and disaster recovery in Azure, refer to:
 
 - [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
 - [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)