Last round of updates before publish

Author: stevenmatthew

articles/databox/data-box-disk-faq.yml

@@ -13,7 +13,7 @@ metadata:
   ms.custom: references_regions
 title: "Azure Data Box Disk: Frequently Asked Questions"
 summary: |
-  The Microsoft Azure Data Box Disk cloud solution enables you to send terabytes of data to Azure in a quick, inexpensive, and reliable way. This FAQ contains questions and answers that you may have when you use Data Box Disks in the Azure portal.
+  The Microsoft Azure Data Box Disk cloud solution enables you to send terabytes of data to Azure in a quick, inexpensive, and reliable way. This FAQ contains questions and answers that you might have when you use Data Box Disks in the Azure portal.
 
 sections:
   - name: About the service
@@ -58,12 +58,12 @@ sections:
       - question: |
           Which regions can I store data in with Data Box Disks?
         answer: |
-          Data Box Disk is supported for all regions within US, Canada, EU, UK, Australia, Singapore, India, China, Hong Kong Special Administrative Region, Japan, Korea, and South Africa. Only the Azure public cloud regions are supported. The Azure Government or other sovereign clouds are not supported.
+          Data Box Disk is supported for all regions within US, Canada, EU, UK, Australia, Singapore, India, China, Hong Kong Special Administrative Region, Japan, Korea, and South Africa. Only the Azure public cloud regions are supported. The Azure Government or other sovereign clouds aren't supported.
 
       - question: |
           How can I import source data present at my location in one country/region to an Azure region in a different country?
         answer: |
-          Data Box Disk supports data ingestion only within the same country/region as their destination and will not cross any international borders. The only exception is for orders in the European Union (EU), where Data Box Disks can ship to and from any EU country/region.
+          Data Box Disk supports data ingestion only within the same country/region as their destination and won't cross any international borders. The only exception is for orders in the European Union (EU), where Data Box Disks can ship to and from any EU country or region.
           
           For example, if you wanted to move data at your location in Canada to an Azure West US storage account, then you could achieve it in the following way:
           
@@ -73,32 +73,32 @@ sections:
           
           **Option 2:**
           
-          1. Order Data Box Disk in Canada by choosing a storage account say in Canada Central. The SSD disk(s) are shipped from the Azure datacenter in Canada Central to the shipping address (in Canada) provided during order creation.
+          1. Order Data Box Disk in Canada by choosing a storage account say in Canada Central. SSD disks are shipped from the Azure datacenter in Canada Central to the shipping address (in Canada) provided during order creation.
           
-          2. After the data from your on-premises server is copied to the disks, return them to the Azure datacenter in Canada using Microsoft provided return labels. The data present on the Data Box Disk(s) then get uploaded to the destination storage account in the Canada Azure region chosen during order creation.
+          2. After the data from your on-premises server is copied to the disks, return them to the Azure datacenter in Canada using Microsoft provided return labels. The data present on Data Box Disks then get uploaded to the destination storage account in the Canada Azure region chosen during order creation.
           
           3. You can then use a tool like AzCopy to copy the data to a storage account in West US. This step incurs [standard storage](https://azure.microsoft.com/pricing/details/storage/) and [bandwidth charges](https://azure.microsoft.com/pricing/details/bandwidth/) that aren't included in the Data Box Disk billing.
           
       - question: |
           Does Data Box Disk store any customer data outside of the service region?
         answer: |
-          No. Data Box Disk does not store any customer data outside of the service region. The customer has full ownership of their data and can save the data to a specified location based on the storage account they select during the order creation.  
+          No. Data Box Disk doesn't store any customer data outside of the service region. The customer has full ownership of their data and can save the data to a specified location based on the storage account they select during the order creation.  
           
-          In addition to the customer data, there is Data Box Disk data that includes metadata and monitoring logs. In all the regions (except Brazil South, Southeast Asia, and East Asia), Data Box Disk data is stored and replicated in a [paired region](../availability-zones/cross-region-replication-azure.md) via a Geo-redundant Storage account to protect against data loss.  
+          In addition to the customer data, there's Data Box Disk data that includes metadata and monitoring logs. In all the regions (except Brazil South, Southeast Asia, and East Asia), Data Box Disk data is stored and replicated in a [paired region](../availability-zones/cross-region-replication-azure.md) via a Geo-redundant Storage account to protect against data loss.  
           
-          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South, Southeast Asia, and East Asia, Data Box Disk data is stored in a Zone-redundant Storage (ZRS) account so that it is contained in a single region. For Southeast Asia, all the Data Box Disk data is stored in Singapore. For Brazil South, the data is stored in Brazil. For East Asia, the data is stored in Hong Kong.
+          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South, Southeast Asia, and East Asia, Data Box Disk data is stored in a Zone-redundant Storage (ZRS) account so that it's contained in a single region. For Southeast Asia, all the Data Box Disk data is stored in Singapore. For Brazil South, the data is stored in Brazil. For East Asia, the data is stored in Hong Kong.
           
-          If there is a service outage in Brazil South, Southeast Asia, or East Asia, the customers can create new orders from another region. The new orders will be served from the region in which they are created and the customers are responsible for the to and fro shipment of the Data Box Disk.
+          If there's a service outage in Brazil South, Southeast Asia, or East Asia, the customers can create new orders from another region. The new orders are served from the region in which they're created and the customers are responsible for the to and fro shipment of the Data Box Disk.
       
       - question: |
           Does my Data Box Disk region have to be in the same Azure region as my destination storage account?
         answer: |
-          No. The Data Box Disk resource does not need to be the same as the storage account region where you want to transfer data. You can choose a storage account in any region within the country or commerce boundary selected during the order. The Data Box Disk region is only used to deploy the resource during order creation. This is fixed for each country or commerce boundary and cannot be changed.
+          No. The Data Box Disk resource doesn't need to be the same as the storage account region where you want to transfer data. You can choose a storage account in any region within the country or commerce boundary selected during the order. The Data Box Disk region is only used to deploy the resource during order creation. This is fixed for each country or commerce boundary and can't be changed.
           
       - question: |
           How can I recover my data if an entire region fails?
         answer: |
-          In extreme circumstances where a region is lost because of a significant disaster, Microsoft may initiate a regional failover. No action on your part is required in this case. Your order will be fulfilled through the failover region if it is within the same country or commerce boundary. However, some Azure regions don't have a paired region in the same geographic or commerce boundary. If there is a disaster in any of those regions, you will need to create the Data Box order again from a different region that is available, and copy the data to Azure in the new region. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../availability-zones/cross-region-replication-azure.md).
+          In extreme circumstances where a region is lost because of a significant disaster, Microsoft might initiate a regional failover. No action on your part is required in this case. Your order is fulfilled through the failover region if it is within the same country or commerce boundary. However, some Azure regions don't have a paired region in the same geographic or commerce boundary. If there is a disaster in any of those regions, you will need to create the Data Box order again from a different region that is available, and copy the data to Azure in the new region. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../availability-zones/cross-region-replication-azure.md).
           
       - question: |
           Whom should I contact if I encounter any issues  with Data Box Disks?
@@ -255,15 +255,15 @@ sections:
         answer: |
           No. Only one storage account, general or classic, is currently supported with Data Box Disks. Both hot and cool blob are supported.
           > [!Note]
-          > Classic storage accounts will not be supported starting **August 1, 2023**.
+          > Classic storage accounts won't be supported starting **August 1, 2023**.
 
       - question: |
           What is the toolset available for my data with Data Box Disks?
         answer: |
           The toolset available with the Data Box Disk contains three tools:
            - **Data Box Disk Unlock tool**: Use this tool to unlock the encrypted disks that are shipped from Microsoft. When unlocking the disks using the tool, you need to provide a passkey available in the Data Box Disk order in the Azure portal. 
            - **Data Box Disk Validation tool**: Use this tool to validate the size, format, and blob names as per the Azure naming conventions. It also generates checksums for the copied data, which are then used to verify the data uploaded to Azure.
-           - **Data Box Disk Split Copy tool**: Use this tool when you are using multiple disks and have a large dataset that needs to be split and copied across all the disks. This tool is currently available for Windows. This tool is not supported with managed disks. This tool validates the data as it copies it, so you can skip the validation step when using this tool.
+           - **Data Box Disk Split Copy tool**: Use this tool when you're using multiple disks and have a large dataset that needs to be split and copied across all the disks. This tool is currently available for Windows. This tool isn't supported with managed disks. This tool validates the data as it copies it, so you can skip the validation step when using this tool.
           
           The toolset is available both for Windows and Linux. You can download the toolset here:
           - [Download Data Box Disk toolset for Windows](https://aka.ms/databoxdisktoolswin) 
@@ -272,7 +272,7 @@ sections:
       - question: |
           Can I use Data Box Disk to transfer data to Azure Files and then use the data with Azure File Sync? 
         answer: |
-          Azure Files are supported with Data Box Disk but will not work well with Azure File Sync. Data Box Disk will transfer file/directory timestamps, attributes, and ACLs to Azure Files. Azure File Sync usage with Data Box disk is now supported.
+          Azure Files are supported with Data Box Disk but won't work well with Azure File Sync. Data Box Disk will transfer file/directory timestamps, attributes, and ACLs to Azure Files. Azure File Sync usage with Data Box disk is now supported.
           
           
   - name: Verify and upload
@@ -290,7 +290,7 @@ sections:
       - question: |
           I just noticed that I didn't follow the Azure naming requirements for my containers. Will my data fail to upload to Azure?
         answer: |
-          Any uppercase letters in your container names are automatically converted to lowercase. If the names are not compliant in other ways - for example, they contain special characters or other languages - the upload will fail. For more information, go to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions).
+          Any uppercase letters in your container names are automatically converted to lowercase. If the names aren't compliant in other ways - for example, they contain special characters or other languages - the upload will fail. For more information, go to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions).
           
       - question: |
           How do I verify the data I copied onto multiple Data Box Disks?
@@ -320,10 +320,10 @@ sections:
       - question: |
           I copied data to the ManagedDisk folder. I don't see any managed disks with the resource group specified for managed disks. Was my data uploaded to Azure? How can I locate it?
         answer: |
-          Yes. Your data was uploaded to Azure, but if you don't see any managed disks with the specified resource groups, it's likely because the data was not valid. If page blobs, block blobs, Azure Files, or managed disks are not valid, they will go to the following folders:
-           - Page blobs will go to a block blob container starting with *databoxdisk-invalid-pb-*.
+          Yes. Your data was uploaded to Azure, but if you don't see any managed disks with the specified resource groups, it's likely because the data wasn't valid. If page blobs, block blobs, Azure Files, or managed disks aren't valid, they'll go to the following folders:
+           - Page blobs go to a block blob container starting with *databoxdisk-invalid-pb-*.
            - Azure Files will go to a block blob container starting with *databoxdisk-invalid-af-*.
-           - Managed disks will go to a block blob container starting with *databoxdisk-invalid-md-*.
+           - Managed disks go to a block blob container starting with *databoxdisk-invalid-md-*.
 
 additionalContent: |
 

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

@@ -25,22 +25,22 @@ This section details some of the top issues faced when using a Linux client to c
 
 **Cause** 
 
-This could be due to an unclean file system.
+An unclean file system could result in drives being mounted as read-only.
 
-Remounting a drive as read-write does not work with Data Box Disks. This scenario is not supported with drives decrypted by dislocker. You may have successfully remounted the device using the following command:
+Remounting a drive as read-write doesn't work with Data Box Disks. This scenario isn't supported with drives decrypted by dislocker. You might successfully remount the device using the following command:
 
 ```
 # mount -o remount, rw /mnt/DataBoxDisk/mountVol1
 ```
 
-Though the remounting was successful, the data will not persist.
+Though the remounting was successful, the data won't persist.
 
 **Resolution**
 
 Take the following steps on your Linux system:
 
 1. Install the `ntfsprogs` package for the ntfsfix utility.
-2. Unmount the mount points provided for the drive by the unlock tool. The number of mount points will vary for drives.
+2. Unmount the mount points provided for the drive by the unlock tool. The number of mount points varies for drives.
 
     ```
     unmount /mnt/DataBoxDisk/mountVol1
@@ -52,7 +52,7 @@ Take the following steps on your Linux system:
     ntfsfix /mnt/DataBoxDisk/bitlockerVol1/dislocker-file
     ```
 
-4. Run the following command to remove the hibernation metadata that may cause the mount issue.
+4. Run the following command to remove the hibernation metadata that might cause the mount issue.
 
     ```
     ntfs-3g -o remove_hiberfile /mnt/DataBoxDisk/bitlockerVol1/dislocker-file /mnt/DataBoxDisk/mountVol1
@@ -73,13 +73,13 @@ Take the following steps on your Linux system:
  
 **Cause** 
 
-If you see that your drive does not have data after it was unmounted (though data was copied to it), then it is possible that you remounted a drive as read-write after the drive was mounted as read-only.
+If your drive doesn't contain your copied data after being mounted, it's possible that it was remounted as read-write after having been mounted as read-only.
 
 **Resolution**
  
 If that is the case, see the resolution for [drives getting mounted as read-only](#issue-drive-getting-mounted-as-read-only).
 
-If that was not the case, copy the logs from the folder that has the Data Box Disk Unlock tool and [contact Microsoft Support](data-box-disk-contact-microsoft-support.md).
+If that wasn't the case, copy the logs from the folder that has the Data Box Disk Unlock tool and [contact Microsoft Support](data-box-disk-contact-microsoft-support.md).
 
 
 ## Data Box Disk Split Copy tool errors
@@ -88,7 +88,7 @@ The issues seen when using a Split Copy tool to split the data over multiple dis
 
 |Error message/Warnings |Recommendations |
 |---------|---------|
-|[Info] Retrieving BitLocker password for volume: m <br>[Error] Exception caught while retrieving BitLocker key for volume m:<br> Sequence contains no elements.|This error is thrown if the destination Data Box Disk are offline. <br> Use `diskmgmt.msc` tool to online disks.|
+|[Info] Retrieving BitLocker password for volume: m <br>[Error] Exception caught while retrieving BitLocker key for volume m:<br> Sequence contains no elements.|This error is thrown if the destination Data Box Disks are offline. <br> Use `diskmgmt.msc` tool to online disks.|
 |[Error] Exception thrown: WMI operation failed:<br> Method=UnlockWithNumericalPassword, ReturnValue=2150694965, <br>Win32Message=The format of the recovery password provided is invalid. <br>BitLocker recovery passwords are 48 digits. <br>Verify that the recovery password is in the correct format and then try again.|Use Data Box Disk Unlock tool to first unlock the disks and retry the command. For more information, go to <li> [Unlock Data Box Disk](data-box-disk-deploy-set-up.md#unlock-disks). </li><li> [Unlock disks](data-box-disk-deploy-set-up.md#unlock-disks) </li>|
 |[Error] Exception thrown: A DriveManifest.xml file exists on the target drive. <br> This indicates the target drive may have been prepared with a different journal file. <br>To add more data to the same drive, use the previous journal file. To delete existing data and reuse target drive for a new import job, delete the *DriveManifest.xml* on the drive. Rerun this command with a new journal file.| This error is received when you attempt to use the same set of drives for multiple import session. <br> Use one set of drives only for one split and copy session only.|
 |[Error] Exception thrown: CopySessionId importdata-sept-test-1 refers to a previous copy session and cannot be reused for a new copy session.|This error is reported when trying to use the same job name for a new job as a previous successfully completed job.<br> Assign a unique name for your new job.|