Acrolinx edits

Author: Mikejo5000

docs/debugger/remote-debugging-cpp.md

@@ -18,7 +18,7 @@ ms.subservice: debug-diagnostics
 ---
 # Remote Debugging a C++ Project in Visual Studio
 
-To debug a Visual Studio application on a different computer, install and run the remote tools on the computer where you will deploy your app, configure your project to connect to the remote computer from Visual Studio, and then deploy and run your app.
+To debug a Visual Studio application on a different computer, install and run the remote tools on the computer where you'll deploy your app, configure your project to connect to the remote computer from Visual Studio, and then deploy and run your app.
 
 ![Remote debugger components](../debugger/media/remote-debugger-client-apps.png "Remote_debugger_components")
 
@@ -29,7 +29,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer and versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 
@@ -40,7 +40,7 @@ The remote debugger is supported on Windows 7 and newer and versions of Windows
 
 ## <a name="BKMK_setup"></a> Set up the remote debugger
 
-Once you have installed the remote debugger, follow these steps.
+After you install the remote debugger, follow these steps.
 
 [!INCLUDE [remote-debugger-configuration](../debugger/includes/remote-debugger-configuration.md)]
 
@@ -101,7 +101,7 @@ Once you have installed the remote debugger, follow these steps.
 
 ## Set Up Debugging with Remote Symbols
 
-You should be able to debug your code with the symbols you generate on the Visual Studio computer. The performance of the remote debugger is much better when you use local symbols.
+You should be able to debug your code with the symbols you generate on the Visual Studio computer. The performance of the remote debugger is significantly better when you use local symbols.
 
 If you must use remote symbols, you need to specify the remote symbols in Visual Studio by adding a Windows file share to the symbol search path in **Tools > Options > Debugging > Symbols**.
 

docs/debugger/remote-debugging-csharp.md

@@ -29,7 +29,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer and on versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 
@@ -40,7 +40,7 @@ The remote debugger is supported on Windows 7 and newer and on versions of Windo
 
 ## <a name="BKMK_setup"></a> Set up the remote debugger
 
-Once you have installed the remote debugger, follow these steps.
+After you install the remote debugger, follow these steps.
 
 [!INCLUDE [remote-debugger-configuration](../debugger/includes/remote-debugger-configuration.md)]
 
@@ -49,11 +49,11 @@ Once you have installed the remote debugger, follow these steps.
 
 ## <a name="remote_csharp"></a> Remote debug the project
 
-The debugger cannot deploy Visual C# or Visual Basic desktop applications to a remote machine, but you can still debug them remotely as follows. The following procedure assumes that you want to debug it on a computer named **MJO-DL**, as shown in the illustration below.
+The debugger can't deploy Visual C# or Visual Basic desktop applications to a remote machine, but you can still debug them remotely as follows. The following procedure assumes that you want to debug it on a computer named **MJO-DL**, as shown in the illustration below.
 
 1. Create a WPF project named **MyWpf**.
 
-   If you are trying to remote debug a MAUI app instead of WPF, see [Remote debug a .NET MAUI app on Windows](#remote-debug-a-net-maui-app-on-windows).
+   If you're trying to remote debug a MAUI app instead of WPF, see [Remote debug a .NET MAUI app on Windows](#remote-debug-a-net-maui-app-on-windows).
 
 2. Set a breakpoint somewhere in the code that is easily reached.
 
@@ -88,7 +88,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
     **MJO-DL:4024** on Visual Studio 2019
     ::: moniker-end
 
-7. Make sure that **Enable native code debugging** is not selected.
+7. Make sure that **Enable native code debugging** isn't selected.
 
 8. Build the project.
 
@@ -97,7 +97,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
 10. Copy the executable that you just built from your Visual Studio computer to the newly created folder on the remote computer.
 
     > [!CAUTION]
-    > Do not make changes to the code or rebuild (or you must repeat this step). The executable you copied to the remote machine must exactly match your local source and symbols.
+    > Don't make changes to the code or rebuild (or you must repeat this step). The executable you copied to the remote machine must exactly match your local source and symbols.
 
     You can copy the project manually, use XCopy, Robocopy, PowerShell, or other options.