1) TOC changes - we need to structure the TOX with sub-folders such that customers are guided to the overview and the sub-structures are helping customers find the right doc. One more folder (cloud-only) is coming with the first migration guide on that side. 2) The TOC had a wrong entry for an Azure File Sync article. - took the opportunity to improve SEO for the article as well as aligned the TOC to the title.

Author: fauhse

articles/storage/files/TOC.yml

@@ -124,14 +124,20 @@
       href: storage-sync-files-monitoring.md
   - name: Migrate
     items:
-    - name: Migrate to Azure File Sync
-      href: storage-sync-offline-data-transfer.md
-    - name: Migrate from an on-premises NAS to a hybrid file server with Azure File Sync
-      href: storage-files-migration-nas-hybrid.md
-    - name: StorSimple 8100 and 8600 migration guide
-      href: storage-files-migration-storsimple-8000.md
-    - name: StorSimple 1200 migration guide
-      href: storage-files-migration-storsimple-1200.md
+    - name: Migrate to Azure file shares
+      href: storage-files-migration-overview.md
+    - name: Target a hybrid deployment
+      items:
+      - name: Migrate bulk data to Azure File Sync with Azure DataBox
+        href: storage-sync-offline-data-transfer.md
+      - name: Migrate from an on-premises NAS to a hybrid file server with Azure File Sync
+        href: storage-files-migration-nas-hybrid.md
+    - name: From StorSimple
+      items:
+      - name: StorSimple 8100 and 8600 migration guide
+        href: storage-files-migration-storsimple-8000.md
+      - name: StorSimple 1200 migration guide
+        href: storage-files-migration-storsimple-1200.md
   - name: Develop
     items:
     - name: Configure connection strings

articles/storage/files/storage-files-migration-overview.md

@@ -34,7 +34,7 @@ The key in any migration is to capture all the applicable file fidelity when mig
 
 File fidelity, in a migration, can therefore be defined as the ability to store all applicable file information on the source, the ability to transfer them with the migration tool and the ability to store them on the target storage of the migration.
 
-In order to ensure your migration proceeds as smoothly as possible, identify [the best copy tool for your needs](#migration-toolbox) and match a storage target to your source.
+To ensure your migration proceeds as smoothly as possible, identify [the best copy tool for your needs](#migration-toolbox) and match a storage target to your source.
 
 Taking the previous information into account, it becomes clear what the target storage for general purpose files in Azure is: [Azure file shares](storage-files-introduction.md). Compared to object storage in Azure blobs, file metadata can be natively stored on files in an Azure file share.
 
@@ -80,7 +80,7 @@ There are several Microsoft and non-Microsoft file copy tools available. In orde
     * Does it support your network path and/or available protocols (for instance REST/SMB/NFS) to and from the source and target storage locations?
 * Does the copy tool preserve the necessary file fidelity that is supported by the source/target location? In some cases, your target storage does not support the same fidelity as your source. You have already made the decision that the target storage is sufficient for your needs, hence the copy tool only needs to match the targets file fidelity capabilities.
 * Does the copy tool have features that make it fit into my migration strategy? 
-    * For example, consider if it has options that allow you to minimize your downtime. A good question to ask is: Can I run this copy multiple times on the same, by users actively accessed location? If so, you can reduce the amount of downtime significantly. Compare that to a situation where you can only start the copy when the source stops changing, in order to guarantee a complete copy.
+    * For example, consider if it has options that allow you to minimize your downtime. A good question to ask is: Can I run this copy multiple times on the same, by users actively accessed location? If so, you can reduce the amount of downtime significantly. Compare that to a situation where you can only start the copy when the source stops changing, to guarantee a complete copy.
 
 The following table classifies Microsoft tools and their current suitability for Azure file shares:
 

articles/storage/files/storage-sync-offline-data-transfer.md

@@ -9,7 +9,7 @@ ms.author: rogarana
 ms.subservice: files
 ---
 
-# Migrate bulk data to Azure File Sync
+# Migrate bulk data to Azure File Sync with Azure DataBox
 You can migrate bulk data to Azure File Sync in two ways:
 
 * **Upload your files by using Azure File Sync.** This is the simplest method. Move your files locally to Windows Server 2012 R2 or later, and install the Azure File Sync agent. After you set up the sync, your files will be uploaded from the server. (Our customers currently experience an average upload speed of 1 TiB about every two days.) To ensure that your server doesn't use too much of the bandwidth for your datacenter, you might want to set up a [bandwidth throttling schedule](storage-sync-files-server-registration.md#ensuring-azure-file-sync-is-a-good-neighbor-in-your-datacenter).