improve draft

Author: TylerMSFT

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

@@ -10,32 +10,20 @@ monikerRange: ">=msvc-170"
 
 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 [`.editorconfig` on ](https://raw.githubusercontent.com/microsoft/vc-ue-extensions/main/Source/.editorconfig).
+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).
 
 ## Example
 
-The For example, an `editorconfig` file that contains:
+Given an `editorconfig` file that contains:
 
-```cpp
-class MyClass
-{ 
-
-public: 
-
-  int getValue() { return value; }  // Flagged: ‘getValue’ doesn't modify the object's state. 
-
-  void setValue(int newValue) { value = newValue; }  // OK: ‘setValue’ modifies the object's state.   
-
-private: 
-
-  int value = 42; 
-
-}; 
+```
+cpp_naming_style.boolean_style.capitalization = pascal_case
+cpp_naming_style.boolean_style.required_prefix = b
 ``````
 
-flags the following code:
+The linter will flag the following code:
 
 ```cpp
 void example()
@@ -46,7 +34,7 @@ void example()
 
 ## How to fix the issue
 
-Change the naming based on the code style specified in the `.editorconfig`. For example:
+Change the naming to match the style specified in the `.editorconfig`. For example:
 
 ```cpp
 void example()
@@ -55,9 +43,9 @@ void example()
 } 
 ```
 
-The editor can make the change for you. Place the cursor on the flagged symbol, and choose **Show potential fixes** and then **Apply naming convention**:
+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="content" source="media/int-naming-convention-apply-naming-convention.png" alt-text="Screenshot of the IDE suggesting to 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.":::
 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:::
 

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, mark them as const. 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 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).
 
 ## Example
 
@@ -18,13 +18,11 @@ class MyClass
 public: 
 
   int getValue() { return value; }  // Flagged: ‘getValue’ doesn't modify the object's state. 
-
   void setValue(int newValue) { value = newValue; }  // OK: ‘setValue’ modifies the object's state.   
 
 private: 
 
   int value = 42; 
-
 }; 
 
 double getRadius()
@@ -35,7 +33,9 @@ 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. In the following example, `const` has been added to `getValue()` and `getRadius()`:
+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.
+
+In the following example, `const` has been added to `getValue()` and `getRadius()`:
 
 ```cpp
 class MyClass
@@ -57,12 +57,14 @@ 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**:
+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." :::
 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.

docs/ide/toc.yml

@@ -32,10 +32,10 @@ items:
         href: ../ide/lnt-logical-bitwise-mismatch.md
       - name: lnt-int-naming-convention
         href: ../ide/lnt-int-naming-convention.md
-      - name: lnt-uninitialized-local
-        href: ../ide/lnt-uninitialized-local.md
       - name: lnt-make-member-function-const
         href: ../ide/lnt-make-member-function-const.md
+      - name: lnt-uninitialized-local
+        href: ../ide/lnt-uninitialized-local.md
     - name: Change signature
       href: ../ide/refactoring/change-signature.md
     - name: Convert to raw string literal