Fixes per Acrolinx

Author: stevenmatthew

articles/databox-gateway/data-box-gateway-1905-release-notes.md

@@ -17,7 +17,7 @@ ms.author: shaas
 
 The following release notes identify the critical open issues and the resolved issues for the 1905 release for Azure Data Box Edge and Azure Data Box Gateway.
 
-The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they are added. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes. 
+The release notes are continuously updated, and critical issues requiring a workaround are added as they're discovered. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes. 
 
 This release corresponds to the software versions:
 
@@ -29,11 +29,11 @@ This release corresponds to the software versions:
 
 ## What's new
 
-- **Field Programmable Gate Array (FPGA) logging improvements** -  In this release, we have made logging and alert enhancements related to FPGA. This is a required update for Data Box Edge if you are using the Edge compute feature with the FPGA. For more information, see how to [transform data with Edge compute on your Data Box Edge](../databox-online/azure-stack-edge-deploy-configure-compute-advanced.md).
+- **Field Programmable Gate Array (FPGA) logging improvements** -  This release includes improvements in logging and alert enhancements related to  field-programmable gate arrays (FPGAs). This update is required for Data Box Edge if you're using the Edge compute feature with the FPGA. For more information, see how to [transform data with Edge compute on your Data Box Edge](../databox-online/azure-stack-edge-deploy-configure-compute-advanced.md).
 
 ## Known issues in GA release
 
-No new issues are release noted for this release. All the release noted issues have carried over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
+No new issues are release noted for this release. All the release noted issues are carried over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
 
 
 ## Next steps

articles/databox-gateway/data-box-gateway-1906-release-notes.md

@@ -13,9 +13,9 @@ ms.author: shaas
 
 # Azure Data Box Edge and Azure Data Box Gateway 1906 release notes
 
-The following release notes identify the critical open issues and the resolved issues for the 1906 release for Azure Data Box Edge and Azure Data Box Gateway. 
+The following release notes identify the critical open issues and the resolved issues for the 1906 release for Azure Data Box Edge and Azure Data Box Gateway.
 
-The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they are added. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes.
+The release notes are continuously updated, and critical issues requiring a workaround are added as they're discovered. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes.
 
 This release corresponds to the software versions:
 
@@ -27,13 +27,12 @@ This release corresponds to the software versions:
 
 ## What's new
 
-- **Bug fix in the recovery key management workflow** -  In the earlier release, there was a bug owing to which the recovery key was not getting applied. This bug is fixed in this release. We strongly recommend that you apply this update as the recovery key allows you to recover the data on the device, in the event the device doesn't boot up. For more information, see how to [save the recovery key when deploying Data Box Edge or Data Box Gateway](../databox-online/azure-stack-edge-deploy-connect-setup-activate.md#set-up-and-activate-the-physical-device).
-- **Field Programmable Gate Array (FPGA) logging improvements** -  Starting 1905 release, logging and alert enhancements related to FPGA were made. This continues to be a required update for Data Box Edge if you are using the Edge compute feature with the FPGA. For more information, see how to [transform data with Edge compute on your Data Box Edge](../databox-online/azure-stack-edge-deploy-configure-compute-advanced.md).
+- **Bug fix in the recovery key management workflow** - In the earlier release, there was a bug owing to which the recovery key wasn't getting applied. This bug is fixed in this release. We strongly recommend that you apply this update as the recovery key allows you to recover the data on the device if the device doesn't boot. For more information, see how to [save the recovery key when deploying Data Box Edge or Data Box Gateway](../databox-online/azure-stack-edge-deploy-connect-setup-activate.md#set-up-and-activate-the-physical-device).
+- **Field Programmable Gate Array (FPGA) logging improvements** - Starting in the 1905 release, both logging and alert enhancements related to Field Programmable Gate Arrays (FPGA) were made. This update continues to be required for Data Box Edge if you're using the Edge compute feature with the FPGA. For more information, see how to [transform data with Edge compute on your Data Box Edge](../databox-online/azure-stack-edge-deploy-configure-compute-advanced.md).
 
 ## Known issues in GA release
 
-No new issues are release noted for this release. All the release noted issues have carried over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
-
+No new issues are release noted for this release. All the release noted issues carry over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
 
 ## Next steps
 

articles/databox-gateway/data-box-gateway-2101-release-notes.md

@@ -15,7 +15,7 @@ ms.author: shaas
 
 The following release notes identify the critical open issues and the resolved issues for the 2101 release of Azure Data Box Gateway.
 
-The release notes are continuously updated. As critical issues that require a workaround are discovered, they are added. Before you deploy your Azure Data Box Gateway, carefully review the information in the release notes.  
+The release notes are continuously updated. Critical issues that require a workaround are added as they're discovered. Before you deploy your Azure Data Box Gateway, carefully review the information in the release notes.  
 
 This release corresponds to the software versions:
 
@@ -28,16 +28,16 @@ This release corresponds to the software versions:
 
 This release contains the following bug fix:
 
-- **Upload issue** - This release fixes an upload problem where upload restarts because of failures can slow the rate of upload completion. This problem can occur when uploading a dataset that primarily consists of files that are large in size relative to available bandwidth, particularly, but not limited to, when bandwidth throttling is active. This change ensures sufficient opportunity for upload completion before restarting upload for a given file.
+- **Upload issue** - This release fixes an upload problem where upload restarts because of failures can slow the rate of upload completion. This problem can occur when uploading datasets consisting primarily of files that are large in size relative to available bandwidth, particularly, but not limited to, when bandwidth throttling is active. This change ensures sufficient opportunity for upload completion before restarting upload for a given file.
 
 This release also contains the following updates:
 
-- All cumulative Windows updates and .NET framework updates released through October 2020.
+- All cumulative Windows and .NET framework updates released through October 2020.
 - The static IP address for Azure Data Box Gateway is retained across software updates.
 
 ## Known issues in this release
 
-No new issues are release noted for this release. All the release noted issues have carried over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
+No new issues are release noted for this release. All the release noted issues are carried over from the previous releases. To see a list of known issues, go to [Known issues in the GA release](data-box-gateway-release-notes.md#known-issues-in-ga-release).
 
 ## Next steps
 

articles/databox-gateway/data-box-gateway-release-notes.md

@@ -17,7 +17,7 @@ ms.author: shaas
 
 The following release notes identify the critical open issues and the resolved issues for General Availability (GA) release for Azure Data Box Edge and Azure Data Box Gateway. 
 
-The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they are added. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes.
+The release notes are continuously updated, and critical issues requiring a workaround are added as they're discovered. Before you deploy your Data Box Edge/Data Box Gateway, carefully review the information contained in the release notes.
 
 The GA release corresponds to the software versions:
 
@@ -27,7 +27,7 @@ The GA release corresponds to the software versions:
 
 ## What's new
 
-- **New virtual disk images** - New VHDX and VMDK are now available in the Azure portal. Download these images to provision, configure, and deploy new Data Box Gateway GA devices. The Data Box Gateway devices created in the earlier preview releases cannot be updated to this version. For more information, go to [Prepare to deploy Azure Data Box Gateway](data-box-gateway-deploy-prep.md).
+- **New virtual disk images** - New VHDX and VMDK are now available in the Azure portal. Download these images to provision, configure, and deploy new Data Box Gateway GA devices. The Data Box Gateway devices created in the earlier preview releases can't be updated to this version. For more information, go to [Prepare to deploy Azure Data Box Gateway](data-box-gateway-deploy-prep.md).
 - **NFS support** - NFS support is currently in preview and available for v3.0 and v4.1 clients that access the Data Box Edge and Data Box Gateway devices.
 - **Storage resiliency** - Your Data Box Edge device can withstand the failure of one data disk with the Storage resiliency feature. This feature is currently in preview. You can enable storage resiliency by selecting the **Resilient** option in the **Storage settings** in the local web UI.
 
@@ -38,9 +38,9 @@ The following table provides a summary of known issues for the Data Box Gateway
 
 | No. | Feature | Issue | Workaround/comments |
 | --- | --- | --- | --- |
-| **1.** |File types | The following file types are not supported: character files, block files, sockets, pipes, symbolic links.  |Copying these files results in 0-length files getting created on the NFS share. These files remain in an error state and are also reported in *error.xml*. <br> Symbolic links to directories result in directories never getting marked offline. As a result, you may not see the gray cross on the directories that indicates that the directories are offline and all the associated content was completely uploaded to Azure. |
-| **2.** |Deletion | Due to a bug in this release, if an NFS share is deleted, then the share may not be deleted. The share status will display *Deleting*.  |This occurs only when the share is using an unsupported file name. |
-| **3.** |Copy | Data copy fails with Error:  The requested operation could not be completed due to a file system limitation.  |The Alternate Data Stream (ADS) associated with file size greater than 128 KB is not supported.   |
+| **1.** |File types | The following file types aren't supported: character files, block files, sockets, pipes, symbolic links.  |Copying these files results in 0-length files getting created on the NFS share. These files remain in an error state and are also reported in *error.xml*. <br> Symbolic links to directories result in directories never getting marked offline. As a result, you may not see the gray cross on the directories that indicates that the directories are offline and all the associated content was uploaded to Azure. |
+| **2.** |Deletion | Due to a bug in this release, if an NFS share is deleted, then the share may not be deleted. The share status displays *Deleting*.  |This occurs only when the share is using an unsupported file name. |
+| **3.** |Copy | Data copy fails with Error:  The requested operation couldn't be completed due to a file system limitation.  |The Alternate Data Stream (ADS) associated with file size greater than 128 KB is not supported.   |
 
 
 ## Next steps