Merging changes synced from https://github.com/MicrosoftDocs/cpp-docs-pr (branch live)

Author: opbld16

docs/atl/atl-collection-classes.md

@@ -97,7 +97,7 @@ For a list of the CTraits classes, see [Collection Classes](../atl/collection-cl
 
 The following diagram shows the class hierarchy for the CTraits classes.
 
-![Traits hierarchy for collection classes](../atl/media/vctraitscollectionclasseshierarchy.gif "Traits hierarchy for collection classes")
+![Diagram that shows the traits hierarchy for collection classes.](../atl/media/vctraitscollectionclasseshierarchy.gif "Traits hierarchy for collection classes")
 
 ## Collection Classes Samples
 

docs/atl/atl-connection-points.md

@@ -9,7 +9,7 @@ ms.assetid: 17d76165-5f83-4f95-b36d-483821c247a1
 
 A connectable object is one that supports outgoing interfaces. An outgoing interface allows the object to communicate with a client. For each outgoing interface, the connectable object exposes a connection point. Each outgoing interface is implemented by a client on an object called a sink.
 
-![Connection points](../atl/media/vc2zw31.gif "Connection points")
+![Diagram that shows the connection points on a client object and a connectable object.](../atl/media/vc2zw31.gif "Connection points")
 
 Each connection point supports the [IConnectionPoint](/windows/win32/api/ocidl/nn-ocidl-iconnectionpoint) interface. The connectable object exposes its connection points to the client through the [IConnectionPointContainer](/windows/win32/api/ocidl/nn-ocidl-iconnectionpointcontainer) interface.
 

docs/atl/example-implementing-a-property-page.md

@@ -60,7 +60,7 @@ Click **OK** to have the wizard generate your property page.
 
 Now that your property page has been generated, you'll need to add a few controls to the dialog resource representing your page. Add an edit box, a static text control, and a check box and set their IDs as shown below:
 
-![Editing a dialog resource](../atl/media/ppgresourcelabeled.gif "Editing a dialog resource")
+![Screenshot of a dialog resource in the visual editor.](../atl/media/ppgresourcelabeled.gif "Editing a dialog resource")
 
 These controls will be used to display the file name of the document and its read-only status.
 

docs/atl/fundamentals-of-atl-com-objects.md

@@ -9,7 +9,7 @@ ms.assetid: 0f9c9d98-cc28-45da-89ac-dc94cee422fe
 
 The following illustration depicts the relationship among the classes and interfaces that are used to define an ATL COM object.
 
-![ATL structure](../atl/media/vc307y1.gif "ATL structure")
+![Diagram of the classes and interfaces used to define an A T L object.](../atl/media/vc307y1.gif "ATL structure")
 
 > [!NOTE]
 > This diagram shows that `CComObject` is derived from `CYourClass` whereas `CComAggObject` and `CComPolyObject` include `CYourClass` as a member variable.

docs/atl/identifying-the-elements-of-the-dhtml-control-project.md

@@ -19,7 +19,7 @@ A DHTML control is similar to any ATL control, except:
 
 The following graphic illustrates the relationship between your DLL, the DHTML control, the Web browser, and the HTML resource.
 
-![Elements of a DHTML control project](../atl/media/vc52en1.gif "Elements of a DHTML control project")
+![Diagram of the elements of a DHTML control project.](../atl/media/vc52en1.gif "Elements of a DHTML control project")
 
 > [!NOTE]
 > The names on this graphic are placeholders. The names of your HTML resource and the interfaces exposed on your control are based on the names you assign them in the ATL Control Wizard.
@@ -40,7 +40,7 @@ In this graphic, the elements are:
 
 The ATL Control Wizard generates a control with default code in both the HTML resource and the .cpp file. You can compile and run the control as generated by the wizard, and then view the control in either the Web browser or the ActiveX Control Test Container. The picture below shows the default ATL DHTML control with three buttons displayed in Test Container:
 
-![ATL DHTML control](../atl/media/vc52en2.gif "ATL DHTML control")
+![ATL DHTML control.](../atl/media/vc52en2.gif "ATL DHTML control")
 
 See [Creating an ATL DHTML Control](../atl/creating-an-atl-dhtml-control.md) to get started building a DHTML control. See [Testing Properties and Events with Test Container](../mfc/testing-properties-and-events-with-test-container.md) for information on how to access Test Container.
 

docs/build-insights/tutorials/vcperf-and-wpa.md

@@ -31,7 +31,7 @@ NOTE: Windows 8 or above is required for installing the Windows Performance Anal
 
 1. When prompted for the features that you want to install, select the **Windows Performance Toolkit**. You may select other features if you wish, but they're not required to install WPA.
 
-   ![The Windows Performance Analyzer installer's feature selection screen](media/wpa-installation.png)
+   ![The Windows Performance Analyzer installer's feature selection screen.](media/wpa-installation.png)
 
 ### <a name="configuration-steps"></a> To configure WPA
 
@@ -75,7 +75,7 @@ To view C++ Build Insights data, first collect it into a trace file by following
 
 Here's what a typical *vcperf.exe* command sequence looks like in a developer command prompt window:
 
-![A simple vcperf.exe usage scenario](media/vcperf-simple-usage.png)
+![Screenshot of a command window showing vcperf.exe commands and results.](media/vcperf-simple-usage.png)
 
 ### Important notes about vcperf.exe
 
@@ -104,7 +104,7 @@ Launch WPA and open the trace you just collected. WPA should recognize it as a C
 
 If you can't see these views, double-check that WPA is configured correctly, as described in [Step 1](#configuration-steps). You can view your build data by dragging the views into the empty Analysis window on the right, as shown here:
 
-![Viewing a C++ Build Insights trace in Windows Performance Analyzer](media/wpa-viewing-trace.gif)
+![View of a C++ Build Insights trace in Windows Performance Analyzer.](media/wpa-viewing-trace.gif)
 
 Other views are available in the Graph Explorer panel. Drag them into the Analysis window when you're interested in the information they contain. A useful one is the CPU (Sampled) view, which shows CPU utilization throughout your build.
 

docs/build/arm64-exception-handling.md

@@ -47,7 +47,7 @@ These assumptions are made in the exception handling description:
 
 ## ARM64 stack frame layout
 
-![stack frame layout](media/arm64-exception-handling-stack-frame.png "stack frame layout")
+![Diagram that shows the stack frame layout for functions.](media/arm64-exception-handling-stack-frame.png "stack frame layout")
 
 For frame chained functions, the fp and lr pair can be saved at any position in the local variable area, depending on optimization considerations. The goal is to maximize the number of locals that can be reached by a single instruction based on the frame pointer (x29) or stack pointer (sp). However, for `alloca` functions, it must be chained, and x29 must point to the bottom of stack. To allow for better register-pair-addressing-mode coverage, nonvolatile register save areas are positioned at the top of the Local area stack. Here are examples that illustrate several of the most efficient prolog sequences. For the sake of clarity and better cache locality, the order of storing callee-saved registers in all canonical prologs is in "growing up" order. `#framesz` below represents the size of entire stack (excluding alloca area). `#localsz` and `#outsz` denote local area size (including the save area for the \<x29, lr> pair) and outgoing parameter size, respectively.
 
@@ -182,7 +182,7 @@ The .pdata records are an ordered array of fixed-length items that describe ever
 
 Each .pdata record for ARM64 is 8 bytes in length. The general format of each record places the 32-bit RVA of the function start in the first word, followed by a second word that contains either a pointer to a variable-length .xdata block, or a packed word describing a canonical function unwinding sequence.
 
-![.pdata record layout](media/arm64-exception-handling-pdata-record.png ".pdata record layout")
+![.pdata record layout.](media/arm64-exception-handling-pdata-record.png ".pdata record layout")
 
 The fields are as follows:
 
@@ -198,7 +198,7 @@ The fields are as follows:
 
 When the packed unwind format is insufficient to describe the unwinding of a function, a variable-length .xdata record must be created. The address of this record is stored in the second word of the .pdata record. The format of the .xdata is a packed variable-length set of words:
 
-![.xdata record layout](media/arm64-exception-handling-xdata-record.png ".xdata record layout")
+![.xdata record layout.](media/arm64-exception-handling-xdata-record.png ".xdata record layout")
 
 This data is broken into four sections:
 
@@ -330,7 +330,7 @@ For functions whose prologs and epilogs follow the canonical form described belo
 
 The format of a .pdata record with packed unwind data looks like this:
 
-![.pdata record with packed unwind data](media/arm64-exception-handling-packed-unwind-data.png ".pdata record with packed unwind data")
+![.pdata record with packed unwind data.](media/arm64-exception-handling-packed-unwind-data.png ".pdata record with packed unwind data")
 
 The fields are as follows:
 

docs/build/clang-support-cmake.md

@@ -25,7 +25,7 @@ You can use Visual Studio with Clang to edit and debug C++ CMake projects that t
 
 For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang compiler for Windows** under **Desktop development with C++** optional components. When using a custom Clang installation, check the **C++ Clang-cl for v142 build tools** component.
 
-![Clang component installation](media/clang-install-vs2019.png)
+![Clang component installation.](media/clang-install-vs2019.png)
 
 ## Create a new configuration
 
@@ -35,11 +35,11 @@ To add a new Clang configuration to a CMake project:
 
 1. Under **Configurations**, press the **Add Configuration** button:
 
-   ![Add configuration](media/cmake-add-config-icon.png)
+   ![Add configuration.](media/cmake-add-config-icon.png)
 
 1. Choose the desired Clang configuration (note that separate Clang configurations are provided for Windows and Linux), then press **Select**:
 
-   ![CMake Clang configuration](media/cmake-clang-configuration.png)
+   ![CMake Clang configuration.](media/cmake-clang-configuration.png)
 
 1. To make modifications to this configuration, use the **CMake Settings Editor**. For more information, see [Customize CMake build settings in Visual Studio](customize-cmake-settings.md).
 
@@ -76,6 +76,6 @@ After you have set up a Clang configuration, you can build and debug the project
 
 When debugging, you can use breakpoints, memory and data visualization, and most other debugging features. Some compiler-dependent features such as Edit and Continue are not available for Clang configurations.
 
-![CMake Clang debugging](media/clang-debug-visualize.png)
+![Screenshot of the Visual Studio debugger debugging a CMake Clang project.](media/clang-debug-visualize.png)
 
 ::: moniker-end

docs/build/clang-support-msbuild.md

@@ -111,6 +111,6 @@ After you have set up a Clang configuration, right-click again on the project no
 
 When debugging, you can use breakpoints, memory and data visualization, and most other debugging features.  
 
-![Clang debugging](media/clang-debug-msbuild.png)
+![Screenshot of Visual Studio showing Clang debugging.](media/clang-debug-msbuild.png)
 
 ::: moniker-end

docs/build/cmake-presets-vs.md

@@ -110,7 +110,7 @@ If you try to open or modify a `CMakePresets.json` file that doesn't exist, Visu
 
 Visual Studio provides three dropdown lists when `CMakePresets.json` integration is enabled:
 
-![Screenshot that shows the dropdown lists for the Target System](./media/target-system-dropdown.png)
+![Screenshot that shows the dropdown lists for the Target System.](./media/target-system-dropdown.png)
 
 ### Select a Target System