Editorial changes for publish

Author: stevenmatthew

articles/databox/data-box-deploy-copy-data.md

@@ -266,7 +266,7 @@ To optimize the performance, use the following robocopy parameters when copying
 
 For more information on Robocopy command, go to [Robocopy and a few examples](https://social.technet.microsoft.com/wiki/contents/articles/1073.robocopy-and-a-few-examples.aspx).
 
-Notifications are displayed during the copy porocess to identify errors.
+Notifications are displayed during the copy process to identify errors.
 
 ![A copy error notification in Connect and copy](media/data-box-deploy-copy-data/view-errors-1.png)
 

articles/databox/data-box-disk-deploy-copy-data.md

@@ -89,7 +89,7 @@ Review the following considerations before you copy the data to the disks:
 - It is your responsibility to copy local data to the share which corresponds to the appropriate data format. For instance, copy block blob data to the *BlockBlob* share. Copy VHDs to the *PageBlob* share. If the local data format doesn't match the appropriate folder for the chosen storage type, the data upload to Azure fails in a later step.
 - You can't copy data directly to a share's *root* folder. Instead, create a folder within the appropriate share and copy your data into it.
     - Folders located at the *PageBlob* share's *root* correspond to containers within your storage account. A new container will be created for any folder whose name does not match an existing container within your storage account.
-    - Folders located at the *AzFile* share's *root* corrsepond to Azure file shares. A new file share will be created for any folder whose name does not match an existing file share within your storage account.
+    - Folders located at the *AzFile* share's *root* correspond to Azure file shares. A new file share will be created for any folder whose name does not match an existing file share within your storage account.
     - The *BlockBlob* share's *root* level contains one folder corresponding to each access tier. When copying data to the *BlockBlob* share, create a subfolder within the top-level folder corresponding to the desired access tier. As with the *PageBlob* share, a new containers will be created for any folder whose name doesn't match an existing container. Data within the container will be copied to the tier corresponding to the subfolder's top-level parent.
 
       A container will also be created for any folder residing at the *BlockBlob* share's *root*, though the data it will be copied to the container's default access tier. To ensure that your data is copied to the desired access tier, don't create folders at the *root* level.

articles/databox/data-box-disk-quickstart-portal.md

@@ -144,7 +144,7 @@ Once the order is created, the device is prepared for shipment.
 
 This step takes roughly 5 minutes.
 
-The Data Box Disk are mailed in a UPS Express Box. Open the box and check that the box has:
+Data Box Disks are mailed in a UPS Express Box. Open the box and check that the box has:
 
 - 1 to 5 bubble-wrapped USB disks.
 - A connecting cable per disk.

articles/databox/data-box-heavy-deploy-copy-data.md

@@ -138,7 +138,7 @@ If using a Windows Server host computer, follow these steps to connect to the Da
 
     **Always create a folder for the files that you intend to copy under the share and then copy the files to that folder**.  You cannot copy files directly to the *root* folder in the storage account. Any folders created under the *PageBlob* share represents containers into which data is uploaded as blobs. Similarly, any sub-folders created within the folders representing access tiers in the *BlockBlob* share also represents a blob storage container. Folders created within the *AzFile* share represent file shares.
 
-    Folders created at the *root* of the *BlockBlob* share will be created as a blob containers. The access tier of these container will be inherited from the storage account.
+    Folders created at the *root* of the *BlockBlob* share will be created as blob containers. The access tier of these container will be inherited from the storage account.
     
 ### Connect on a Linux system
 

includes/data-box-order-portal.md

@@ -191,7 +191,7 @@ Do the following steps in the Azure portal to order a device:
     > If you use a customer-managed key, you must enable the `Get`, `UnwrapKey`, and `WrapKey` permissions on the key. Without these permissions, order creation will fail. They're also needed during data copy. To set the permissions in Azure CLI, see [az keyvault set-policy](/cli/azure/keyvault#az-keyvault-set-policy).
 
 
-16. If you don't want to use the system-generated passwords that Azure Data Box uses by default, expand **Bring your own password** on the **Security** screen.
+15. If you don't want to use the system-generated passwords that Azure Data Box uses by default, expand **Bring your own password** on the **Security** screen.
 
     The system-generated passwords are secure, and are recommended unless your organization requires otherwise.
 
@@ -227,7 +227,7 @@ Do the following steps in the Azure portal to order a device:
 
     On the **Security** screen, you can use **View or change passwords** to change the passwords.
 
-17. In **Security**, if you want to enable software-based double encryption, expand **Double-encryption (for highly secure environments)**, and select **Enable double encryption for the order**.
+16. In **Security**, if you want to enable software-based double encryption, expand **Double-encryption (for highly secure environments)**, and select **Enable double encryption for the order**.
 
     ![Screenshot of Double Encryption options on the Security tab for a Data Box order. The Enable Double Encryption For The Order option and the Next: Contact Details button are highlighted.](media/data-box-order-portal/double-encryption-01.png)
 
@@ -238,19 +238,19 @@ Do the following steps in the Azure portal to order a device:
 
     Select **Next: Contact details>** to continue.
 
-18. In **Contact details**, select **+ Add Address**.
+17. In **Contact details**, select **+ Add Address**.
 
     ![Screenshot of Contact Details tab for a Data Box order. The Contact Details tab and the Plus Add Address option are highlighted.](media/data-box-order-portal/contact-details-01.png)
 
-19. On the **Add address** screen, provide your first and last name, the name and postal address of the company, and a valid phone number. Select **Validate address**. The service validates the address for service availability and notifies you if service is available for that address.
+18. On the **Add address** screen, provide your first and last name, the name and postal address of the company, and a valid phone number. Select **Validate address**. The service validates the address for service availability and notifies you if service is available for that address.
 
     ![Screenshot of the Add Address screen for a Data Box order. The Ship using options and the Add shipping address option called out.](media/data-box-order-portal/contact-details-02.png)
 
     If you selected self-managed shipping, you will receive an email notification after the order is placed successfully. For more information about self-managed shipping, see [Use self-managed shipping](../articles/databox/data-box-portal-customer-managed-shipping.md).
 
-20. Select **Add shipping address** once the shipping details have been validated successfully. You will return to the **Contact details** tab.
+19. Select **Add shipping address** once the shipping details have been validated successfully. You will return to the **Contact details** tab.
 
-21. Beside **Email**, add one or more email addresses. The service sends email notifications regarding any updates to the order status to the specified email addresses.
+20. Beside **Email**, add one or more email addresses. The service sends email notifications regarding any updates to the order status to the specified email addresses.
 
     We recommend that you use a group email so that you continue to receive notifications if an admin in the group leaves.