Fixes per @AnnaMHuff.

Author: wmgries

articles/storage/file-sync/file-sync-deployment-guide.md

@@ -21,10 +21,10 @@ We strongly recommend that you read [Planning for an Azure Files deployment](../
 
 # [Portal](#tab/azure-portal)
 
-1. An **Azure file share** in the same region that you want to deploy Azure File Sync. We recommended provisioned v2 file shares for all new deployments. For more information, see:
+1. An **Azure file share** in the same region that you want to deploy Azure File Sync. We recommend provisioned v2 file shares for all new deployments. For more information, see:
     - [Region availability](file-sync-planning.md#azure-file-sync-region-availability) for Azure File Sync.
     - [Create a file share](../files/storage-how-to-create-file-share.md?toc=/azure/storage/filesync/toc.json) for a step-by-step description of how to create a file share.
-    - [Understanding the provisioned v2 billing model](../files/understanding-billing.md#provisioned-v2-model) for information on the how to use the provisioned v2 model.
+    - [Understanding the provisioned v2 billing model](../files/understanding-billing.md#provisioned-v2-model) for information on how to use the provisioned v2 model.
 2. The following **storage account** settings must be enabled to allow Azure File Sync access to the storage account:  
     -  **SMB security settings** must allow **SMB 3.1.1** protocol version, **NTLM v2** authentication and **AES-128-GCM** encryption. To check the SMB security settings on the storage account, see [SMB security settings](../files/files-smb-protocol.md#smb-security-settings).
     -  **Allow storage account key access** must be **Enabled**. To check this setting, navigate to your storage account and select Configuration under the Settings section. 
@@ -51,9 +51,10 @@ We strongly recommend that you read [Planning for an Azure Files deployment](../
 
 # [PowerShell](#tab/azure-powershell)
 
-1. An **Azure file share** in the same region that you want to deploy Azure File Sync. For more information, see:
+1. An **Azure file share** in the same region that you want to deploy Azure File Sync. We recommend provisioned v2 file shares for all new deployments. For more information, see:
     - [Region availability](file-sync-planning.md#azure-file-sync-region-availability) for Azure File Sync.
     - [Create a file share](../files/storage-how-to-create-file-share.md?toc=/azure/storage/filesync/toc.json) for a step-by-step description of how to create a file share.
+    - [Understanding the provisioned v2 billing model](../files/understanding-billing.md#provisioned-v2-model) for information on how to use the provisioned v2 model.
 2. The following **storage account** settings must be enabled to allow Azure File Sync access to the storage account:  
     -  **SMB security settings** must allow **SMB 3.1.1** protocol version, **NTLM v2** authentication and **AES-128-GCM** encryption. To check the SMB security settings on the storage account, see [SMB security settings](../files/files-smb-protocol.md#smb-security-settings).
     -  **Allow storage account key access** must be **Enabled**. To check this setting, navigate to your storage account and select **Configuration** under the **Settings** section.
@@ -93,9 +94,10 @@ We strongly recommend that you read [Planning for an Azure Files deployment](../
 
 # [Azure CLI](#tab/azure-cli)
 
-1. An **Azure file share** in the same region that you want to deploy Azure File Sync. For more information, see:
+1. An **Azure file share** in the same region that you want to deploy Azure File Sync. We recommend provisioned v2 file shares for all new deployments. For more information, see:
     - [Region availability](file-sync-planning.md#azure-file-sync-region-availability) for Azure File Sync.
     - [Create a file share](../files/storage-how-to-create-file-share.md?toc=/azure/storage/filesync/toc.json) for a step-by-step description of how to create a file share.
+    - [Understanding the provisioned v2 billing model](../files/understanding-billing.md#provisioned-v2-model) for information on how to use the provisioned v2 model.
 2. The following **storage account** settings must be enabled to allow Azure File Sync access to the storage account:  
     -  **SMB security settings** must allow **SMB 3.1.1** protocol version, **NTLM v2** authentication and **AES-128-GCM** encryption. To check the SMB security settings on the storage account, see [SMB security settings](../files/files-smb-protocol.md#smb-security-settings).
     -  **Allow storage account key access** must be **Enabled**. To check this setting, navigate to your storage account and select Configuration under the Settings section.

includes/storage-file-sync-cost-categories.md

@@ -10,11 +10,11 @@
  ms.custom: include file
 ---
 
-- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure virtual machine, or even in another cloud. The costs for sync servers hosted on-premises or in other cloud providers including capital, such as the upfront hardware costs of your solution, and operating, such as the cost of labor, electricity, etc., costs aren't part of your Azure bill, but are still be part of the total cost of ownership of the solution. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads, and other organization-specific costs you might have. For more information, see [recommended system resources](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources).
+- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure virtual machine, or even in another cloud. The costs for sync servers hosted on-premises or in other cloud providers include both capital and operating costs that aren't tracked as part of your Azure bill, but are still part of the total cost of ownership of the solution. Captial expenses are the upfront hardware costs of your solution. Operating expenses are the ongoing costs of labor, electricity, etc. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads, and other organization-specific costs you might have. For more information, see [recommended system resources](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources).
 
 - **Per server licensing cost for servers registered with Azure File Sync.** To use Azure File Sync with a specific Windows File Server, you must first register it with Azure File Sync's Azure resource, the Storage Sync Service. Each server that you register after the first server has a flat monthly fee. Although this fee is small, it is one component of your bill to consider. To see the current price of the server registration fee for your desired region, see [the File Sync section on Azure Files pricing page](https://azure.microsoft.com/pricing/details/storage/files/).
 
-- **Azure Files costs.** Azure File Sync consumes resources from your Azure file share. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using HDD provisioned v2 file shares with Azure File Sync, although Azure File Sync on all Azure Files billing models (SSD provisioned v2, SSD provisioned v1, or HDD pay-as-you-go).
+- **Azure Files costs.** Azure File Sync consumes resources from your Azure file share. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using HDD provisioned v2 file shares with Azure File Sync, although Azure File Sync is fully supported on all Azure Files billing models (SSD provisioned v2, SSD provisioned v1, or HDD pay-as-you-go).
     - **Storage utilization.** Azure File Sync replicates any changes you make to your server endpoint to your Azure file share causing storage to be consumed. On provisioned file shares, changes consume provisioned space, so it is your responsibility to periodically increase provisioning as needed to account for file share growth. On pay-as-you-go file shares, adding or increasing the size of existing files on server endpoints causes the used storage costs to grow because the changes are replicated. 
 
     - **Snapshot utilization.** Azure File Sync takes share and file-level snapshots as part of regular usage. Although snapshot utilization is always differential, this can contribute in a noticeable way to the total Azure Files bill.