@@ -1,5 +1,5 @@
 ---
-title: "ATL Collection Classes"
+title: "ATL collection class overview"
 ms.date: "11/19/2018"
 helpviewer_keywords: ["DestructElements function", "collection classes, choosing", "ConstructElements function", "SerializeElements function", "traits classes", "collection classes, about collection classes", "CTraits classes", "collection classes"]
 ms.assetid: 4d619d46-5b4e-41dd-b9fd-e86b1fbc00b5
 
@@ -1,5 +1,5 @@
 ---
-title: "ATL Collection Classes"
+title: "Collection classes in ATL"
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords: ["collection classes"]
@@ -79,7 +79,7 @@ The following classes provide support for arrays, lists, maps, and also traits m
 
 ## Related Articles
 
-[ATL Collection Classes](../atl/atl-collection-classes.md)
+[ATL collection class overview](../atl/atl-collection-classes.md)
 
 ## See also
 
 
@@ -149,7 +149,7 @@ In this step, we'll debug an example program that demonstrates the Bullet Physic
 
    If you've already added a remote connection, you can open this window by navigating to **Tools > Options > Cross Platform > Connection Manager**.
 
-1. Provide the [connection information to your Linux machine](/cpp/linux/connect-to-your-remote-linux-computer) and choose **Connect**. Visual Studio adds that machine as to CMakeSettings.json as your default connection for **Linux-Debug**. It also pulls down the headers from your remote machine, so you get [IntelliSense specific to that remote connection](/cpp/linux/configure-a-linux-project?view=vs-2019#remote_intellisense). Next, Visual Studio sends your files to the remote machine and generates the CMake cache on the remote system. These steps may take some time, depending on the speed of your network and power of your remote machine. You'll know it's complete when the message "Target info extraction done" appears in the CMake output window.
+1. Provide the [connection information to your Linux machine](../linux/connect-to-your-remote-linux-computer.md) and choose **Connect**. Visual Studio adds that machine as to CMakeSettings.json as your default connection for **Linux-Debug**. It also pulls down the headers from your remote machine, so you get [IntelliSense specific to that remote connection](../linux/configure-a-linux-project.md#remote_intellisense). Next, Visual Studio sends your files to the remote machine and generates the CMake cache on the remote system. These steps may take some time, depending on the speed of your network and power of your remote machine. You'll know it's complete when the message "Target info extraction done" appears in the CMake output window.
 
 ## Set a breakpoint, build, and run on Linux
 
 
@@ -37,7 +37,7 @@ If **/DRIVER** is specified:
 
 ### To set this linker option programmatically
 
-- See [VCLinkerTool.driver Property](/dotnet/api/microsoft.visualstudio.vcprojectengine.vclinkertool.driver?view=visualstudiosdk-2017#Microsoft_VisualStudio_VCProjectEngine_VCLinkerTool_driver).
+- See [VCLinkerTool.driver Property](/dotnet/api/microsoft.visualstudio.vcprojectengine.vclinkertool.driver).
 
 ## See also
 
 
@@ -4,7 +4,7 @@ ms.date: "11/04/2016"
 helpviewer_keywords: ["<exception> C++ XML tag", "exception C++ XML tag"]
 ms.assetid: 24451e79-9b89-4b77-98fb-702c6516b818
 ---
-# &lt;exception&gt;
+# &lt;exception&gt; tag
 
 The \<exception> tag lets you specify which exceptions can be thrown. This tag is applied to a method definition.
 
 
@@ -20,7 +20,7 @@ When you right-click on a file node **Solution Explorer**, the **General** prope
 
 - **Item Type**
 
-   The **Item Type** specifies the tool that will be used to process the file during the build process. [Files whose extension is known to Visual Studio](/visualstudio/extensibility/visual-cpp-project-extensibility?view=vs-2019#project-items) have a default value in this property. You can specify a custom tool here if you have a custom file type or wish to override the default tool for a known file type. See [Specifying Custom Build Tools](../specifying-custom-build-tools.md) for more information. You can also use this property page to specify that a file is not part of the build process.
+   The **Item Type** specifies the tool that will be used to process the file during the build process. [Files whose extension is known to Visual Studio](/visualstudio/extensibility/visual-cpp-project-extensibility#project-items) have a default value in this property. You can specify a custom tool here if you have a custom file type or wish to override the default tool for a known file type. See [Specifying Custom Build Tools](../specifying-custom-build-tools.md) for more information. You can also use this property page to specify that a file is not part of the build process.
 
    The following illustration shows the property page for a *.cpp* file. The default **Item Type** for this kind of file is the **C/C++ Compiler** (*cl.exe*) and the property page exposes various compiler settings that can be applied to this file only.
 
 
@@ -5,13 +5,13 @@ f1_keywords: ["list"]
 helpviewer_keywords: ["list C++ XML tag", "<list> C++ XML tag"]
 ms.assetid: c792a10b-0451-422c-9aa0-604116e69d64
 ---
-# &lt;list&gt;
+# &lt;list&gt; and &lt;listheader&gt;
 
 The \<listheader> block is used to define the heading row of either a table or definition list. When defining a table, you only need to supply an entry for term in the heading.
 
 ## Syntax
 
-```
+```xml
 <list type="bullet" | "number" | "table">
    <listheader>
       <term>term</term>
 
@@ -1,10 +1,10 @@
 ---
-title: "Resource Files (C++)"
+title: "Project Resource Files (C++)"
 ms.date: "05/14/2019"
 helpviewer_keywords: ["resource files", "resources [C++]"]
 ms.assetid: 338a4a0f-0c62-4ef1-a34f-5d86262d93a4
 ---
-# Resource Files (C++)
+# Project Resource Files (C++)
 
 Resources are interface elements that provide information to the user. Bitmaps, icons, toolbars, and cursors are all resources. Some resources can perform an action such as selecting from a menu or entering data in dialog box.
 
 
@@ -46,7 +46,7 @@ For links to more information about DLLs, see [Create C/C++ DLLs in Visual Studi
 
 ::: moniker range="vs-2015"
 
-- A copy of Visual Studio. For information on how to download and install Visual Studio 2015, see [Install Visual Studio 2015](/visualstudio/install/install-visual-studio-2015?view=vs-2015). Use a **Custom** installation to install the C++ compiler and tools, since they're not installed by default.
+- A copy of Visual Studio. For information on how to download and install Visual Studio 2015, see [Install Visual Studio 2015](/visualstudio/install/install-visual-studio-2015?view=vs-2015&preserve-view=true). Use a **Custom** installation to install the C++ compiler and tools, since they're not installed by default.
 
 ::: moniker-end
 
 
@@ -82,11 +82,11 @@ A user-defined macro is stored in a property sheet. If your project does not alr
 
 You can use the Property Editor to modify certain string properties and select macros as values. To access the Property Editor, select a property on a property page and then choose the down arrow button on the right. If the drop-down list contains **\<Edit>**, then you can choose it to display the Property Editor for that property.
 
-![Property&#95;Editor&#95;Dropdown](media/property_editor_dropdown.png "Property_Editor_Dropdown")
+![A property drop-down control is used to access the Property Editor](media/property_editor_dropdown.png "Property Editor dropdown")
 
 In the Property Editor, you can choose the **Macros** button to view the available macros and their current values. The following illustration shows the Property Editor for the **Additional Include Directories** property after the **Macros** button was chosen. When the **Inherit from parent or project defaults** check box is selected and you add a new value, it is appended to any values that are currently being inherited. If you clear the check box, your new value replaces the inherited values. In most cases, leave the check box selected.
 
-![Property editor, Visual C&#43;&#43;](media/propertyeditorvc.png "PropertyEditorVC")
+![The Property Editor dialog for the Include Directories property](media/propertyeditorvc.png "PropertyEditorVC")
 
 ## Add an include directory to the set of default directories