draft

Author: TylerMSFT

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

@@ -8,7 +8,7 @@ monikerRange: ">=msvc-170"
 ---
 # `make-member-function-const`
 
-When member functions don’t modify their object 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).
+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).
 
 ## Example
 
@@ -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 provides a clear indication to both developers and the compiler that the function is safe to call on `const` objects.
+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.
 
 In the following example, `const` has been added to `getValue()` and `getRadius()`:
 
@@ -59,7 +59,7 @@ 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="content" source="media/make-member-function-const.png" alt-text="Screenshot of the editor suggesting to make member const." :::
+:::image type="complex" source="media/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:::
 
@@ -69,7 +69,7 @@ Make this change for all flagged member functions.
 
 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 for the assignment of `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.
+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.
 
 ## See also
 

docs/ide/lnt-int-naming-convention.md renamed to docs/ide/lnt-naming-convention.md

@@ -1,18 +1,18 @@
 ---
-title: int-naming-convention
-description: "Reference for Visual Studio C++ IntelliSense Linter check int-naming-convention."
+title: lnt-naming-convention
+description: "Reference for Visual Studio C++ IntelliSense Linter check lnt-naming-convention."
 ms.date: 09/27/2023
-f1_keywords: ["int-naming-convention"]
-helpviewer_keywords: ["int-naming-convention"]
+f1_keywords: ["lnt-naming-convention"]
+helpviewer_keywords: ["lnt-naming-convention"]
 monikerRange: ">=msvc-170"
 ---
-# `int-naming-convention`
+# `lnt-naming-convention`
 
 Ensure that the naming convention for symbols aligns with the coding style specified in the project's `.editorconfig` file.
 
 To enable this feature, add an `.editorconfig` file in the same directory as your project file. The `.editorconfig` specifies the naming conventions for symbols in your project. For an example `.editorconfig` that specifies the naming conventions for Unreal Engine projects, see this example on [GitHub](https://raw.githubusercontent.com/microsoft/vc-ue-extensions/main/Source/.editorconfig).
 
-Once you have the `.editorconfig` file in your project, turn on the `int-naming-convention` check with the **Naming Convention** setting in the C/C++ Code Style options. For information about how to change this setting, see [Configure the linter](cpp-linter-overview.md#configure-the-linter).
+Once you have the `.editorconfig` file in your project, turn on the `lnt-naming-convention` check with the **Naming Convention** setting in the C/C++ Code Style options. For information about how to change this setting, see [Configure the linter](cpp-linter-overview.md#configure-the-linter).
 
 ## Example
 
@@ -21,9 +21,9 @@ Given an `editorconfig` file that contains:
 ```
 cpp_naming_style.boolean_style.capitalization = pascal_case
 cpp_naming_style.boolean_style.required_prefix = b
-``````
+```
 
-The linter will flag the following code:
+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:
 
 ```cpp
 void example()
@@ -34,7 +34,7 @@ void example()
 
 ## How to fix the issue
 
-Change the naming to match the style specified in the `.editorconfig`. For example:
+Change the naming to match the style specified in the `.editorconfig`:
 
 ```cpp
 void example()
@@ -45,13 +45,13 @@ void example()
 
 The editor can make the change for you. Place the cursor on the flagged symbol. Choose **Show potential fixes** and then **Apply naming convention**:
 
-:::image type="complex" source="media/int-naming-convention-apply-naming-convention.png" alt-text="Screenshot of the IDE suggesting applying naming convention.":::
+:::image type="complex" source="media/lnt-naming-convention-apply-naming-convention.png" alt-text="Screenshot of the IDE suggesting applying naming convention.":::
 The code editor shows bool myFlag = true. With the cursor on that line of code, **Show potential fixes** appeared and was chosen. Now **Apply naming convention** is visible and it shows bool my Flag = true in red and the suggested change, bool b My Flag, in green. You can now choose **Apply naming convention** to change the flagged code to bool b My Flag = true.
 :::image-end:::
 
 ## Remarks
 
-The `int-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.
+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
 

docs/ide/toc.yml

@@ -30,10 +30,10 @@ items:
         href: ../ide/lnt-integer-float-division.md
       - name: lnt-logical-bitwise-mismatch
         href: ../ide/lnt-logical-bitwise-mismatch.md
-      - name: lnt-int-naming-convention
-        href: ../ide/lnt-int-naming-convention.md
       - name: lnt-make-member-function-const
         href: ../ide/lnt-make-member-function-const.md
+      - name: lnt-naming-convention
+        href: ../ide/lnt-naming-convention.md
       - name: lnt-uninitialized-local
         href: ../ide/lnt-uninitialized-local.md
     - name: Change signature