First round editorial fixes per Balaji

stevenmatthew · stevenmatthew · commit 00e259eac522 · 2024-03-10T19:21:30.000-07:00
diff --git a/articles/databox/data-box-deploy-copy-data.md b/articles/databox/data-box-deploy-copy-data.md
@@ -7,7 +7,7 @@ author: stevenmatthew
 ms.service: databox
 ms.subservice: pod
 ms.topic: tutorial
-ms.date: 02/27/2024
+ms.date: 03/10/2024
 ms.author: shaas
 
 # Customer intent: As an IT admin, I need to be able to copy data to Data Box to upload on-premises data from my server onto Azure.
@@ -66,7 +66,6 @@ The following table shows the UNC path to the shares on your Data Box and the co
 | Azure Block blobs | <li>UNC path to shares: `\\<DeviceIPAddress>\<storageaccountname_BlockBlob>\<accessTier>\<ContainerName>\myFile.txt`</li><li>Azure Storage URL: `https://<storageaccountname>.blob.core.windows.net/<ContainerName>/myFile.txt`</li> |  
 | Azure Page blobs  | <li>UNC path to shares: `\\<DeviceIPAddress>\<storageaccountname_PageBlob>\<ContainerName>\myFile.txt`</li><li>Azure Storage URL: `https://<storageaccountname>.blob.core.windows.net/<ContainerName>/myFile.txt`</li>   |  
 | Azure Files       |<li>UNC path to shares: `\\<DeviceIPAddress>\<storageaccountname_AzFile>\<ShareName>\myFile.txt`</li><li>Azure Storage URL: `https://<storageaccountname>.file.core.windows.net/<ShareName>/myFile.txt`</li>        | 
-<!--| Azure Block blobs (Archive)   | <li>UNC path to shares: `\\<DeviceIPAddress>\<storageaccountname_BlockBlob_Archive>\<ContainerName>\files\a.txt`</li><li>Azure Storage URL: `https://<storageaccountname>.blob.core.windows.net/<ContainerName>/files/a.txt`</li>      | -->
 
 If using a Windows Server host computer, follow these steps to connect to the Data Box.
 
diff --git a/articles/databox/data-box-disk-deploy-copy-data.md b/articles/databox/data-box-disk-deploy-copy-data.md
@@ -7,7 +7,7 @@ author: stevenmatthew
 ms.service: databox
 ms.subservice: disk
 ms.topic: tutorial
-ms.date: 11/18/2022
+ms.date: 03/10/2024
 ms.author: shaas
 ---
 
@@ -59,7 +59,7 @@ Before you begin, make sure that:
 
 Review the following considerations before you copy the data to the disks:
 
-- It is your responsibility to ensure that you copy your local data to the folders that correspond to the appropriate data format. For instance, copy block blob data to the folder corrresponding to the appropriate access tier within the *BlockBlob* folder. Frequently used block blobs should be copies to the *Hot* tier's folder within *BlockBlob*. Blobs being archived should be copied to the *BlockBlob_Archive* folder. 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.
+- It is your responsibility to ensure that you copy your local data to the folders that correspond to the appropriate data format. For instance, copy block blob data to the folder corrresponding to the appropriate access tier within the *BlockBlob* folder. Frequently used block blobs should be copies to the *Hot* tier's folder within *BlockBlob*. Likewise, blobs being uploaded to the *archive* tier should be copied to the *Archive* folder. 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.
 
    > [!IMPORTANT]
    > Data uploaded to the archive tier remains offline and needs to be rehydrated before reading or modifying. Data copied to the archive tier must remain for at least 180 days or be subject to an early deletion charge. Archive tier is not supported for ZRS, GZRS, or RA-GZRS accounts.
diff --git a/articles/databox/data-box-disk-limits.md b/articles/databox/data-box-disk-limits.md
@@ -7,7 +7,7 @@ author: stevenmatthew
 ms.service: databox
 ms.subservice: disk
 ms.topic: article
-ms.date: 12/29/2022
+ms.date: 03/10/2024
 ms.author: shaas
 ---
 # Azure Data Box Disk limits
@@ -73,7 +73,7 @@ Here are the sizes of the Azure objects that can be written. Make sure that all
 |-------------------|-----------------------------------------------------------|
 | Block blob        | 7 TiB                                                  |
 | Page blob         | 4 TiB <br> Every file uploaded in page blob format must be 512 bytes aligned (an integral multiple), else the upload fails. <br> VHD and VHDX are 512 bytes aligned. |
-| Azure Files        | 1 TiB                                                      |
+| Azure Files        | 4 TiB                                                      |
 | Managed disks     | 4 TiB <br> For more information on size and limits, see: <li>[Scalability targets of Standard SSDs](../virtual-machines/disks-types.md#standard-ssds)</li><li>[Scalability targets of Premium SSDs](../virtual-machines/disks-types.md#standard-hdds)</li><li>[Scalability targets of Standard HDDs](../virtual-machines/disks-types.md#premium-ssds)</li><li>[Pricing and billing of managed disks](../virtual-machines/disks-types.md#billing)</li>
 
 ## Azure block blob, page blob, and file naming conventions
diff --git a/articles/databox/data-box-disk-quickstart-portal.md b/articles/databox/data-box-disk-quickstart-portal.md
@@ -6,7 +6,7 @@ author: stevenmatthew
 ms.service: databox
 ms.subservice: disk
 ms.topic: quickstart
-ms.date: 11/04/2020
+ms.date: 03/10/2024
 ms.author: shaas
 ms.custom: mode-ui, devx-track-azurecli
 #Customer intent: As an IT admin, I need to quickly deploy Data Box Disk so as to import data into Azure.
@@ -166,7 +166,7 @@ This step takes roughly 5 minutes.
 
 The time to complete this operation depends upon your data size.
 
-1. The drive contains *PageBlob*, *BlockBlob*, *AzureFile*, *ManagedDisk*, and *DataBoxDiskImport* folders. Within the *BlockBBlob* root folder, you'll find a sub-folder corresponding to each of the available access tiers. 
+1. The drive contains *PageBlob*, *BlockBlob*, *AzureFile*, *ManagedDisk*, and *DataBoxDiskImport* folders. Within the *BlockBlob* root folder, you'll find a sub-folder corresponding to each of the available access tiers. 
 
     Drag and drop data such as VHD/VHDX to *PageBlob* folder, and appropriate data to *AzureFile*. Copy any VHDs that you want to upload as managed disks to a folder under *ManagedDisk*.
 
@@ -178,7 +178,7 @@ The time to complete this operation depends upon your data size.
 
     > [!NOTE]
     > - All the containers, blobs, and files should conform to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). If these rules are not followed, the data upload to Azure will fail.
-    > - Ensure that files do not exceed ~4.75 TiB for block blobs, ~8 TiB for page blobs, and ~1 TiB for Azure Files.
+    > - Ensure that files do not exceed ~4.75 TiB for block blobs, ~8 TiB for page blobs, and ~4 TiB for Azure Files.
 
 2. **(Optional but recommended)** After the copy is complete, we strongly recommend that at a minimum you run the `DataBoxDiskValidation.cmd` provided in the *DataBoxDiskImport* folder and select option 1 to validate the files. We also recommend that time permitting, you use option 2 to also generate checksums for validation (may take time depending upon the data size). These steps minimize the chances of any failures when uploading the data to Azure.
 3. Safely remove the drive.
diff --git a/includes/data-box-object-size-limits.md b/includes/data-box-object-size-limits.md
@@ -3,7 +3,7 @@ author: stevenmatthew
 ms.service: databox
 ms.subservice: heavy   
 ms.topic: include
-ms.date: 01/24/2022
+ms.date: 03/10/2024
 ms.author: shaas
 ---
 
@@ -13,6 +13,6 @@ Here are the sizes of the Azure objects that can be written. Make sure that all
 |-------------------|-----------------------------------------------------------|
 | Block blob        | 14 TiB                                                  |
 | Page blob         | 4 TiB <br> Every file uploaded in page blob format must be 512 bytes aligned (an integral multiple), else the upload fails. <br> VHD and VHDX are 512 bytes aligned. |
-| Azure Files        | 1 TiB                                                      |
+| Azure Files        | 4 TiB                                                      |
 | Managed disks     | 4 TiB <br> For more information on size and limits, see: <li>[Scalability targets of Standard SSDs](../articles/virtual-machines/disks-types.md#standard-ssds)</li><li>[Scalability targets of Premium SSDs](../articles/virtual-machines/disks-types.md#standard-hdds)</li><li>[Scalability targets of Standard HDDs](../articles/virtual-machines/disks-types.md#premium-ssds)</li><li>[Pricing and billing of managed disks](../articles/virtual-machines/disks-types.md#billing)</li>  
 
