prepare for review

Author: TylerMSFT

docs/ide/lnt-make-member-function-const.md

@@ -1,12 +1,12 @@
 ---
-title: make-member-function-const
-description: "Reference for Visual Studio C++ IntelliSense Linter check make-member-function-const."
-ms.date: 09/27/2023
-f1_keywords: ["make-member-function-const"]
-helpviewer_keywords: ["make-member-function-const"]
+title: lnt-make-member-function-const
+description: "Reference for Visual Studio C++ IntelliSense Linter check lnt-make-member-function-const."
+ms.date: 09/28/2023
+f1_keywords: ["lnt-make-member-function-const"]
+helpviewer_keywords: ["lnt-make-member-function-const"]
 monikerRange: ">=msvc-170"
 ---
-# `make-member-function-const`
+# `lnt-make-member-function-const`
 
 When member functions don’t modify the object's state, annotate them with the `const` keyword. This guidance comes from the [C++ Core Guideline Con.2](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#con2-by-default-make-member-functions-const).
 
@@ -33,7 +33,7 @@ double getRadius()
 
 ## How to fix the issue
 
-The solution proposed by the linter is to mark member functions `const` when they don't modify the object's state. This let's both developers and the compiler know that the function is safe to call on a `const` object.
+Mark member functions `const` when they don't modify the object's state. This lets both developers and the compiler know that the function is safe to call on a `const` object.
 
 In the following example, `const` has been added to `getValue()` and `getRadius()`:
 
@@ -59,15 +59,15 @@ double getRadius() const // added const
 
 The editor can make this change for you. Place the cursor on the flagged symbol and choose **Show potential fixes** and then **Make member const**:
 
-:::image type="complex" source="media/make-member-function-const.png" alt-text="Screenshot of the editor suggesting to make member const." :::
+:::image type="complex" source="media/lnt-make-member-function-const.png" alt-text="Screenshot of the editor suggesting to make member const." :::
 The cursor is on the line int getValue() and **Show potential fixes** appeared and was chosen. Now **Make member const** is visible and it shows the get value function with const added to it. You can now choose **Make member const** to make the change.
 :::image-end:::
 
 Make this change for all flagged member functions.
 
 ## Remarks
 
-This check focuses on `const` usage for member functions in C++ code. The C++ Core Guidelines recommends marking member functions as `const` when they don't modify the object's state.
+Introduced in Visual Studio 2022 17.8, this check focuses on `const` usage for member functions in C++ code. The C++ Core Guidelines recommends marking member functions as `const` when they don't modify the object's state.
 
 The current implementation of this check allows you to add `const` to member functions after their declaration. It's a good practice to declare member functions as `const` from the beginning if they don't modify the object's state.
 

docs/ide/lnt-naming-convention.md

@@ -1,7 +1,7 @@
 ---
 title: lnt-naming-convention
 description: "Reference for Visual Studio C++ IntelliSense Linter check lnt-naming-convention."
-ms.date: 09/27/2023
+ms.date: 09/28/2023
 f1_keywords: ["lnt-naming-convention"]
 helpviewer_keywords: ["lnt-naming-convention"]
 monikerRange: ">=msvc-170"
@@ -23,7 +23,7 @@ cpp_naming_style.boolean_style.capitalization = pascal_case
 cpp_naming_style.boolean_style.required_prefix = b
 ```
 
-The linter will flag the following code because it isn't prefixed with 'b' and it isn't Pascal case, as specified in the `.editorconfig` file:
+The linter will flag the following code because it isn't prefixed with 'b' and because it isn't Pascal case, as specified in the `.editorconfig` file:
 
 ```cpp
 void example()
@@ -51,7 +51,7 @@ The code editor shows bool myFlag = true. With the cursor on that line of code,
 
 ## Remarks
 
-The `lnt-naming-convention` linter check ensures that naming conventions align with naming conventions specified in the `editorconfig` file. You can apply this check to any project that has an `editorconfig` file. You can also customize your `.editorconfig` file to suit your project's coding style.
+Introduced in Visual Studio 2022 17.7, the `lnt-naming-convention` linter check ensures that naming conventions align with naming conventions specified in the `editorconfig` file. You can apply this check to any project that has an `editorconfig` file. You can also customize your `.editorconfig` file to suit your project's coding style.
 
 ## See also