More acrolinx feedback on writing style.

Author: fauhse

includes/storage-files-migration-namespace-mapping.md

@@ -11,7 +11,7 @@ ms.subservice: files
 
 In this step, you are evaluating how many Azure file shares you need. A single Windows Server (or cluster) can sync up to 30 Azure file shares.
 
-You may have more folders on your volumes that you currently share out locally as SMB shares to your users and apps. The easiest would be to envision for an on-premises share to map 1:1 to an Azure file share. If this number is manageably small, meaning below 30 for a single Windows Server, or you plan on having two Windows Servers (60) and so on, then a 1:1 mapping is recommended.
+You may have more folders on your volumes that you currently share out locally as SMB shares to your users and apps. The easiest would be to envision for an on-premises share to map 1:1 to an Azure file share. If you have a small enough number, below 30 for a single Windows Server, then a 1:1 mapping is recommended.
 
 If you have more shares than 30, it is often unnecessary to map an on-premises share 1:1 to an Azure file share.
 Consider the following options:
@@ -25,7 +25,11 @@ For instance, if your HR department has a total of 15 shares, then you could con
 Azure File Sync supports syncing the root of a volume to an Azure file share.
 If you sync the root folder, then all subfolders and files will end up in the same Azure file share.
 
-Synching the root of the volume will not always be the best answer. There are benefits in syncing multiple locations, doing so helps keep the number of items lower per sync scope. Setting up Azure File Sync with a lower number of items is not just beneficial for file sync. A lower number of items also benefits other scenarios like a cloud-side restore from a backup and aids the speed of disaster recovering an on-premises server, to mention a few.
+Synching the root of the volume will not always be the best answer. There are benefits in syncing multiple locations, doing so helps keep the number of items lower per sync scope. Setting up Azure File Sync with a lower number of items is not just beneficial for file sync. A lower number of items also benefits other scenarios like:
+
+* cloud-side restore from an Azure file share snapshot taken as a backup
+* disaster recovery of an on-premises server can speed up significantly
+* changes made directly in an Azure file share (outside of sync) can be detected and synced faster
 
 #### A structured approach to a deployment map
 
@@ -34,7 +38,7 @@ Before deploying cloud storage in a subsequent step, it is important to create a
 To make the decision about how many Azure file shares you need, review the following limits and best practices. Doing so will help you optimize your map:
 
 * A server with the Azure File Sync agent installed, can sync with up to 30 Azure file shares.
-* An Azure file share is deployed inside of a storage account. That makes the storage account a scale target for performance numbers such as IOPS and throughput. Two standard (not premium) Azure file shares could theoretically saturate the maximum performance a storage account can deliver. If you plan to just attach Azure File Sync to these file shares with occasional direct access of the Azure file share in the cloud, then grouping several Azure file shares into the same storage account is fine. If you plan on lifting an app to Azure, that will then use the Azure file share natively, you might need more performance for this app than Azure File Sync needed from the file share. In these situations, it would be better to map an Azure file share to its own storage account.
+* An Azure file share is deployed inside of a storage account. That makes the storage account a scale target for performance numbers such as IOPS and throughput. Two standard (not premium) Azure file shares could theoretically saturate the maximum performance a storage account can deliver. If you plan to only attach Azure File Sync to these file shares, then grouping several Azure file shares into the same storage account is not creating a problem. Review the Azure file share performance targets for deeper insight into the relevant metrics to consider. If you plan on lifting an app to Azure that will use the Azure file share natively, then you might need more performance from your Azure file share. If this is a possibility, even in the future, then mapping an Azure file share to its own storage account is best.
 * There is a limit of 250 storage accounts per subscription in a single Azure region.
 
 > [!TIP]
@@ -48,7 +52,7 @@ Another important aspect of Azure File Sync and a balanced performance and exper
 > [!IMPORTANT]
 > The most important scale vector for Azure File Sync is the number of items (files and folders) that need to be synchronized.
 
-Azure File Sync supports syncing up to 100,000 items to a single Azure file share, which is not a hard limit, but depicts what the Azure File Sync team tests on a regular basis.
+Azure File Sync supports syncing up to 100,000 items to a single Azure file share. This limit can be exceeded and only depicts what the Azure File Sync team tests on a regular basis.
 
 It is a best practice to keep the number of items per sync scope low. That aspect is an important factor to be considered in your mapping of folders to Azure file shares.
 
@@ -65,7 +69,7 @@ Even if in your situation a set of folders can logically sync to the same Azure
 
         Create a table that records your thoughts, such that you can refer to it in the next step. Staying organized is important as it can be easy to lose details of your mapping plan when provisioning many Azure resources at once. To help you in creating a complete mapping, you can download a Microsoft Excel file as a template.
 
-[//]: # (After several attempts, there does not appear to be a markdown way capable of adding a nested two-column table with working image parsing and text/hyperlink on the same line. HTML seems like the only option.)
+[//]: # (HTML appears as the only way to accomplish adding a nested two-column table with working image parsing and text/hyperlink on the same line.)
 
 <br>
 <table>