alt-text updates

TylerMSFT · TylerMSFT · commit b4fb20d3d7ee · 2022-09-15T11:47:33.000-07:00
diff --git a/docs/get-started/includes/git-source-control.md b/docs/get-started/includes/git-source-control.md
@@ -20,7 +20,7 @@ To associate your code with Git, you start by creating a new Git repository wher
 
 1. In the **Create a Git repository** dialog box, sign in to GitHub.
 
-    :::image type="content" source="../media/vs-2022/git-create-repo.png" alt-text="Screenshot of the Create a Git Repository dialog window where you can sign in to GitHub.":::
+    :::image type="content" source="../media/vs-2022/git-create-repo.png" alt-text="Screenshot of the Create a Git Repository dialog window where you create a new GitHub repository.":::
 
     The repository name auto-populates based on your folder location. By default, your new repository is private, which means you're the only one who can access it.
 
@@ -29,9 +29,9 @@ To associate your code with Git, you start by creating a new Git repository wher
 
 1. Select **Create and Push**.
 
-    After you create your repository, you see status details in the status bar.
+    After you create your repository, status details appear in the status bar.
 
-    :::image type="content" source="../media/vs-2022/git-new-private-repo-status-details.png" alt-text="Screenshot of the repo status bar that's below the Solution Explorer pane in Visual Studio.":::
+    :::image type="content" source="../media/vs-2022/git-new-private-repo-status-details.png" alt-text="Screenshot of the repo status bar located below the Visual Studio Solution Explorer pane, showing the branch name and number of outstanding changes.":::
 
     The first icon with the arrows shows how many outgoing/incoming commits are in your current branch. You can use this icon to pull any incoming commits or push any outgoing commits. You can also choose to view these commits first. To do so, select the icon, and then select **View Outgoing/Incoming**.
 
diff --git a/docs/get-started/tutorial-console-cpp.md b/docs/get-started/tutorial-console-cpp.md
diff --git a/docs/linux/cmake-linux-configure.md b/docs/linux/cmake-linux-configure.md
@@ -108,7 +108,7 @@ When you do a build:
 
 ## Choose a Linux target
 
-When you open a CMake project folder, Visual Studio parses the *CMakeLists.txt* file and specifies a Windows target of **x86-Debug**. To target a remote Linux system, you'll change the project settings based on your Linux compiler. For example, if you're using GCC on Linux and compiling with debug info, choose:  **Linux-GCC-Debug** or **Linux-GCC-Release**.
+When you open a CMake project folder, Visual Studio parses the *CMakeLists.txt* file, and specifies a Windows target of **x86-Debug**. To target a remote Linux system, you'll change the project settings based on your Linux compiler. For example, if you're using GCC on Linux and compiling with debug info, choose:  **Linux-GCC-Debug** or **Linux-GCC-Release**.
 
 If you specify a remote Linux target, your source is copied to the remote system.
 
diff --git a/docs/linux/connect-to-your-remote-linux-computer.md b/docs/linux/connect-to-your-remote-linux-computer.md
@@ -64,11 +64,11 @@ 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++ > Connection Manager selected under options, and the Add button highlighted.](media/settings_connectionmanager.png)
+   ![Screenshot showing CrossPlatform > C plus plus > Connection Manager selected under options, and the Add button highlighted.](media/settings_connectionmanager.png)
 
    In either scenario, the **Connect to Remote System** window is displayed.
 
-   ![Screenshot showing the Connect to Remote System window which has fields for the host name, port, user name, auth type, and password.](media/connect.png)
+   ![Screenshot showing the Connect to Remote System window which has fields for host name, port, user name, authentication type, and password.](media/connect.png)
 
 1. Enter the following information:
 
@@ -90,7 +90,7 @@ If `ssh` isn't already set up and running on your Linux system, follow these ste
 
    If the connection fails, the entry boxes that need to be changed are outlined in red.
 
-   ![Screenshot showing a Connection Manager Error. The host name and port fields are outlined in red to indicate an error.](media/settings_connectionmanagererror.png)
+   ![Screenshot of the Connect to Remote System window with the host name and port fields outlined in red to indicate that they are incorrect.](media/settings_connectionmanagererror.png)
 
    If you use key files for authentication, make sure the target machine's SSH server is running and configured properly.
 
@@ -181,7 +181,7 @@ For example: `HostKeyAlgorithms ssh-dss,ssh-rsa`
 
    You can enable logging to help troubleshoot connection problems. On the menu bar, select **Tools > Options**. In the **Options** dialog, select **Cross Platform > Logging**:
 
-   ![Screenshot showing the Remote Logging screen with options to enable logging, log file location, and a checkbox indicating whether to log to the "Cross Platform Logging pane in the output window.](media/remote-logging-vs2019.png)
+   ![Screenshot of the Remote Logging screen with options to enable logging, log file location, and whether to log to the output window.](media/remote-logging-vs2019.png)
 
    Logs include connections, all commands sent to the remote machine (their text, exit code and execution time), and all output from Visual Studio to the shell. Logging works for any cross-platform CMake project or MSBuild-based Linux project in Visual Studio.
 
diff --git a/docs/linux/create-a-new-linux-project.md b/docs/linux/create-a-new-linux-project.md
@@ -2,7 +2,6 @@
 title: "Create a Linux MSBuild C++ project in Visual Studio"
 ms.date: "10/15/2020"
 description: "Create a new MSBuild-based Linux project in Visual Studio."
-ms.assetid: 5d7c1d67-bc31-4f96-8622-2b4cf91372fd
 ---
 # Create a Linux MSBuild C++ project in Visual Studio
 
@@ -25,7 +24,7 @@ To create a new Linux project in Visual Studio 2017, follow these steps:
 1. Select **File > New Project** in Visual Studio, or press **Ctrl + Shift + N**.
 1. Select the **Visual C++ > Cross Platform > Linux** node, and then select the project type to create. Enter a **Name** and **Location**, and choose **OK**.
 
-   ![Screenshot showing the New Project dialog box with Visual C plus plus > Cross Platform > Linux selected, all of the project types called out, and the Name and Location text boxes also called out.](media/newproject.png)
+![The New Project dialog box with Visual C plus plus > Cross Platform > Linux selected and all project types and Name and Location text boxes called out.](media/newproject.png)
 
    | Project Type | Description |
    | ------------ | --- |
@@ -52,7 +51,7 @@ To create a new Linux project in Visual Studio, follow these steps:
 1. In the **Search for templates** textbox, enter **Linux** to list the available templates for Linux projects.
 1. Select the project type to create, for example **Console Application**, and then choose **Next**. Enter a **Name** and **Location**, and choose **Create**.
 
-   ![Screenshot of the new project dialog box with the language drop-down set to C++ and the platform drop-down set to Linux.](media/newproject-vs2019.png)
+   ![Screenshot of the new project dialog box with the language drop-down set to C plus plus and the platform drop-down set to Linux.](media/newproject-vs2019.png)
 
    | Project Type | Description |
    | ------------ | --- |
diff --git a/docs/linux/deploy-run-and-debug-your-linux-project.md b/docs/linux/deploy-run-and-debug-your-linux-project.md
@@ -2,7 +2,6 @@
 title: "Deploy, run, and debug your Linux MSBuild C++ project in Visual Studio"
 description: "Describes how to compile, execute, and debug code on the remote target from inside a MSBuild-based Linux C++ project in Visual Studio."
 ms.date: "08/08/2020"
-ms.assetid: f7084cdb-17b1-4960-b522-f84981bea879
 ms.custom: intro-deployment
 ---
 # Deploy, run, and debug your Linux MSBuild project
@@ -56,11 +55,11 @@ There are several ways to interact with and debug your Linux project.
 
    When the remote target is available, you'll see it listed by either name or IP address.
 
-   ![Screenshot showing a Remote target.](media/remote_target.png)
+   ![Screenshot showing a Remote target IP address.](media/remote_target.png)
 
    If you haven't connected to the remote target yet, you'll see an instruction to use [Linux Connection Manager](connect-to-your-remote-linux-computer.md) to connect to the remote target.
 
-   ![Screenshot showing the Remote Architecture.](media/architecture.png)
+   ![Screenshot showing the Remote Architecture, which is x64.](media/architecture.png)
 
 1. Set a breakpoint by clicking in the left gutter of some code that you know will execute.
 
@@ -126,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.](media/linux-remote-debug-machine.png)
+![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)
 
 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 Linux deployable files specified in the Properties window.](media/linux-deployable-content.png)
+![Screenshot showing the properties of main.cpp with 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.
 
@@ -159,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.vs.json file.](media/cmake-remote-debug-machine.png)
+![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)
 
 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**.
 
diff --git a/docs/linux/download-install-and-setup-the-linux-development-workload.md b/docs/linux/download-install-and-setup-the-linux-development-workload.md
@@ -2,7 +2,6 @@
 title: "Install the C++ Linux workload in Visual Studio"
 description: "How to download, install, and set up the Linux workload for C++ in Visual Studio."
 ms.date: "05/03/2020"
-ms.assetid: e11b40b2-f3a4-4f06-b788-73334d58dfd9
 ms.custom: intro-installation
 ---
 # Download, install, and set up the Linux workload
@@ -29,11 +28,11 @@ 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.](media/visual-studio-installer-search.png)
+   ![Screenshot showing the Windows search box with the contents 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.
 
-   ![Screenshot showing the Visual C++ for Linux Development workload item in Visual Studio Installer.](media/linuxworkload.png)
+   ![Screenshot highlighting the Visual C++ for Linux Development workload item in Visual Studio Installer.](media/linuxworkload.png)
 
 1. If you're targeting IoT or embedded platforms, go to the **Installation details** pane on the right. Under **Linux development with C++**, expand **Optional Components**, and choose the components you need. CMake support for Linux is selected by default.
 
diff --git a/docs/linux/linux-asan-configuration.md b/docs/linux/linux-asan-configuration.md
@@ -20,7 +20,7 @@ ASan is a runtime memory error detector for C/C++ that catches the following err
 
 When ASan detects an error, it stops execution immediately. If you run an ASan-enabled program in the debugger, you see a message that describes the type of error, the memory address, and the location in the source file where the error occurred:
 
-   ![Screenshot showing an ASan error message.](media/asan-error.png)
+   ![Screenshot showing the address sanitizer error message: heap use after free.](media/asan-error.png)
 
 You can also view the full ASan output (including where the corrupted memory was allocated/deallocated) in the Debug pane of the output window.
 
@@ -31,26 +31,26 @@ 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.
 
-![Enable ASan for an MSBuild project.](media/msbuild-asan-prop-page.png)
+![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)
 
 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.
 
-![Configure ASan runtime flags.](media/msbuild-asan-runtime-flags.png)
+![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)
 
 ## Enable ASan for Visual Studio CMake projects
 
 > [!NOTE]
 > To build with CMake Presets, first enable ASan in your CMakeLists.txt file. For more information, see [Enable AddressSanitizer for Windows and Linux](../build/cmake-presets-vs.md#enable-addresssanitizer-for-windows-and-linux).
 
-To enable ASan for CMake, right-click on the CMakeLists.txt file in **Solution Explorer** and choose **CMake Settings for Project**.
+To enable ASan for CMake, right-click on the `CMakeLists.txt` file in **Solution Explorer** and choose **CMake Settings for Project**.
 
 Make sure you have a Linux configuration (for example, **Linux-Debug**) selected in the left pane of the dialog:
 
-![Screenshot of the left pane with Linux Debug listed as one of the Configuration options.](media/linux-debug-configuration.png)
+![Screenshot of the Configurations pane with Linux Debug listed as one of 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.
 
-![Screenshot of the Enable Address Sanitizer option showing some Address Sanitizer run time flags.](media/cmake-settings-asan-options.png)
+![Screenshot of the Enable Address Sanitizer option showing some Address Sanitizer run time flags like detect_leaks=0.](media/cmake-settings-asan-options.png)
 
 ## Install the ASan debug symbols
 
diff --git a/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md b/docs/linux/set-up-fips-compliant-secure-remote-linux-development.md
@@ -99,11 +99,11 @@ You've successfully set up `ssh`, created and deployed encryption keys, and test
 
 1. In the Connection Manager dialog, choose the **Add** button to add a new connection.
 
-   ![Screenshot showing the Connection Manager dialog.](media/settings_connectionmanager.png)
+   ![Screenshot showing the Connection Manager dialog under Cross Platform > C plus plus > Connection Manager.](media/settings_connectionmanager.png)
 
    The **Connect to Remote System** window is displayed.
 
-   ![Screenshot showing the Connect to Remote System window.](media/connect.png)
+   ![Screenshot showing the Connect to Remote System window, which has text boxes for host name, port, user name, auth type, and password.](media/connect.png)
 
 1. In the **Connect to Remote System** dialog, enter the connection details of your remote machine.
 
@@ -124,7 +124,7 @@ You've successfully set up `ssh`, created and deployed encryption keys, and test
 
    If the connection fails, the entry boxes that need to be changed are outlined in red.
 
-   ![Screenshot showing a Connection Manager Error.](media/settings_connectionmanagererror.png)
+   ![Screenshot of the Connect to Remote System window showing the host name and port text boxes outlined in red to indicate they need to be changed.](media/settings_connectionmanagererror.png)
 
    For more information on troubleshooting your connection, see [Connect to your remote Linux computer](connect-to-your-remote-linux-computer.md).
 
