Merge pull request #185317 from mtalasila/master

Update file-sync-planning.md

Author: PRMerger12

articles/storage/file-sync/file-sync-planning.md

@@ -197,7 +197,7 @@ We'll use an example to illustrate how to estimate the amount of free space woul
 1. NTFS allocates a cluster size for each of the tiered files. 1 million files * 4 KiB cluster size = 4,000,000 KiB (4 GiB)
 > [!Note]  
 > The space occupied by tiered files is allocated by NTFS. Therefore, it will not show up in any UI.
-3. Sync metadata occupies a cluster size per item. (1 million files + 100,000 directories) * 4 KiB cluster size = 4,400,000 KiB (4.4 GiB)
+3. Sync metadata occupies a cluster size per item. (1 million files + 100,000 directories) * 4 KB cluster size = 4,400,000 KiB (4.4 GiB)
 4. Azure File Sync heatstore occupies 1.1 KiB per file. 1 million files * 1.1 KiB = 1,100,000 KiB (1.1 GiB)
 5. Volume free space policy is 20%. 1000 GiB * 0.2 = 200 GiB
 
@@ -403,4 +403,4 @@ These increases in both the number of recalls and the amount of data being recal
 * [Consider firewall and proxy settings](file-sync-firewall-and-proxy.md)
 * [Deploy Azure Files](../files/storage-how-to-create-file-share.md?toc=%2fazure%2fstorage%2ffilesync%2ftoc.json)
 * [Deploy Azure File Sync](file-sync-deployment-guide.md)
-* [Monitor Azure File Sync](file-sync-monitoring.md)
+* [Monitor Azure File Sync](file-sync-monitoring.md)