fix alt-text

Author: TylerMSFT

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

@@ -57,13 +57,13 @@ 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**:
 
-:::image type="content" source="media/int-naming-convention-apply-naming-convention.png" :::
+:::image type="content" source="media/int-naming-convention-apply-naming-convention.png" alt-text="Screenshot of the IDE suggesting to apply 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. This check check can be applied to any project that has an `editorconfig` file, and can customize your `.editorconfig` file to suit your project's coding style.
+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.
 
 ## See also
 

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

@@ -35,7 +35,7 @@ double getRadius()
 
 ## How to fix the issue
 
-The solution proposed by the linter is to mark member functions `const` when they do not 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
@@ -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="content" source="media/make-member-function-const.png" :::
-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 change make the change.
+:::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:::
 
 ## 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 do not modify the object's state.
+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. However, it is a good practice to declare member functions as `const` from the beginning if they do not 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.
 
 ## See also