Updated regin tables for DBH and other SKUs.

stevenmatthew · stevenmatthew · commit 409d6d7189ba · 2024-05-30T16:15:23.000-07:00
diff --git a/articles/databox/data-box-heavy-overview.md b/articles/databox/data-box-heavy-overview.md
@@ -13,28 +13,28 @@ ms.author: shaas
 
 # What is Azure Data Box Heavy?
 
-Azure Data Box Heavy allows you to send hundreds of terabytes of data to Azure in a quick, inexpensive, and reliable way. The data is transferred to Azure by shipping you a Data Box Heavy device with 1-PB storage capacity, which you fill with your data and send back to Microsoft. The device has a rugged casing to protect and secure your data during transit.
+Azure Data Box Heavy is a service that allows you to transfer hundreds of terabytes of data to Azure in a quick, inexpensive, and reliable way. 
 
-Once the device is received at your datacenter, set it up using the local web UI. Copy the data from your servers to the device and ship the device back to Azure. In the Azure datacenter, your data is uploaded to your Azure Storage account(s). You can track the entire end-to-end process in the Azure portal.
+The transfer process begins when a Data Box Heavy device with 1-PB storage capacity is shipped to your data center. After the device is received, set it up using the local web UI and copy your data to the device and return it to Microsoft. The device has a rugged case that protects and secures your data during transit. Your data is uploaded to your Azure Storage account after the device arrives at the Azure datacenter.
 
+You can track the entire end-to-end process in the Azure portal.
 
 > [!IMPORTANT]
 > - To request a device, sign up in the [Azure portal](https://portal.azure.com).
 
-
 ## Use cases
 
-Data Box Heavy is best suited for data sizes in the hundreds of terabytes, where network connectivity is insufficient to upload the data to Azure. The data movement can be one-time, periodic, or an initial bulk data transfer followed by periodic transfers. Here are the various scenarios where Data Box Heavy can be used for data transfer.
+Data Box Heavy is best suited for data sizes in the hundreds of terabytes, and in scenarios where network connectivity is insufficient to upload your data to Azure. The data movement can be one-time, periodic, or an initial bulk data transfer followed by periodic transfers. The following scenarios contain examples illustrating how Data Box Heavy can be used for data transfer.
 
- - **One time migration** - when large amount of on-premises data is moved to Azure.
-     - Move a media library from offline tapes into Azure to create an online media library.
-     - Migrate your VM farm, SQL server, and applications to Azure.
+ - **One time migration** - Appropriate when large amount of on-premises data is moved to Azure.
+     - Create an online media library by moving offline tapes into Azure.
+     - Migrate your virtual machine (VM) farm, SQL server, and applications to Azure.
      - Move historical data to Azure for in-depth analysis and report using HDInsight.
 
- - **Initial bulk transfer** - when an initial bulk transfer is done using Data Box Heavy (seed) followed by incremental transfers over the network.
-     - For example, Data Box Heavy and a backup solutions partner are used to move initial large historical backup to Azure. Once complete, the incremental data is transferred via network to Azure storage.
+ - **Initial bulk transfer** - Use Data Box Heavy to complete an initial bulk transfer, or *seed*, followed by incremental transfers over the network.
+     - For example, Data Box Heavy and a backup solutions partner are used to move initial large historical backup to Azure. After the initial transfer is complete, the incremental data is transferred via network to Azure storage.
 
- - **Periodic uploads** - when large amount of data is generated periodically and needs to be moved to Azure. For example in energy exploration, where video content is generated on oil rigs and windmill farms.
+ - **Periodic uploads** - Ideal for transferring large amounts of periodically generated data. For example, a scenario where video content is generated on oil rigs and windmill farms for use in energy exploration.
 
 ## Benefits
 
@@ -43,8 +43,8 @@ Data Box Heavy is designed to move massive amounts of data to Azure with little
 - **Speed** - Data Box Heavy uses high-performance 40-Gbps network interfaces.
 
 - **Security** - Data Box Heavy has built-in security protections for the device, data, and the service.
-    - The device has a rugged device casing secured by tamper-resistant screws and tamper-evident stickers.
-    - The data on the device is secured with an AES 256-bit encryption at all times.
+    - The device has a rugged device case secured by tamper-resistant screws and tamper-evident stickers.
+    - The data on the device is secured with AES 256-bit encryption at all times.
     - The device can only be unlocked with a password provided in the Azure portal.
     - The service is protected by the Azure security features.
     - Once your data is uploaded to Azure, the disks on the device are wiped clean, in accordance with National Institute of Standards and Technology (NIST) 800-88r1 standards.
@@ -57,11 +57,11 @@ Data Box Heavy is designed to move massive amounts of data to Azure with little
 
 Previous releases of Data Box, Data Box Disk, and Data Box Heavy didn’t support cross-region data transfer. With the exception of transfers both originating and terminating between the United Kingdom (UK) and the European Union (EU), data couldn’t cross commerce boundaries.
 
-Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. Data is transferred between regions using the Azure network and incurs no additional cost.
+Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. It's important to note that the Data Box device isn't shipped across commerce boundaries. Instead, it's transported to an Azure data center within the originating country or region. Data transfer between the source country and the destination region takes place using the Azure network and incurs no additional cost.
 
-Note that although cross-region data transfer currently doesn’t incur additional costs, functionality is presently in preview and subject to change. Note, too, that in some scenarios data transfers might be crossing large geographic areas. Higher than normal latencies may be encountered during such transfers.
+Although cross-region data transfer doesn't incur additional costs, the functionality is currently in preview and subject to change. Note, too, that some data transfer scenarios take place over large geographic areas. Higher than normal latencies might be encountered during such transfers.
 
-At present, cross-region transfers are supported between the following between the following countries and regions:
+Cross-region transfers are currently supported between the following countries and regions:
 
 | Source Country |  Destination Region |
 |----------------|---------------------|
@@ -71,18 +71,18 @@ At present, cross-region transfers are supported between the following between t
 <sup>1</sup>US denotes all Azure regions in which Data Box is supported across the United States.<br>
 <sup>2</sup>EU denotes all Azure regions in which Data Box is supported across the European Union. 
 
-Data transfers not represented within the preceding table represent unsupported cross-commerce boundary transfer selections. For more information, or if your region combination is unsupported, please contact the [Azure Data Box team](mailto:azuredbx@microsoft.com).
+Data transfers not represented within the preceding table represent unsupported cross-commerce boundary transfer selections. If you need more information, or if your region combination is unsupported, contact the [Azure Data Box team](mailto:azuredbx@microsoft.com).
 
 The Data Box Heavy device has the following features in this release.
 
 | Specifications                                          | Description              |
 |---------------------------------------------------------|--------------------------|
 | Weight                                                  | ~ 500 lbs. <br>Device on locking wheels for transport|
 | Dimensions                                              | Width: 26 inches Height: 28 inches Length: 48 inches |
-| Rack space                                              | Cannot be rack-mounted|
-| Cables required                                         | 4 grounded 120 V / 10 A power cords (NEMA 5-15) included <br> Device supports up to 240 V power and has C-13 power receptacles <br> Use network cables compatible with Mellanox MCX314A-BCCT  |
-| Power                                                    | 4 built-in power supply units (PSUs) shared across both the device nodes <br> 1,200 watt typical power draw|
-| Storage capacity                                        | ~ 1-PB raw, 70 disks of 14 TB each <br> 770-TB usable capacity|
+| Rack space                                              | Can't be rack-mounted|
+| Cables required                                         | 4 grounded 120 V / 10 A power cords (NEMA 5-15) included <br> Device supports up to 240V power and has C-13 power receptacles <br> Use network cables compatible with Mellanox MCX314A-BCCT  |
+| Power                                                    | 4 built-in power supply units (PSUs) shared across both the device nodes <br> 1,200-watt typical power draw|
+| Storage capacity                                        | ~ 1 PB raw, 70 disks of 14 TB each <br> 770-TB usable capacity|
 | Number of nodes                                          | 2 independent nodes per device (500 TB each) |
 | Network interfaces per node                             | 4 network interfaces per node <br><br> MGMT, DATA3 <ul><li> 2 X 1-GbE interfaces </li><li> MGMT is for management and initial setup, not user configurable </li><li> DATA3 is user-configurable and Dynamic Host Configuration Protocol (DHCP) by default</li></ul>DATA1, DATA2 data interfaces <ul><li>2 X 40-GbE interfaces </li><li> User configurable for DHCP (default) or static</li></ul>|
 
diff --git a/includes/data-box-cross-region.md b/includes/data-box-cross-region.md
@@ -11,9 +11,9 @@ ms.author: shaas
 
 Previous releases of Data Box, Data Box Disk, and Data Box Heavy didn’t support cross-region data transfer. With the exception of transfers both originating and terminating between the United Kingdom (UK) and the European Union (EU), data couldn’t cross commerce boundaries.
 
-Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. Data is transferred between regions using the Azure network and incurs no additional cost.
+Data Box cross-region data transfer capabilities, now in preview, support offline seamless cross-region data transfers between many regions. This capability allows you to copy your data from a local source and transfer it to a destination within a different country, region, or boundary. It's important to note that the Data Box device isn't shipped across commerce boundaries. Instead, it's transported to an Azure data center within the originating country or region. Data transfer between the source country and the destination region takes place using the Azure network and incurs no additional cost.
 
-Note that although cross-region data transfer currently doesn’t incur additional costs, functionality is presently in preview and subject to change. Note, too, that in some scenarios data transfers might be crossing large geographic areas. Higher than normal latencies may be encountered during such transfers.
+Although cross-region data transfer doesn't incur additional costs, the functionality is currently in preview and subject to change. Note, too, that some data transfer scenarios take place over large geographic areas. Higher than normal latencies might be encountered during such transfers.
 
 Cross-region transfers are currently supported between the following countries and regions:
 
