Update articles/storage/file-sync/file-sync-choose-cloud-tiering-policies.md

Co-authored-by: Ken Downie <[email protected]>

Author: codefinite-vri

articles/storage/file-sync/file-sync-choose-cloud-tiering-policies.md

@@ -75,7 +75,7 @@ When adjusting your volume free space policy, the amount of data you should keep
 
 ## Impact of aggressive cloud tiering configurations
 
-When configuring Azure File Sync cloud tiering, evaluate the volume free space percentage and the date policy 'number of days' based on the usage of the Azure File Sync server. For example, if you expect the last 7 days of recent data to be cached on the server, you may set the date policy to 7 days and ensure that the total volume size and current free space on the volume allow for the last 7 days of churn (new content and recalls due to access to some already tiered content to get cached upon recall). Assuming the volume size is 100 GB and the last 7 days of churn is ~10 GB, your volume must allow the latest 10 GB to be cached and tier the remaining data to cloud. A volume free space of 20% would be fair in this case, as Azure File Sync will try to keep 20% (i.e., 20 GB free space), which allow for 10 GB of new content over 7 days and provides some extra room for file system overhead and occasional excess data to also be cached.
+When configuring Azure File Sync cloud tiering, evaluate the volume free space percentage and the date policy 'number of days' based on the usage of the Azure File Sync server. For example, if you expect the last 7 days of recent data to be cached on the server, you may set the date policy to 7 days and ensure that the total volume size and current free space on the volume allow for the last 7 days of churn (new content and recalls due to access to some already tiered content to get cached upon recall). Assuming the volume size is 100 GiB and the last 7 days of churn is ~10 GiB, your volume must allow the latest 10 GiB to be cached and tier the remaining data to cloud. A volume free space of 20% would be fair in this case, as Azure File Sync will try to keep 20% (i.e., 20 GiB free space), which allows for 10 GiB of new content over 7 days and provides some extra room for file system overhead and occasional excess data to also be cached.
 
 Setting a very high volume free space can significantly reduce the amount of data kept locally on the server. This would mean you expect almost all the files to be tiered. If the local cache contains only a small percentage of the working dataset, users may experience more frequent recalls from Azure. This can increase access latency and may result in additional transaction and data transfer costs for Azure Files.