alt-text fixes

TylerMSFT · TylerMSFT · commit 401c607addbc · 2023-02-01T14:21:32.000-08:00
diff --git a/docs/build/media/vcppdir_libdir_macros.png b/docs/build/media/vcppdir_libdir_macros.png
diff --git a/docs/build/reference/common-macros-for-build-commands-and-properties.md b/docs/build/reference/common-macros-for-build-commands-and-properties.md
@@ -3,17 +3,19 @@ description: "Learn more about: Common macros for MSBuild commands and propertie
 title: "Common macros for MSBuild commands and properties"
 ms.date: 03/15/2022
 helpviewer_keywords: ["$(FrameworkSDKDir) macro", "ProjectName macro $(ProjectName)", "DevEnvDir macro $(DevEnvDir)", "$(DevEnvDir) macro", "TargetPath macro $(TargetPath)", "VSInstallDir macro $(VSInstallDir)", "$(InputFileName) macro", "$(SolutionFileName) macro", "macros [C++], build macros", "InputFileName macro $(InputFileName)", "$(VCInstallDir) macro", "$(IntDir) macro", "$(ConfigurationName) macro", "SolutionDir macro $(SolutionDir)", "$(TargetPath) macro", "$(Inherit) macro", "$(SolutionPath) macro", "WebDeployRoot macro $(WebDeployRoot)", "WebDeployPath macro $(WebDeployPath)", "StopEvaluating macro $(StopEvaluating)", "$(RootNamespace) macro", "$(WebDeployRoot) macro", "ProjectPath macro $(ProjectPath)", "$(ProjectPath) macro", "$(InputDir) macro", "SolutionName macro $(SolutionName)", "ProjectExt macro $(ProjectExt)", "$(TargetExt) macro", "$(ProjectFileName) macro", "TargetName macro $(TargetName)", "$(References) macro", "References macro $(References)", "TargetExt macro $(TargetExt)", "ProjectDir macro $(ProjectDir)", "$(TargetDir) macro", "SolutionExt macro $(SolutionExt)", "$(SolutionDir) macro", "ProjectFileName macro $(ProjectFileName)", "VCInstallDir macro $(VCInstallDir)", "$(InputExt) macro", "$(TargetFileName) macro", "$(SolutionExt) macro", "PlatformName macro $(PlatformName)", "IntDir macro $(IntDir)", "$(FrameworkVersion) macro", "$(ProjectDir) macro", "build macros [C++]", "InputPath macro $(InputPath)", "$(VSInstallDir) macro", "$(WebDeployPath) macro", "TargetFileName macro $(TargetFileName)", "NoInherit macro $(NoInherit)", "ConfigurationName macro $(ConfigurationName)", "$(ProjectExt) macro", "TargetDir macro $(TargetDir)", "InputName macro $(InputName)", "$(ProjectName) macro", "FrameworkSDKDir macro $(FrameworkSDKDir)", "$(ParentName) macro", "InputExt macro $(InputExt)", "$(SafeRootNamespace) macro", "InputDir macro $(InputDir)", "$(FxCopDir) macro", "$(RemoteMachine) macro", "Inherit macro $(Inherit)", "FrameworkVersion macro $(FrameworkVersion)", "$(StopEvaluating) macro", "$(OutDir) macro", "FrameworkDir macro $(FrameworkDir)", "SolutionFileName macro $(SolutionFileName)", "$(NoInherit) macro", "RemoteMachine macro $(RemoteMachine)", "properties [C++], build property macros", "$(TargetName) macro", "$(SolutionName) macro", "$(InputPath) macro", "ParentName macro $(ParentName)", "OutDir macro $(OutDir)", "SafeRootNamespace macro $(SafeRootNamespace)", "FxCopDir macro $(FxCopDir)", "$(InputName) macro", "RootNamespace macro $(RootNamespace)", "builds [C++], macros", "$(FrameworkDir) macro", "$(PlatformName) macro", "$(PlatformShortName) macro","SolutionPath macro $(SolutionPath)"]
-ms.assetid: 239bd708-2ea9-4687-b264-043f1febf98b
 ---
 # Common macros for MSBuild commands and properties
 
 Depending on your installation options, Visual Studio can make hundreds of macros available to you in an MSBuild-based *`.vcxproj`* Visual Studio project. The macros correspond to the MSBuild properties that are set by default, or in *`.props`* or *`.targets`* files, or in your project settings. You can use these macros anywhere in a project's **Property Pages** dialog box where strings are accepted. These macros aren't case-sensitive.
 
 ## View the current properties and macros
 
-To display all of the currently available macros, in the **Property Pages** dialog, under **VC++ Directories**, choose the drop-down arrow at the end of a property row. Select **Edit** and then in the Edit dialog box, choose the **Macros** button. The current set of properties and macros visible to Visual Studio is listed along with the current value for each. For more information, see the **Specifying User-Defined Values** section of [C++ project property page reference](property-pages-visual-cpp.md).
+To display all of the currently available macros, open the project property pages from the main menu by selecting **Project** > **Properties**. In the **Property Pages** dialog, choose an entry that has a macro in it. You can recognize a a macro by the dollar sign and parenthesis that surround its name. For example, select **Configuration Properties** > **VC++ Directories** in the left pane, and then select **Include directories** in the right pane. The value for **Include directories** is `$(VC_IncludePath);$(WindowsSDK_IncludePath);`, which indicates that the include directories are populated by the expansion of those two macros. Select the drop-down arrow at the end of that row (you'll need to click the row to see it), then select **Edit**. In the **Include Directories** dialog box that appears, select the **Macros>>** button. That expands the dialog to show the current set of properties and macros visible to Visual Studio, along with the current value for each. For more information, see the **Specifying User-Defined Values** section of [C++ project property page reference](property-pages-visual-cpp.md).
 
-![Screenshot of the Library Directories dialog after choosing the Macros button.](../media/vcppdir_libdir_macros.png "Macros menu")
+![Screenshot of the Executable Directories dialog after choosing the Macros button.]( "Macros menu")
+:::image type="complex" source="../media/vcppdir_libdir_macros.png" alt-text="Macros menu.":::
+Screenshot of the Visual Studio **Include Directories** dialog. On the right are a list of Visual Studio macros. On the left is a pane that shows the evaluated value of the include directory property. The bottom pane shows which macros were expanded, if any, as part of the evaluation. Because the Include Directories macro is a combination of two other macros, $(VC_IncludePath) and $(WindowsSDK_IncludePath), the bottom pane, labeled Inherited values, lists those two macros.
+:::image-end:::
 
 ## List of common macros
 
diff --git a/docs/cpp/destructors-cpp.md b/docs/cpp/destructors-cpp.md
@@ -3,7 +3,6 @@ description: "Learn more about: Destructors (C++)"
 title: "Destructors (C++)"
 ms.date: "07/20/2019"
 helpviewer_keywords: ["objects [C++], destroying", "destructors, C++"]
-ms.assetid: afa859b0-f3bc-4c4d-b250-c68b335b6004
 ---
 # Destructors (C++)
 
@@ -140,8 +139,9 @@ B1 dtor
 
 Destructors for virtual base classes are called in the reverse order of their appearance in a directed acyclic graph (depth-first, left-to-right, postorder traversal). the following figure depicts an inheritance graph.
 
-![Inheritance graph that shows virtual base classes.](../cpp/media/vc392j1.gif "Inheritance graph that shows virtual base classes") <br/>
-Inheritance graph that shows virtual base classes
+:::image type="complex" source="../cpp/media/vc392j1.gif" alt-text="Inheritance graph that shows virtual base classes.":::
+There are 5 classes, labeled A through E, arranged in an inheritance graph. Class E is the base class of classes B, C, and D. Classes C and D are the base class of classes A and B.
+:::image-end:::
 
 The following lists the class heads for the classes shown in the figure.
 
diff --git a/docs/cpp/lambda-expressions-in-cpp.md b/docs/cpp/lambda-expressions-in-cpp.md
@@ -1,9 +1,8 @@
 ---
 description: "Learn more about: Lambda Expressions in C++"
 title: "Lambda expressions in C++"
-ms.date: 07/13/2021
+ms.date: 01/30/2023
 helpviewer_keywords: ["lambda expressions [C++]", "lambda expressions [C++], overview", "lambda expressions [C++], vs. function objects"]
-ms.assetid: 713c7638-92be-4ade-ab22-fa33417073bf
 ---
 # Lambda expressions in C++
 
@@ -17,7 +16,7 @@ In C++11 and later, a lambda expression—often called a *lambda*—is a conveni
 
 ## Parts of a lambda expression
 
-The ISO C++ Standard shows a simple lambda that is passed as the third argument to the `std::sort()` function:
+Here is a simple lambda that is passed as the third argument to the `std::sort()` function:
 
 ```cpp
 #include <algorithm>
@@ -36,6 +35,7 @@ void abssort(float* x, unsigned n) {
 This illustration shows the parts of a lambda:
 
 ![An illustration of the structural elements of a lambda expression.](../cpp/media/lambdaexpsyntax.png "Structural elements of a lambda expression")
+:::image type="complex" source="../cpp/media/lambdaexpsyntax.png" alt-text="Diagram that identifies the various parts of a lambda expression":::Diagram that identifies the various parts of a lambda expression. The lambda expression example is [=]() mutable throw() -> int { return x+y; } The [=] is the capture clause; also known as the lambda-introducer in the C++ specification. The parenthesis are for the parameter list. The mutable keyword is optional. throw() is the optional exception specification. -> int is the optional trailing return type. The lambda body consists of the statement inside the curly braces, or return x+y; These are explained in more detail following the image.:::image-end:::
 
 1. *capture clause* (Also known as the *lambda-introducer* in the C++ specification.)
 
diff --git a/docs/cpp/tutorial-named-modules-cpp.md b/docs/cpp/tutorial-named-modules-cpp.md
@@ -66,7 +66,7 @@ A module consists of one or more files. One of these files must be what is calle
 
 To add a primary module interface unit, in **Solution Explorer**, right-click **Source Files** then select **Add** > **Module**.
 
-![Add item dialog in solution explorer with Add > Module... highlighted to illustrate where to click to add a module](media/add-module.png)
+![Add item dialog in solution explorer with Add > Module... highlighted to illustrate where to click to add a module.](media/add-module.png)
 
 In the **Add New Item** dialog that appears, give the new module the name *`BasicPlane.Figures.ixx`* and choose **Add**.
 
diff --git a/docs/mfc/reference/cwnd-class.md b/docs/mfc/reference/cwnd-class.md
