Merge pull request #7982 from AmandaAZ/Branch-PostEdit

AB#3291, AB#3290: Post Edit two PRs

Author: khdownie

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-installation.md

@@ -164,11 +164,11 @@ You can also work around this issue by using the following PowerShell commands t
 Connect-AzAccount -Subscription "<guid>" -Tenant "<guid>"
 Register-AzStorageSyncServer -ResourceGroupName "<your-resource-group-name>" -StorageSyncServiceName "<your-storage-sync-service-name>"
 ```
-<a id="server-registration-missing-resource-groups"></a>**Server Registration doesn't list all Resource Groups**
+<a id="server-registration-missing-resource-groups"></a>**Server registration doesn't list all resource groups**
 
-When registering a server using ServerRegistration.exe, some resource groups are missing when you select the Resource Group drop-down.
+When registering a server using *ServerRegistration.exe*, some resource groups are missing when you select the **Resource Group** drop-down.
 
-This issue occurs due to a known bug that has been fixed in File Sync Agent v19.1. Install the latest version of the agent to resolve this.
+This issue occurs due to a known issue that has been fixed in File Sync Agent v19.1. To resolve this issue, install the latest version of the agent.
 
 <a id="server-already-registered"></a>**Server Registration displays the following message: "This server is already registered"**
 

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -177,7 +177,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0x80070459 | -2147023783 | ERROR_NO_UNICODE_TRANSLATION | The file or directory name has unsupported surrogate pair characters. | Rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |
 | 0x80c80255 | -2134375851 | ECS_E_XSMB_REST_INCOMPATIBILITY | The file or directory name is invalid. | Rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |
 | 0x80c80018 | -2134376424 | ECS_E_SYNC_FILE_IN_USE | The file can't be synced because it's in use. The file will be synced when it's no longer in use. | No action required. Azure File Sync creates a temporary VSS snapshot once a day on the server to sync files that have open handles. |
-| 0x80c86013 | -2134351853 | ECS_E_SYNC_CLOUD_FILE_IN_USE | The cloud file can't be synced because it's in use. This error occurs when an application holds an open handle to a file in the cloud, preventing sync operations from being performed until the application releases the handle. | Check the open file handles and close them if they are no longer needed. See [List Open File Handles](/rest/api/storageservices/list-handles) and [Force Close Open Handles](/rest/api/storageservices/force-close-handles). |
+| 0x80c86013 | -2134351853 | ECS_E_SYNC_CLOUD_FILE_IN_USE | The cloud file can't be synced because it's in use. This error occurs when an application holds an open handle to a file in the cloud, preventing sync operations from being performed until the application releases the handle. | Check the open file handles and close them if they're no longer needed. For more information, see [List Handles](/rest/api/storageservices/list-handles) and [Force Close Handles](/rest/api/storageservices/force-close-handles). |
 | 0x80c8031d | -2134375651 | ECS_E_CONCURRENCY_CHECK_FAILED | The file has changed, but the change hasn't yet been detected by sync. Sync will recover after this change is detected. | No action required. |
 | 0x80070002 | -2147024894 | ERROR_FILE_NOT_FOUND | The file was deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
 | 0x80070003 | -2147024893 | ERROR_PATH_NOT_FOUND | Deletion of a file or directory can't be synced because the item was already deleted in the destination and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection runs on the destination and sync detects the item was deleted. |
@@ -208,7 +208,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0x80041007 | -2147217401 | SYNC_E_ITEM_MUST_EXIST | An internal error occurred. | If the error persists for more than a day, create a support request. |
 | 0X80C80293 | -2134375789 | ECS_E_SYNC_INITIAL_SCAN_COMPLETED | The sync session failed because the initial enumeration was completed. The next session will cover the full namespace. | No action required. This error should automatically resolve. If the error persists for several days, create a support request. |
 | 0X80C80342 | -2134375614 | ECS_E_SYNC_CUSTOM_METADATA_VERSION_NOT_SUPPORTED | The sync database has custom metadata with a version higher than the supported version. | Please upgrade the File Sync agent to the latest version. If the error persists after upgrading the agent, create a support request. |
-| 0x80c8604b | -2134351797 | ECS_E_AZURE_FILE_SHARE_FILE_NOT_FOUND | The specified Azure file wasn't found in the file share. This might occur if the file has been deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
+| 0x80c8604b | -2134351797 | ECS_E_AZURE_FILE_SHARE_FILE_NOT_FOUND | The specified Azure file wasn't found in the file share. This issue might occur if the file has been deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
 | 0x80c80201 | -2134375935 | ECS_E_SYNC_UNPROCESSABLE_ITEM_REPARSEPOINT | The sync failed due to the presence of a reparse point. | Remove the reparse point or replace it with regular file content before attempting the sync again. |
 
 ### Handling unsupported characters
@@ -630,7 +630,7 @@ This error can occur if there is a file system corruption on the NTFS volume whe
 | **Error string** | ERROR_REPARSE_TAG_INVALID |
 | **Remediation required** | Yes |
 
-This error occurs when files are copied between servers with different configurations, such as transferring files from a server with a file system filter driver or deduplication feature enabled to one where these features aren't present, resulting in unreadable files due to invalid reparse points. To resolve this error, delete the affected files or re-copy them as actual files, not as reparse points.
+This error occurs when files are copied between servers with different configurations. For example, transferring files from a server with a file system filter driver or deduplication feature enabled to one where these features aren't present can result in unreadable files due to invalid reparse points. To resolve this error, delete the affected files or recopy them as actual files rather than reparse points.
 
 <a id="-2146762487"></a>**The server failed to establish a secure connection. The cloud service received an unexpected certificate.**