Merge pull request #284029 from khdownie/kendownie080824

screenshot security cleanup

Author: Jill Grant

articles/storage/file-sync/file-sync-resource-move.md

@@ -4,7 +4,7 @@ description: Learn how to move sync resources across resource groups, subscripti
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: how-to
-ms.date: 09/21/2023
+ms.date: 08/08/2024
 ms.author: kendownie
 ---
 
@@ -29,7 +29,7 @@ In Azure File Sync, the only resource capable of moving is the Storage Sync Serv
 * :::image type="icon" source="media/storage-sync-resource-move/storage-sync-resource-move-storage-account.png" border="false"::: Storage account
     * :::image type="icon" source="media/storage-sync-resource-move/storage-sync-resource-move-file-share.png" border="false"::: File share
 
-In Azure Storage, the only resource capable of moving is the storage account. An Azure file share, as a subresource, can't move to a different storage account.
+The only resource capable of moving is the storage account. An Azure file share, as a subresource, can't move to a different storage account.
 
 ## Supported combinations
 
@@ -41,7 +41,7 @@ As a best practice, the Storage Sync Service and the storage accounts that have
 * Storage Sync Service and storage accounts are located in **different subscriptions** (same Azure tenant)
 
 > [!IMPORTANT]
-> Through different combinations of moves, a Storage Sync Service and storage accounts can end up in different subscriptions, governed by different Microsoft Entra tenants. Sync would even appear to be working, but this is not a supported configuration. Sync can stop in the future with no ability to get back into a working condition.
+> Through different combinations of moves, a Storage Sync Service and storage accounts can end up in different subscriptions, governed by different Microsoft Entra tenants. Sync would even appear to be working, but this isn't a supported configuration. Sync can stop in the future with no ability to get back into a working condition.
 
 When planning your resource move, there are different considerations for [moving within the same Microsoft Entra tenant](#move-within-the-same-azure-active-directory-tenant) and moving across [to a different Microsoft Entra tenant](#move-to-a-new-azure-active-directory-tenant). When moving Microsoft Entra tenants, always move sync and storage resources together.
 

articles/storage/file-sync/media/storage-sync-resource-move/storage-sync-resource-move-aad-tenant-expanded.png

@@ -100,7 +100,6 @@ Now that you've created the VM, connect to it so you can mount your file share.
 
    :::image type="content" source="media/storage-files-quick-create-use-windows/local-host2.png" alt-text="Screenshot of the VM log in prompt, more choices is highlighted.":::
 
-
 1. You might receive a certificate warning during the sign-in process. Select **Yes** or **Continue** to create the connection.
 
 ### Map the Azure file share to a Windows drive
@@ -121,7 +120,6 @@ Now that you've mapped the drive, create a snapshot.
 
    :::image type="content" source="media/storage-files-quick-create-use-windows/create-snapshot.png" alt-text="Screenshot of the storage account snapshots tab.":::
 
-
 1. In the VM, open the *qstestfile.txt* and type "this file has been modified". Save and close the file.
 1. Create another snapshot.