@@ -1,7 +1,7 @@
 ---
 title: "CMake projects in Visual Studio"
 description: "How to create and build C++ projects using CMake in Visual Studio."
-ms.date: 12/15/2021
+ms.date: 02/14/2022
 helpviewer_keywords: ["CMake in Visual C++"]
 ms.assetid: 444d50df-215e-4d31-933a-b41841f186f8
 ---
@@ -41,9 +41,9 @@ When you **open a folder** containing a *`CMakeLists.txt`* file, the following t
 > [!NOTE]
 > Starting in Visual Studio 2022 version 17.1 Preview 2, if your folder doesn't contain a root `CMakeLists.txt` you'll be prompted whether you'd like to enable CMake integration or not. For more information, see [CMake partial activation](#cmake-partial-activation).
 
-Once CMake cache generation has succeeded, you can also view your projects organized logically by targets. Choose **Targets view** from the dropdown in the **Solution Explorer** toolbar:
+Once CMake cache generation has succeeded, you can also view your projects organized logically by targets. Choose the **Select View** button on the **Solution Explorer** toolbar. From the list in **Solution Explorer - Views**, select **CMake Targets View** and press **Enter** to open the targets view:
 
-![CMake targets view button.](media/cmake-targets-view.png)
+:::image type="content" source="media/cmake-targets-view-dark.png" alt-text="Screenshot of the Solution Explorer window with the Select View toolbar button highlighted.":::
 
 Choose the **Show All Files** button at the top of **Solution Explorer** to see all the CMake-generated output in the *`out/build/<config>`* folders.
 
@@ -90,7 +90,7 @@ You can also disable all CMake cache notifications (gold bars) by deselecting **
 
 If you need more information about the state of the CMake cache to diagnose a problem, open the **Project** main menu or the *`CMakeLists.txt`* context menu in **Solution Explorer** to run one of these commands:
 
-- **View CMakeCache.txt** opens the *`CMakeCache.txt`* file from the build directory in the editor. Any edits you make here to *`CMakeCache.txt`* are wiped out if you clean the cache. To make changes that persist after you clean the cache, see [Customize CMake settings](customize-cmake-settings.md) or [Configure and Build with CMake Presets](cmake-presets-vs.md).
+- **View CMakeCache.txt** opens the *`CMakeCache.txt`* file from the build directory in the editor. Any edits you make here to *`CMakeCache.txt`* are wiped out if you clean the cache. To make changes that persist after you clean the cache, see [Customize CMake settings](customize-cmake-settings.md) or [Configure and build with CMake Presets](cmake-presets-vs.md).
 
 - **Delete Cache and Reconfigure** deletes the build directory and reconfigures from a clean cache.
 
@@ -149,7 +149,7 @@ Visual Studio allows you to debug a process running on a remote Linux system or
 
 ## <a name="cmake-partial-activation"></a> CMake partial activation
 
-Starting in Visual Studio 2022 version 17.1 Preview 2, CMake functionality won't be enabled automatically if your root folder doesn't contain a `CMakeLists.txt` file. Instead, a dialog will prompt you on whether you'd like to enable CMake functionality for your project. If you decline, CMake cache generation won't start and CMake configurations (from `CMakeSettings.json` or `CMakePresets.json`) won't appear in the configuration dropdown. If you accept, you'll be taken to a workspace-level configuration file, `CMakeWorkspaceSettings.json` (stored in the `.vs` directory), to specify the folders you'd like to enable CMake for. (These folders contain your root `CMakeLists.txt` files).
+In Visual Studio 2022 version 17.1 and later, CMake functionality won't be enabled automatically if your root folder doesn't contain a `CMakeLists.txt` file. Instead, a dialog will prompt you on whether you'd like to enable CMake functionality for your project. If you decline, CMake cache generation won't start and CMake configurations (from `CMakeSettings.json` or `CMakePresets.json`) won't appear in the configuration dropdown. If you accept, you'll be taken to a workspace-level configuration file, `CMakeWorkspaceSettings.json` (stored in the `.vs` directory), to specify the folders you'd like to enable CMake for. (These folders contain your root `CMakeLists.txt` files).
 
 The accepted properties are:
 
@@ -197,7 +197,7 @@ As soon as you save the file, the configuration step automatically runs again an
 
 ### Language services for CMake
 
-Language services for CMake are available in Visual Studio 2019 version 16.5 or later. Code navigation features like Go To Definition, Peek Definition, and Find All References are supported for CMake variables, functions, and targets in CMake script files. For more information, see [Code Navigation for CMake Scripts](https://devblogs.microsoft.com/cppblog/code-navigation-for-cmake-scripts/).
+Language services for CMake are available in Visual Studio 2019 version 16.5 or later. It supports code navigation features like Go To Definition, Peek Definition, and Find All References for CMake variables, functions, and targets in CMake script files. For more information, see [Code Navigation for CMake Scripts](https://devblogs.microsoft.com/cppblog/code-navigation-for-cmake-scripts/).
 
 ![Find All References on a CMake variable, target, or function.](media/cmake-find-all-refs.png)
 
 
@@ -2,7 +2,7 @@
 description: "Learn more about: C26812"
 title: c26812
 keywords: c26812
-ms.date: 07/15/2019
+ms.date: 02/14/2022
 ms.topic: reference
 f1_keywords: ["C26812"]
 helpviewer_keywords: ["C26812"]
@@ -12,32 +12,32 @@ dev_langs: ["C++"]
 
 > Warning C26812: Prefer 'enum class' over 'enum' (Enum.3)
 
-The enum type *type-name* is unscoped. Prefer 'enum class' over 'enum' (Enum.3)
+The `enum` type *type-name* is unscoped. Prefer `enum class` over `enum` (Enum.3)
 
 ## Example
 
-The following example is from the C++ Core Guidelines
+The following example is from the C++ Core Guidelines:
 
 ```cpp
 void Print_color(int color);
 
-enum Web_color { red = 0xFF0000, green = 0x00FF00, blue = 0x0000FF }; // C26812 reported here
-enum Product_info { Red = 0, Purple = 1, Blue = 2 }; // C26812 reported here
+enum Web_color { red = 0xFF0000, green = 0x00FF00, blue = 0x0000FF };
+enum Product_info { Red = 0, Purple = 1, Blue = 2 };
 
 Web_color webby = Web_color::blue;
 
 // Clearly at least one of these calls is buggy.
-Print_color(webby);
-Print_color(Product_info::Blue);
+Print_color(webby);               // C26812
+Print_color(Product_info::Blue);  // C26812
 ```
 
 These warnings are corrected by declaring the enum as enum class:
 
 ```cpp
 void Print_color(int color);
 
-enum class Web_color { red = 0xFF0000, green = 0x00FF00, blue = 0x0000FF }; // no C26812
-enum class Product_info { red = 0, purple = 1, blue = 2 }; // no C26812
+enum class Web_color { red = 0xFF0000, green = 0x00FF00, blue = 0x0000FF };
+enum class Product_info { Red = 0, Purple = 1, Blue = 2 };
 
 Web_color webby = Web_color::blue;
 Print_color(webby);  // Error: cannot convert Web_color to int.
@@ -46,4 +46,4 @@ Print_color(Product_info::Red);  // Error: cannot convert Product_info to int.
 
 ## See also
 
-[Enum.3 Prefer enum class over enum](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#enum3-prefer-class-enums-over-plain-enums )
+[Enum.3 Prefer enum class over enum](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#enum3-prefer-class-enums-over-plain-enums)
@@ -1,13 +1,13 @@
 ---
 title: "module, import, export"
-ms.date: "12/12/2019"
+ms.date: 02/14/2022
 f1_keywords: ["module_cpp", "import_cpp", "export_cpp"]
 helpviewer_keywords: ["modules [C++]", "modules [C++], import", "modules [C++], export"]
 description: Use import and export declarations to access and to publish types and functions defined in the specified module.
 ---
 # `module`, `import`, `export`
 
-The **`module`**, **`import`**, and **`export`** declarations are available in C++20 and require the [/experimental:module](../build/reference/experimental-module.md) compiler switch along with [/std:c++20](../build/reference/std-specify-language-standard-version.md) or later (such as **`/std:c++latest`**). For more information, see [Overview of modules in C++](modules-cpp.md).
+The **`module`**, **`import`**, and **`export`** declarations are available in C++20 and require the [`/experimental:module`](../build/reference/experimental-module.md) compiler switch along with [`/std:c++20`](../build/reference/std-specify-language-standard-version.md) or later (such as **`/std:c++latest`**). For more information, see [Overview of modules in C++](modules-cpp.md).
 
 ## `module`
 
@@ -40,7 +40,7 @@ namespace ModuleA_NS
 }
 ```
 
-Non-exported names are not visible to code that imports the module:
+Non-exported names aren't visible to code that imports the module:
 
 ```cpp
 //MyProgram.cpp
@@ -56,7 +56,7 @@ int main() {
 
 The **`export`** keyword may not appear in a module implementation file. When **`export`** is applied to a namespace name, all names in the namespace are exported.
 
-## import
+## `import`
 
 Use an **`import`** declaration to make a module's names visible in your program. The `import` declaration must appear after the `module` declaration and after any `#include` directives, but before any declarations in the file.
 
@@ -76,10 +76,9 @@ class Baz
 
 ## Remarks
 
-Both **import** and **module** are treated as keywords only when they appear at the start of a logical line:
+Both **`import`** and **`module`** are treated as keywords only when they appear at the start of a logical line:
 
 ```cpp
-
 // OK:
 module ;
 module module-name
@@ -100,7 +99,7 @@ int i; module ;
 
 **Microsoft Specific**
 
-In Microsoft C++, the tokens **`import`** and **`module`** are always identifiers and never keywords when they are used as arguments to a macro.
+In Microsoft C++, the tokens **`import`** and **`module`** are always identifiers and never keywords when they're used as arguments to a macro.
 
 ### Example
 
 
@@ -1,6 +1,6 @@
 ---
 title: "Overview of modules in C++"
-ms.date: 02/03/2022
+ms.date: 02/14/2022
 helpviewer_keywords: ["modules [C++]", "modules [C++], overview"]
 description: Modules in C++20 provide a modern alternative to header files.
 ---
@@ -93,13 +93,13 @@ When it does argument-dependent lookup for overload resolutions in the importing
 A module can be componentized into *partitions*, each consisting of an interface file and zero or more implementation files. A module partition is similar to a module, except it shares ownership of all declarations in the entire module. All names exported by partition interface files are imported and re-exported by the primary interface file. A partition's name must begin with the module name followed by a colon. Declarations in any of the partitions are visible within the entire module. No special precautions are needed to avoid one-definition-rule (ODR) errors. You can declare a name (function, class, and so on) in one partition and define it in another. A partition implementation file begins like this:
 
 ```cpp
-module Example:part1
+module Example:part1;
 ```
 
 The partition interface file begins like this:
 
 ```cpp
-export module Example:part1
+export module Example:part1;
 ```
 
 To access declarations in another partition, a partition must import it, but it can only use the partition name, not the module name:
@@ -112,8 +112,8 @@ import :part1;
 The primary interface unit must import and re-export all of the module's interface partition files like this:
 
 ```cpp
-export import :part1
-export import :part2
+export import :part1;
+export import :part2;
 ...
 ```