Updated text to meet Acrolinx score

Author: ronmiab

azure-local/manage/get-support-for-deployment-issues.md

@@ -25,14 +25,14 @@ The following table outlines potential issues you might encounter during deploym
 
 ## Perform standalone log collection
 
-If observability components have not been deployed or if you encounter issues during the system deployment or registration process, you can perform standalone log collection to collect and send diagnostic data to Microsoft for troubleshooting purposes. Make sure to file a support ticket before you proceed with the log collection.
+If observability components aren't deployed or you run into issues during system deployment or registration, perform standalone log collection to collect and send diagnostic data to Microsoft for troubleshooting. Make sure to file a support ticket before you start log collection.
 
 Here are the high-level steps for standalone log collection:
 
-1. As instructed by Microsoft Support, copy the requested diagnostic data from the Azure Local machine to a system which has connectivity to Azure.
+1. As instructed by Microsoft Support, copy the requested diagnostic data from the Azure Local machine to a system, which has connectivity to Azure.
 1. Use `Send-AzStackHciDiagnosticData` to transmit the copied diagnostic data to Microsoft for troubleshooting purposes. Microsoft can access that data after you file a support ticket.
 
-If the observability feature is already configured, you can send diagnostic data to Microsoft using the on-demand log collection process. For instructions, see [Collect logs](./collect-logs.md). To explore additional log collection methods in Azure Local and understand when to use them, see [Diagnostics](../concepts/observability.md#diagnostics).
+If the observability feature is already set up, send diagnostic data to Microsoft using the on-demand log collection process. For instructions, see [Collect logs](./collect-logs.md). To learn about other log collection methods in Azure Local and when to use them, see [Diagnostics](../concepts/observability.md#diagnostics).
 
 ### Send logs to Microsoft
 
@@ -44,7 +44,7 @@ You can use any of the following credentials to send logs:
 
 #### Send logs using device code credentials
 
-When you run the following command, you'll be prompted to open a web browser and enter the provided code to proceed with the authentication process.
+When you run the following command, you're prompted to open a web browser and enter the provided code to continue the authentication process.
 
 ```powershell
 Send-AzStackHciDiagnosticData -ResourceGroupName <ResourceGroupName> -SubscriptionId <SubscriptionId> -TenantId <TenantId> - RegistrationWithDeviceCode -DiagnosticLogPath <LogPath> -RegistrationRegion <RegionName> -Cloud <AzureCloud>    
@@ -74,7 +74,7 @@ Send-AzStackHciDiagnosticData -ResourceGroupName <ResourceGroupName> -Subscripti
 
 ## Get remote support
 
-In the pre-deployment or pre-registration scenarios, you are prompted to install and enable remote support via the Environment Checker to evaluate the readiness for deployment. If you enable remote support, Microsoft Support can connect to your device remotely and offer assistance. If you want to get remote support post-deployment of the system, see [Get remote support for Azure Local](./get-remote-support.md).
+In the pre-deployment or pre-registration scenarios, you're prompted to install and enable remote support via the Environment Checker to evaluate the readiness for deployment. If you enable remote support, Microsoft Support can connect to your device remotely and offer assistance. If you want to get remote support post-deployment of the system, see [Get remote support for Azure Local](./get-remote-support.md).
 
 The high-level workflow to get remote support in the pre-deployment or pre-registration scenario is as follows:
 
@@ -83,26 +83,26 @@ The high-level workflow to get remote support in the pre-deployment or pre-regis
 
 ### Enable remote support
 
-Follow these steps to enable remote support:
+To enable remote support, follow these steps:
 
 1. Establish a remote PowerShell session with the machine. Run PowerShell as administrator and run the following command:
 
    ```powershell
    Enter-PsSession -ComputerName <MachineName> -Credential $cred
    ```
 
-1. Run the following command to enable remote support. The sample Shared Access Signature (SAS) is provided by the Microsoft support team.
+1. To enable remote support, run the following command. The sample Shared Access Signature (SAS) is provided by the Microsoft support team.
 
    ```powershell
    Enable-AzStackHciRemoteSupport -AccessLevel <Diagnostics Or DiagnosticsRepair> -ExpireInMinutes <1440> -SasCredential <Sample SAS> -PassThru
    ```
 
    > [!NOTE]
-   > When you run the command to enable remote support, you may get the following error:
+   > When you run the command to enable remote support, you can get the following error:
    >
    > `Processing data from remote server <MachineName> failed with the following error message: The I/O operation has been aborted because of either a thread exit or an application request.`
    >
-   > This means the Just Enough Administration (JEA) configuration has not been established. When you enable remote support, a service restart is required to activate JEA. During the remote support JEA configuration, the Windows Remote Management (WinRM) restarts twice, which may disrupt the PsSession to the machine. To resolve this error, wait for a few minutes before reconnecting to the remote machine and then run the `Enable-AzStackHciRemoteSupport` command again to enable remote support.
+   > This means the Just Enough Administration (JEA) configuration isn't established. When you enable remote support, a service restart is required to activate JEA. During the remote support JEA configuration, Windows Remote Management (WinRM) restarts twice, which can disrupt the PsSession to the machine. To fix this error, wait a few minutes before reconnecting to the remote machine, and then run the `Enable-AzStackHciRemoteSupport` command again to enable remote support.
    >
 
 For remote support usage scenarios, see [Enable remote support diagnostics](./get-remote-support.md#enable-remote-support-diagnostics) and [Other remote support operations](./get-remote-support.md#other-remote-support-operations).