Update data-box-troubleshoot-data-upload.md

Author: LakshJ-MS

articles/databox/data-box-troubleshoot-data-upload.md

@@ -1,6 +1,6 @@
 ---
-title: Review copy errors in uploads from Azure Data Box, Data Box Next Gen, and Azure Data Box Heavy devices
-description: Describes review and follow-up for errors during uploads from an Azure Data Box, Data Box Next Gen, and Azure Data Box Heavy device to the Azure cloud.
+title: Review copy errors in uploads from Azure Data Box, Data Box Next-Gen, and Azure Data Box Heavy devices
+description: Describes review and follow-up for errors during uploads from an Azure Data Box, Data Box Next-Gen, and Azure Data Box Heavy device to the Azure cloud.
 services: databox
 author: v-dalc
 
@@ -10,7 +10,7 @@ ms.date: 03/06/2025
 ms.author: shaas
 ---
 
-# Review copy errors in uploads from Azure Data Box, Data Box Next Gen, and Azure Data Box Heavy devices
+# Review copy errors in uploads from Azure Data Box, Data Box Next-Gen, and Azure Data Box Heavy devices
 
 This article describes review and follow-up for errors that occasionally prevent files from uploading to the Azure cloud from an Azure Data Box or Azure Data Box Heavy device.
 
@@ -19,7 +19,7 @@ The error notification and options vary depending on whether you can fix the err
 - **Retryable errors** - You can fix many types of copy error and resume the upload. The data is then successfully uploaded in your current order. 
 
 
-    An example of a retryable error is when Large File Shares are not enabled for a storage account that requires shares with data more than 5 TiB. To resolve this, you will need to enable this setting and then confirm to resume data copy. This type of error is referred to as a *retryable error* in the discussion that follows.
+    An example of a retryable error is when Large File Shares aren't enabled for a storage account that requires shares with data more than 5 TiB. To resolve this, you will need to enable this setting and then confirm to resume data copy. This type of error is referred to as a *retryable error* in the discussion that follows.
 
 - **Non-retryable errors** - These are errors that can't be fixed. For those errors, the upload pauses to give you a chance to review the errors. But the order completes without the data that failed to upload, and the data is secure erased from the device. You'll need to create a new order after you resolve the issues in your data. 
 
@@ -101,7 +101,7 @@ When the following errors occur, you can resolve the errors and include the file
 
 |Error message  |Error description |Error resolution |
 |---------------|------------------|-----------------|
-|Large file share not enabled on account |Large file shares aren’t enabled on one or more storage accounts. Resolve the error and resume data copy, or skip to data erasure and complete the order. | Large file shares are not enabled on the indicated storage accounts. Select the option highlighted to enable quota up to 100 TiB per share.|
+|Large file share not enabled on account |Large file shares aren’t enabled on one or more storage accounts. Resolve the error and resume data copy, or skip to data erasure and complete the order. | Large file shares aren't enabled on the indicated storage accounts. Select the option highlighted to enable quota up to 100 TiB per share.|
 |Storage account deleted or moved |One or more storage accounts were moved or deleted. Resolve the error and resume data copy, or skip to data erasure and complete the order. |**Storage accounts deleted or moved**<br>Storage accounts: &lt;*storage accounts list*&gt; were either deleted, or moved to a different subscription or resource group. Recover or re-create the storage accounts with the original set of properties, and then confirm to resume data copy.<br>[Learn more on how to recover a storage account](../storage/common/storage-account-recover.md). |
 |Storage account location changed |One or more storage accounts were moved to a different region. Resolve the error and resume data copy, or skip to data erasure and complete the order. |**Storage accounts location changed**<br>Storage accounts: &lt;*storage accounts list*&gt; were moved to a different region. Restore the account to the original destination region and then confirm to resume data copy.<br>[Learn more on how to move storage accounts](../storage/common/storage-account-move.md). |
 |Virtual network restriction on storage account |One or more storage accounts are behind a virtual network and have restricted access. Resolve the error and resume data copy, or skip to data erasure and complete the order. |**Storage accounts behind virtual network**<br>Storage accounts: &lt;*storage accounts list*&gt; were moved behind a virtual network. Add Data Box to the list of trusted services to allow access and then confirm to resume data copy.<br>[Learn more about trusted first party access](../storage/common/storage-network-security.md#exceptions). |
@@ -189,7 +189,7 @@ Other REST API errors might occur during data uploads. For more information, see
 
 **Error description:** If a blob storage container is configured as Write Once, Read Many (WORM), upload of any blobs that are already stored in the container will fail.
 
-**Follow-up:** You can't fix this error in the current upload. The upload has completed with errors. Before you do a network transfer or start a new import order, make sure the listed blobs are not part of an immutable storage container. For more information, see [Store business-critical blob data with immutable storage](../storage/blobs/immutable-storage-overview.md).
+**Follow-up:** You can't fix this error in the current upload. The upload has completed with errors. Before you do a network transfer or start a new import order, make sure the listed blobs aren't part of an immutable storage container. For more information, see [Store business-critical blob data with immutable storage](../storage/blobs/immutable-storage-overview.md).
 
 
 ### The total provisioned capacity of the shares cannot exceed the account maximum size limit
@@ -230,7 +230,7 @@ Other REST API errors might occur during data uploads. For more information, see
 
 **Error code:** 409
 
-**Error description:** The listed page blobs failed to upload because they are not a size that can be converted to a Managed Disk. To be converted to a Managed Disk, a page blob must be from 20 MB (20,971,520 Bytes) to 8192 GiB in size.
+**Error description:** The listed page blobs failed to upload because they aren't a size that can be converted to a Managed Disk. To be converted to a Managed Disk, a page blob must be from 20 MB (20,971,520 Bytes) to 8192 GiB in size.
 
 **Follow-up:** You can't fix this error in the current upload. The upload has completed with errors. Before you do a network transfer or start a new import order, make sure each listed blob is from 20 MB to 8192 GiB in size.
 
@@ -239,4 +239,4 @@ Other REST API errors might occur during data uploads. For more information, see
 ## Next steps
 
 - [Review common REST API errors](/rest/api/storageservices/common-rest-api-error-codes).
-- [Verify data upload to Azure](data-box-deploy-picked-up.md#verify-data-has-uploaded-to-azure)
+- [Verify data upload to Azure](data-box-deploy-picked-up.md#verify-data-has-uploaded-to-azure)