cleanup pass

Author: TylerMSFT

docs/get-started/tutorial-console-cpp.md

@@ -141,9 +141,9 @@ It's time to add some math logic.
 
    ![Screenshot of the Visual Studio 2019 Solution Explorer window displaying the Calculator Tutorial project.](./media/calc-vs2019-solution-explorer.png "Solution Explorer")
 
-   You should now have three tabs open in the editor: *`CalculatorTutorial.cpp`*, *Calculator.h*, and *`Calculator.cpp`*. If you accidentally close one of them, you can reopen it by double-clicking it in the **Solution Explorer** window.
+   You should now have three tabs open in the editor: *`CalculatorTutorial.cpp`*, *`Calculator.h`*, and *`Calculator.cpp`*. If you accidentally close one of them, you can reopen it by double-clicking it in the **Solution Explorer** window.
 
-1. In **Calculator.h**, remove the `Calculator();` and `~Calculator();` lines that were generated, since you won't need them here. Next, add the following line of code so the file now looks like this:
+1. In **`Calculator.h`**, remove the `Calculator();` and `~Calculator();` lines that were generated, since you won't need them here. Next, add the following line of code so the file now looks like this:
 
     ```cpp
     #pragma once
@@ -167,7 +167,7 @@ It's time to add some math logic.
 
    A pop-up appears that gives you a peek of the code change that was made in the other file. The code was added to *`Calculator.cpp`*.
 
-   ![Pop-up with definition of Calculate.](./media/calc-vs2019-pop-up-definition.png "Screenshot of a pop-up displaying the definition of Calculate.")
+   !["Screenshot of a pop-up displaying the definition of Calculate."](./media/calc-vs2019-pop-up-definition.png)
 
    Currently, it just returns 0.0. Let's change that. Press **Esc** to close the pop-up.
 
@@ -267,7 +267,7 @@ Since the user is free to type anything into the console window, let's make sure
 
 1. Set a breakpoint on the `result = c.Calculate(x, oper, y);` line, just after the user was asked for input. To set the breakpoint, click next to the line in the gray vertical bar along the left edge of the editor window. A red dot appears.
 
-   ![Screenshot of Visual Studio with a red dot on a line of code, representing a breakpoint.](./media/calc-vs2019-set-breakpoint.png "Set a breakpoint")
+   ![Screenshot of Visual Studio with a red dot to the left of a line of code, representing a breakpoint.](./media/calc-vs2019-set-breakpoint.png "Set a breakpoint")
 
    Now when we debug the program, it always pauses execution at that line. We already have a rough idea that the program works for simple cases. Since we don't want to pause execution every time, let's make the breakpoint conditional.
 
@@ -289,7 +289,7 @@ Whenever you debug your code, you may notice that some new windows appear. These
 
 You can also just hover over variables in the code itself to see their current values where the execution is currently paused. Make sure the editor window is in focus by clicking on it first.
 
-   ![Screenshot of Visual Studio showing a tooltip displaying the value of the variable oper, which is the character /.](./media/calc-vs2019-hover-tooltip.png "Hover to view current variable values")
+   ![Screenshot of a tooltip displaying the value of the variable oper, which is the character `/`.](./media/calc-vs2019-hover-tooltip.png "Hover to view current variable values")
 
 ### To continue debugging
 
@@ -438,7 +438,7 @@ The template for a new windows console application creates a simple C++ "Hello W
 
 1. To run the code, on the menu bar, choose **Debug**, **Start without debugging**.
 
-   ![Screenshot of the Visual StudioDebug Console showing the output: Hello World!.](./media/calculator-hello-world-console.png "Start the project")
+   ![Screenshot of the Visual Studio Debug Console showing the output: Hello World!.](./media/calculator-hello-world-console.png "Start the project")
 
    A console window opens and then runs your app. When you start a console app in Visual Studio, it runs your code, then prints "Press any key to continue . . ." to give you a chance to see the output. Congratulations! You've created your first "Hello, world!" console app in Visual Studio!
 
@@ -494,7 +494,7 @@ Now let's turn the code in this template into a calculator app.
 1. To run the application, press **Ctrl+F5** or go to the **Debug** menu and choose **Start Without Debugging**. If you get a pop-up that says **This project is out of date**, you may select **Do not show this dialog again**, and then choose **Yes** to build your application. You should see a console window appear that displays the text specified in the code.
 
    :::image type="complex" source="./media/calculator-first-launch.gif" alt-text="Short video of running the calculator app.":::
-   Short video showing Debug > Start without debugging. A dialog asks whether to build because the project is out of date. The checkbox for Do not show this dialog again is selected. Yes is selected to build the project, the calculator project builds, and then launches in a Windows console window.
+   Short video showing Debug > Start without debugging. A dialog is visible that asks whether to build because the project is out of date. The checkbox for 'Do not show this dialog again' is selected. 'Yes' is selected to build the project, the calculator project builds, and then launches in a Windows console window.
    :::image-end:::
 
 1. Close the console window when you're done.
@@ -513,9 +513,9 @@ It's time to add some math logic.
 
    ![Screenshot of the Solution Explorer window displaying the Calculator Tutorial project.](./media/calculator-solution-explorer.png "Solution Explorer")
 
-   You should now have three tabs open in the editor: *`CalculatorTutorial.cpp`*, *Calculator.h*, and *`Calculator.cpp`*. If you accidentally close one of them, you can reopen it by double-clicking it in the **Solution Explorer** window.
+   You should now have three tabs open in the editor: *`CalculatorTutorial.cpp`*, *`Calculator.h`*, and *`Calculator.cpp`*. If you accidentally close one of them, you can reopen it by double-clicking it in the **Solution Explorer** window.
 
-1. In **Calculator.h**, remove the `Calculator();` and `~Calculator();` lines that were generated, since you won't need them here. Next, add the following line of code so the file now looks like this:
+1. In **`Calculator.h`**, remove the `Calculator();` and `~Calculator();` lines that were generated, since you won't need them here. Next, add the following line of code so the file now looks like this:
 
     ```cpp
     #pragma once
@@ -637,21 +637,21 @@ Since the user is free to type anything into the console window, let's make sure
 
 1. Set a breakpoint on the `result = c.Calculate(x, oper, y);` line, just after the user was asked for input. To set the breakpoint, click next to the line in the gray vertical bar along the left edge of the editor window. A red dot appears.
 
-   ![Short video of Visual Studio showing the user creating the red dot in the left of a line of code that represents a breakpoint.](./media/calculator-set-breakpoint.gif "Set a breakpoint")
+   ![Short video of Visual Studio showing the user setting a breakpoint which creates a red dot to the left of the line of code.](./media/calculator-set-breakpoint.gif "Set a breakpoint")
 
    Now when we debug the program, it always pauses execution at that line. We already have a rough idea that the program works for simple cases. Since we don't want to pause execution every time, let's make the breakpoint conditional.
 
 1. Right-click the red dot that represents the breakpoint, and choose **Conditions**. In the edit box for the condition, enter `(y == 0) && (oper == '/')`. Choose the **Close** button when you're done. The condition is saved automatically.
 
    :::image type="complex" source="./media/calculator-conditional-breakpoint.gif" alt-text="Set a conditional breakpoint":::
-    Short video showing a right-click on the breakpoint on the line of code that reads result = c dot Calculate ( x, oper, y). Conditions... is selected in the dropdown which opens the breakpoint settings window. In the text box following the Conditional Expression and Is true dropdowns, the user enters y==0 && oper == '/', and then selects close to set the conditional breakpoint.
+    Short video showing a right-click on the breakpoint. The breakpoint is on the line of code that reads result = c dot Calculate ( x, oper, y). 'Conditions...' is selected in the dropdown which opens the breakpoint settings window. In the text box following the Conditional Expression and Is true dropdowns, the user enters y == 0 && oper == '/', and then selects close to set the conditional breakpoint.
     :::image-end:::
 
    Now we pause execution at the breakpoint specifically if a division by 0 is attempted.
 
 1. To debug the program, press **F5**, or choose the **Local Windows Debugger** toolbar button that has the green arrow icon. In your console app, if you enter something like "5 - 0", the program behaves normally and keeps running. However, if you type "10 / 0", it pauses at the breakpoint. You can even put any number of spaces between the operator and numbers; `cin` is smart enough to parse the input appropriately.
 
-   ![Short video showing that the program paused at the conditional breakpoint.](./media/calculator-debug-conditional.gif "Pause at the conditional breakpoint")
+   ![Short video showing the program paused at the conditional breakpoint.](./media/calculator-debug-conditional.gif "Pause at the conditional breakpoint")
 
 ### Useful windows in the debugger
 
@@ -661,11 +661,11 @@ Whenever you debug your code, you may notice that some new windows appear. These
 
 To see all of the variables from that function, switch to the **Locals** window. You can actually modify the values of these variables while debugging, to see what effect they would have on the program. In this case, we'll leave them alone.
 
-   ![Screenshot of the Locals window showing the values of the local variables.](./media/calculator-locals.png "The Locals window")
+   ![Screenshot of the Locals window showing the values of the function's local variables.](./media/calculator-locals.png "The Locals window")
 
 You can also just hover over variables in the code itself to see their current values where the execution is currently paused. Make sure the editor window is in focus by clicking on it first.
 
-   ![Short video showing the tooltip that appears when you hover over a variable and displays the variables' value.](./media/calculator-hover-tooltip.gif "Hover to view current variable values")
+   ![Short video showing the tooltip that appears when you hover over a variable. The tooltip displays the variable's value.](./media/calculator-hover-tooltip.gif "Hover to view current variable values")
 
 ### To continue debugging
 

docs/linux/cmake-linux-configure.md

@@ -129,7 +129,7 @@ To target WSL, select **Manage Configurations** in the configuration dropdown in
 
 The **CMakeSettings.json** window appears.
 
-![CMake settings dialog with the plus button highlighted which adds the selected configuration: Linux-GCC-debug.](media/cmake-linux-configurations.png )
+![CMake settings dialog with the plus button highlighted which adds the selected configuration, which is Linux-GCC-debug.](media/cmake-linux-configurations.png )
 
 Press **Add Configuration** (the green '+' button) and then choose **Linux-GCC-Debug** or **Linux-GCC-Release** if using GCC. Use the Clang variants if you're using the Clang/LLVM toolset.  Press **Select** and then **Ctrl+S** to save the configuration.
 

docs/linux/connect-to-your-remote-linux-computer.md

@@ -64,7 +64,7 @@ If `ssh` isn't already set up and running on your Linux system, follow these ste
 
 1. In the Connection Manager dialog, choose the **Add** button to add a new connection.
 
-   ![Screenshot showing CrossPlatform > C plus plus > Connection Manager selected under options, and the Add button highlighted.](media/settings_connectionmanager.png)
+   ![Screenshot showing the options pane and CrossPlatform > C plus plus > Connection Manager selected. The Add button is highlighted.](media/settings_connectionmanager.png)
 
    In either scenario, the **Connect to Remote System** window is displayed.
 
@@ -203,7 +203,7 @@ The `rsync` command is used by both MSBuild-based Linux projects and CMake proje
 
 `rsync` is also used by Visual Studio's CMake support to copy source files to the remote system. If you can't enable TCP port forwarding, you can use `sftp` as your remote copy sources method. `sftp` is often slower than `rsync`, but doesn't have a dependency on TCP port forwarding. You can manage your remote copy sources method with the `remoteCopySourcesMethod` property in the [CMake Settings Editor](../build/cmakesettings-reference.md#settings-for-cmake-linux). If TCP port forwarding is disabled on your remote system, you'll see an error in the CMake output window the first time it invokes `rsync`.
 
-![Screenshot of the output window showing an Rsync Error that the SSH channel couldn't be opened.](media/port-forwarding-copy-error.png)
+![Screenshot of the output window which shows an Rsync Error that the SSH channel couldn't be opened.](media/port-forwarding-copy-error.png)
 
 `gdbserver` can be used for debugging on embedded devices. If you can't enable TCP port forwarding, then you must use `gdb` for all remote debugging scenarios. `gdb` is used by default when debugging projects on a remote system.
 

docs/linux/deploy-run-and-debug-your-linux-project.md

@@ -104,7 +104,7 @@ The [Debugging](prop-pages/debugging-linux.md) property page for Visual Studio p
 <?xml version="1.0" encoding="utf-8"?>
 <SupplementalLaunchOptions>
     <AttachOptions>
-      <AttachOptionsForConnection lSOLibSearchPath="/home/user/solibs">
+      <AttachOptionsForConnection AdditionalSOLibSearchPath="/home/user/solibs">
         <ServerOptions MIDebuggerPath="C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise\Common7\IDE\VC\Linux\bin\gdb\7.9\x86_64-linux-gnu-gdb.exe"
 ExePath="C:\temp\ConsoleApplication17\ConsoleApplication17\bin\x64\Debug\ConsoleApplication17.out"/>
         <SetupCommands>
@@ -125,13 +125,13 @@ You can separate your remote build machine from your remote debug machine for bo
 
 By default, the remote debug machine is the same as the remote build machine (**Configuration Properties** > **General** > **Remote Build Machine**). To specify a new remote debug machine, right-click on the project in **Solution Explorer** and go to **Configuration Properties** > **Debugging** > **Remote Debug Machine**.  
 
-![Screenshot showing the Linux remote debug machine property in the Property Pages dialog which displays the username, authentication type, and port.](media/linux-remote-debug-machine.png)
+![Screenshot showing the Linux remote debug machine property in the Property Pages dialog which shows the username, authentication type, and port.](media/linux-remote-debug-machine.png)
 
 The drop-down menu for **Remote Debug Machine** is populated with all established remote connections. To add a new remote connection, navigate to **Tools** > **Options** > **Cross Platform** > **Connection Manager** or search for "Connection Manager" in **Quick Launch**. You can also specify a new remote deploy directory in the project's Property Pages (**Configuration Properties** > **General** > **Remote Deploy Directory**).
 
 By default, only the files necessary for the process to debug will be deployed to the remote debug machine. You can use **Solution Explorer** to configure which source files will be deployed to the remote debug machine. When you click on a source file, you'll see a preview of its File Properties directly below the Solution Explorer.
 
-![Screenshot showing the properties of main.cpp with content = False highlighted.](media/linux-deployable-content.png)
+![Screenshot showing the properties of the file main.cpp with the property content = False highlighted.](media/linux-deployable-content.png)
 
 The **Content** property specifies whether the file will be deployed to the remote debug machine. You can disable deployment entirely by navigating to **Property Pages** > **Configuration Manager** and unchecking **Deploy** for the desired configuration.
 
@@ -158,7 +158,7 @@ In some cases, you may require more control over your project's deployment. For
 
 For CMake projects that target a remote Linux machine, you can specify a new remote debug machine in launch.vs.json. By default, the value of "remoteMachineName" is synchronized with the "remoteMachineName" property in CMakeSettings.json, which corresponds to your remote build machine. These properties no longer need to match, and the value of "remoteMachineName" in launch.vs.json will dictate which remote machine is used for deploy and debug.
 
-![The CMake remote debug machine specified in the launch_schema.json file. remote Machine Name is specified as ${debugInfo . remoteMachineName}](media/cmake-remote-debug-machine.png)
+![The CMake remote debug machine specified in the launch_schema.json file. The remote Machine Name is ${debugInfo . remoteMachineName}](media/cmake-remote-debug-machine.png)
 
 IntelliSense will suggest all a list of all established remote connections. You can add a new remote connection by navigating to **Tools** > **Options** > **Cross Platform** > **Connection Manager** or searching for "Connection Manager" in **Quick Launch**.
 

docs/linux/download-install-and-setup-the-linux-development-workload.md

@@ -28,7 +28,7 @@ For any of these scenarios, the **Linux development with C++** workload is requi
 
 1. Type "Visual Studio Installer" in the Windows search box:
 
-   ![Screenshot showing the Windows search box with the contents visual studio installer.](media/visual-studio-installer-search.png)
+   ![Screenshot of the Windows search box which contains the text: `visual studio installer`.](media/visual-studio-installer-search.png)
 
 1. Look for the installer under the **Apps** results and double-click it. When the installer opens, choose **Modify**, and then click on the **Workloads** tab. Scroll down to **Other toolsets** and select the **Linux development with C++** workload.
 

docs/linux/linux-asan-configuration.md

@@ -31,11 +31,11 @@ You can also view the full ASan output (including where the corrupted memory was
 
 To enable ASan for MSBuild-based Linux projects, right-click on the project in **Solution Explorer** and select **Properties**. Next, navigate to **Configuration Properties** > **C/C++** > **Sanitizers**. ASan is enabled via compiler and linker flags, and requires your project to be recompiled to work.
 
-![Screenshot of the project property page with Configuration Properties > C/C plus plus > Sanitizers Enable Address Sanitizer drop down set to Yes.](media/msbuild-asan-prop-page.png)
+![Screenshot of the project property page with Configuration Properties > C/C plus plus > Sanitizers selected. Enable Address Sanitizer is set to Yes.](media/msbuild-asan-prop-page.png)
 
 You can pass optional ASan runtime flags by navigating to **Configuration Properties** > **Debugging** > **AddressSanitizer Runtime Flags**. Click the down-arrow to add or remove flags.
 
-![Screenshot of the project property page with Configuration Properties > Debugging > Address Sanitizer Runtime Flags set to detect_leaks = 0.](media/msbuild-asan-runtime-flags.png)
+![Screenshot of the project property page with Configuration Properties > Debugging selected. Address Sanitizer Runtime Flags is `detect_leaks = 0`.](media/msbuild-asan-runtime-flags.png)
 
 ## Enable ASan for Visual Studio CMake projects
 
@@ -46,7 +46,7 @@ To enable ASan for CMake, right-click on the `CMakeLists.txt` file in **Solution
 
 Make sure you have a Linux configuration (for example, **Linux-Debug**) selected in the left pane of the dialog:
 
-![Screenshot of the Configurations pane with Linux Debug listed as one of the options.](media/linux-debug-configuration.png)
+![Screenshot of the Configurations pane with x64-Debug and Linux Debug listed as the options.](media/linux-debug-configuration.png)
 
 The ASan options are under **General**. Enter the ASan runtime flags in the format "flag=value", separated by spaces. The UI incorrectly suggests using semi-colons. Use spaces or colons to separate flags.