Publishing team bug fixes

Author: stevenmatthew

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

@@ -82,7 +82,7 @@ Take the following steps to order Data Box Disk.
 
 1. Select **Data Box Disk**. The maximum capacity of the solution for a single order of five disks is 35 TB. You could create multiple orders for larger data sizes.
 
-     :::image type="content" alt-text="Select Data Box Disk option 2" source="media/data-box-disk-deploy-ordered/select-data-box-sku-zoom.png" lightbox="media/data-box-disk-deploy-ordered/select-data-box-sku-zoom-lrg.png":::
+     :::image type="content" alt-text="Screenshot showing the location of the Data Box Disk option's Select button." source="media/data-box-disk-deploy-ordered/select-data-box-sku-zoom.png" lightbox="media/data-box-disk-deploy-ordered/select-data-box-sku-zoom-lrg.png":::
 
 1. In **Order**, specify the **Order details** in the **Basics** tab. Enter or select the following information.
 

articles/databox/data-box-disk-deploy-set-up.md

@@ -157,7 +157,7 @@ Perform the following steps to connect and unlock your disks.
     .\DataBoxDiskUnlock.exe /help
     ```
 
-    :::image type="content" source="media/data-box-disk-deploy-set-up/disk-unlock-help.png" alt-text="Screenshot showing the output fo the Data Box Unlock tool's Help sommand." lightbox="media/data-box-disk-deploy-set-up/disk-unlock-help-lrg.png":::
+    :::image type="content" source="media/data-box-disk-deploy-set-up/disk-unlock-help.png" alt-text="Screenshot showing the output of the Data Box Unlock tool's Help command." lightbox="media/data-box-disk-deploy-set-up/disk-unlock-help-lrg.png":::
 
 8. After the disk is unlocked, you can view the contents of the disk.
 
@@ -229,7 +229,7 @@ Perform the following steps to connect and unlock hardware encrypted Data Box di
     > [!IMPORTANT]
     > SEDUtil is an external utility for Self-Encrypting Drives. This is not managed by Microsoft. More information, including license information for this utility, can be found at [https://sedutil.com/](https://sedutil.com/).
 
-1.	Extract `SEDUtil` to a local path on the machine and create a symbolic link to the utility path using the following example. Alternatively, you can add the utility paht to the `PATH` environment variable.
+1.	Extract `SEDUtil` to a local path on the machine and create a symbolic link to the utility path using the following example. Alternatively, you can add the utility path to the `PATH` environment variable.
 
     ```bash
     chmod +x /path/to/sedutil-cli
@@ -256,7 +256,7 @@ Perform the following steps to connect and unlock hardware encrypted Data Box di
 
     :::image type="content" source="media/data-box-disk-deploy-set-up/disk-serial.png" alt-text="Screen capture of example output of the sedutil tool showing identified volumes." lightbox="media/data-box-disk-deploy-set-up/disk-serial-lrg.png":::
    
-1.	Run the **Data Box Disk Unlock Utility** from the Linux toolset extracted in a previous step. Supply the passkey from the Azure portal you obtained from the **Connect to disks** section. Optionally, you can specify a list of Bitlocker encrypted volumes to unlock. The passkey and volume list should be specified within single quotes as shown in the following example.
+1.	Run the **Data Box Disk Unlock Utility** from the Linux toolset extracted in a previous step. Supply the passkey from the Azure portal you obtained from the **Connect to disks** section. Optionally, you can specify a list of BitLocker encrypted volumes to unlock. The passkey and volume list should be specified within single quotes as shown in the following example.
 
     ```bash
     chmod +x DataBoxDiskUnlock
@@ -267,9 +267,9 @@ Perform the following steps to connect and unlock hardware encrypted Data Box di
     sudo ./DataBoxDiskUnlock /Passkey:<'passkey'> /SerialNumbers:<'serialNumber1,serialNumber2'> /SED
     ```
    
-    The following example output indicates that the volume was successfully unlocked. The mount point is also displayed for the volume in whick your data can be copied.
+    The following example output indicates that the volume was successfully unlocked. The mount point is also displayed for the volume in which your data can be copied.
 
-    :::image type="content" source="media/data-box-disk-deploy-set-up/disk-unlocked.png" alt-text="Screen capture showing showing a successfully unlocked data box disk.":::
+    :::image type="content" source="media/data-box-disk-deploy-set-up/disk-unlocked.png" alt-text="Screen capture showing a successfully unlocked data box disk.":::
 
     > [!IMPORTANT]
     > Repeat the steps to unlock the disk for any future disk reinserts.
@@ -327,7 +327,7 @@ Perform the following steps to connect and unlock software encrypted Data Box di
     `chmod +x DataBoxDiskUnlock`
     `chmod +x DataBoxDiskUnlock_Prep.sh`
 
-    After the `chmod` command has been excuted, verify that the file permissions are changed by running the `ls` command as shown in the following sample output.
+    After the `chmod` command has been executed, verify that the file permissions are changed by running the `ls` command as shown in the following sample output.
 
     ```
         [user@localhost Downloads]$ chmod +x DataBoxDiskUnlock
@@ -337,7 +337,7 @@ Perform the following steps to connect and unlock software encrypted Data Box di
         -rwxrwxr-x. 1 user user 795 Aug 5 23:26 DataBoxDiskUnlock_Prep.sh
     ```
 
-1. Execute the following script to install the Data Box Disk Unlock binaries. Use `sudo` to run the command as root. An acknowledgement is displayed in the terminal to notify you of the successful installation.
+1. Execute the following script to install the Data Box Disk Unlock binaries. Use `sudo` to run the command as root. An acknowledgment is displayed in the terminal to notify you of the successful installation.
 
     `sudo ./DataBoxDiskUnlock_Prep.sh`
 

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

@@ -190,7 +190,7 @@ sections:
               
           1. After you place the order, the order is processed and the disks are prepared. You will be notified via an email that your order is ready for pickup. 
           2. Once the order is ready for pickup, go to your order in the Azure portal and navigate to the **Overview** blade. 
-          3. You will see a notification with a code in the Azure portal. Email the [Azure Data Box Operations team](mailto:[email protected]) and provide them the code. The team will provide the location and schedule a pickup date and time. You must call the team within 5 business days after you receive the email notification.
+          3. You will see a notification with a code in the Azure portal. Email the [Azure Data Box Operations team](mailto:[email protected]) and provide them with the code. The team will provide the location and schedule a pickup date and time. You must call the team within 5 business days after you receive the email notification.
           
           Once the data copy and validation is complete, take the following steps to return your disk:
           
@@ -200,7 +200,7 @@ sections:
               - Reuse the packaging from the initial shipment. We recommend that you pack disks using a well-secured bubbled wrap.
               - Make sure the fit is snug to reduce any movements within the box.
           3. Go to the **Overview blade** for your order in Azure portal. You should see a notification with a code.
-          4. Use that code and email the [Azure Data Box Operations team](mailto:[email protected]) and provide them the code. They would provide you information on where and when to drop off the disks.
+          4. Use that code and email the [Azure Data Box Operations team](mailto:[email protected]) and provide them with the code. They would provide you with information on where and when to drop off the disks.
           
           
   - name: Migrate data
@@ -223,7 +223,7 @@ sections:
       - question: |
           How do I know that my data is secure during transit? 
         answer: |
-          Data Box Disks are encrypted using BitLocker AES-128 bit encryption and the passkey is only available in the Azure portal. Log into the Azure portal using your account credentials to get the passkey. Supply this passkey when you run the Data Box Disk unlock tool.
+          Data Box Disks are encrypted using BitLocker AES-128 bit encryption and the passkey is only available in the Azure portal. Log in to the Azure portal using your account credentials to get the passkey. Supply this passkey when you run the Data Box Disk unlock tool.
 
       - question: |
           How do I copy the data to the Data Box Disks? 

articles/databox/data-box-disk-overview.md

@@ -22,7 +22,7 @@ If you want to import data to Azure Blob storage and Azure Files, you can use Az
 
 ## Use cases
 
-Use Data Box Disk to transfer TBs of data in scenarios with limited network connectivity. The data movement can be one-time, periodic, or an initial bulk data transfer followed by periodic transfers.
+Use Data Box Disk to transfer terabytes of data in scenarios with limited network connectivity. The data movement can be one-time, periodic, or an initial bulk data transfer followed by periodic transfers.
 
 - **One time migration** - when large amount of on-premises data is moved to Azure. For example, moving data from offline tapes to archival data in Azure cool storage.
 - **Incremental transfer** - when an initial bulk transfer is done using Data Box Disk (seed) followed by incremental transfers over the network. For example, Commvault and Data Box Disk are used to move backup copies to Azure. This migration is followed by copying incremental data using network to Azure Storage.
@@ -36,7 +36,7 @@ Azure providers and non-Azure providers can ingest data from Azure Data Box. The
 
 - **Azure File Sync** -  replicates files from your Data Box to an Azure file share, enabling you to centralize your file services in Azure while maintaining local access to your data. For more information, see [Deploy Azure File Sync](../storage/file-sync/file-sync-deployment-guide.md).
 
-- **HDFS stores** - migrate data from an on-premises Hadoop Distributed File System (HDFS) store of your Hadoop cluster into Azure Storage using Data Box. For more information, see [Migrate from on-prem HDFS store to Azure Storage with Azure Data Box](../storage/blobs/data-lake-storage-migrate-on-premises-hdfs-cluster.md).
+- **HDFS stores** - migrate data from an on-premises Hadoop Distributed File System (HDFS) store of your Hadoop cluster into Azure Storage using Data Box. For more information, see [Migrate from on-premises HDFS store to Azure Storage with Azure Data Box](../storage/blobs/data-lake-storage-migrate-on-premises-hdfs-cluster.md).
 
 - **Azure Backup** - allows you to move large backups of critical enterprise data through offline mechanisms to an Azure Recovery Services Vault. For more information, see [Azure Backup overview](../backup/backup-overview.md).
 

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

@@ -68,7 +68,7 @@ This step takes approximately 5 minutes.
 1. Create a new **Azure Data Box** resource in the Azure portal.
 2. Select a subscription enabled for this service and choose transfer type as **Import**. Provide the **Source country** where the data resides and **Azure destination region** for the data transfer.
 3. Select **Data Box Disk**. The maximum solution capacity is 35 TB and you can create multiple disk orders for larger data sizes.  
-4. Enter the order details and shipping information. Select either **Hardware encryption** (new) or **Software encryption** from the **Disk encryption type** drop down list. If the service is available in your region, provide notification email addresses, review the summary, and then create the order.
+4. Enter the order details and shipping information. Select either **Hardware encryption** (new) or **Software encryption** from the **Disk encryption type** drop-down list. If the service is available in your region, provide notification email addresses, review the summary, and then create the order.
 
 Once the order is created, the disks are prepared for shipment.
 

articles/databox/data-box-disk-system-requirements.md

@@ -33,7 +33,7 @@ The system requirements include the supported platforms for clients connecting t
 2. You have a client computer available from which you can copy the data. Your client computer must:
 
     - Run a supported operating system.
-    - Have other required software installed.
+    - Have any additional required software installed.
 
 ::: zone-end
 
@@ -98,7 +98,7 @@ The following additional software is required.
 > [!Note]
 > Classic storage accounts are not supported beginning **August 1, 2023**.
 
-The follow table contains supported storage types for Data Box Disks.
+The following table contains supported storage types for Data Box Disks.
 
 | **Storage account** | **Supported access tiers** |
 | --- | --- |

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

@@ -90,7 +90,7 @@ The issues seen when using a Split Copy tool to split the data over multiple dis
 |---------|---------|
 |[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: 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 sessions. <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.|
 |[Info] Destination file or directory name exceeds the NTFS length limit. |This message is reported when the destination file was renamed because of long file path.<br> Modify the disposition option in `config.json` file to control this behavior.|
 |[Error] Exception thrown: Bad JSON escape sequence. |This message is reported when the config.json has format that is not valid. <br> Validate your `config.json` using [JSONlint](https://jsonlint.com/) before you save the file.|