Fix link and apply some suggestions from the grammar checker.

Xazax-hun · Xazax-hun · commit b9f5c175502d · 2023-05-18T16:17:53.000-07:00
diff --git a/docs/code-quality/c26437.md b/docs/code-quality/c26437.md
@@ -13,7 +13,7 @@ ms.assetid: ed2f55bc-a6d8-4cc4-8069-5c96e581a96a
 **C++ Core Guidelines**:
 [ES.63: Don't slice](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-slice)
 
-[Slicing](https://en.wikipedia.org/wiki/Object_slicing) is allowed by the compiler and can be viewed as a special case of a dangerous implicit cast. Even if it's done intentionally and doesn't lead to immediate issues, it's still highly discouraged. It makes code harder to change, by forcing extra requirements on related data types. It's especially true if types are polymorphic or involve resource management.
+The language allows [slicing](https://en.wikipedia.org/wiki/Object_slicing) and can be viewed as a special case of a dangerous implicit cast. Even if it's done intentionally and doesn't lead to immediate issues, it's still highly discouraged. It makes code harder to change, by forcing extra requirements on related data types. It's especially true if types are polymorphic or involve resource management.
 
 ## Remarks
 
@@ -44,7 +44,7 @@ bool read_id(stream &s, id &v) {
 }
 ```
 
-To fix the issue update the function to use the correct types:
+To fix the issue, update the function to use the correct types:
 
 ```cpp
 // ...
diff --git a/docs/code-quality/c26439.md b/docs/code-quality/c26439.md
@@ -14,7 +14,7 @@ ms.assetid: 9df2a1b0-ea94-4884-9d28-c1522ec33a1b
 
 Some kinds of operations should never throw exceptions. Their implementations should be reliable and should handle possible errors conditions gracefully. They should never use exceptions to indicate failure. This rule flags cases where such operations aren't explicitly marked as `noexcept`, which means that they may throw exceptions and can't convey assumptions about their reliability.
 
-It is important for these operations to be reliable as they are often used to implement operations with certain [exception safety guarantees](https://en.cppreference.com/w/cpp/language/exceptions). A throwing move constructor could also force STL containers to fall back to copy operations and reduce the runtime performance.
+It's important for these operations to be reliable as they're often used to implement operations with certain [exception safety guarantees](https://en.cppreference.com/w/cpp/language/exceptions). A throwing move constructor could also force STL containers to fall back to copy operations and reduce the runtime performance.
 
 Code analysis name: `SPECIAL_NOEXCEPT`
 
@@ -25,13 +25,13 @@ Code analysis name: `SPECIAL_NOEXCEPT`
   - move constructors and move assignment operators;
   - standard functions with move semantics: `std::move` and `std::swap`.
 
-- Non-standard and outdated specifiers like `throw()` or `declspec(nothrow)` aren't equivalent to `noexcept`.
+- Nonstandard and outdated specifiers like `throw()` or `declspec(nothrow)` aren't equivalent to `noexcept`.
 
 - Explicit specifiers `noexcept(false)` and `noexcept(true)` are respected appropriately.
 
 ## Example
 
-All functions except the destructor will warn because they're missing noexcept.
+The tool warns on all functions except the destructor because they're missing noexcept.
 
 ```cpp
 struct S
@@ -63,5 +63,5 @@ struct S
 
 ## See also
 
-[C26455](./c26455)\
+[C26455](./c26455.md)\
 [**C++ Core Guidelines** F.6](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-noexcept)
diff --git a/docs/code-quality/c26455.md b/docs/code-quality/c26455.md
@@ -23,5 +23,5 @@ Code analysis name: `DEFAULT_CTOR_NOEXCEPT`
 
 ## See also
 
-[C26439](./c26439)\
+[C26439](./c26439.md)\
 [**C++ Core Guidelines** F.6](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-noexcept)
diff --git a/docs/code-quality/c26498.md b/docs/code-quality/c26498.md
@@ -37,7 +37,7 @@ void foo()
 }
 ```
 
-To fix the issues mark the flagged variables **`constexpr`**:
+To fix the issues, mark the flagged variables **`constexpr`**:
 
 ```cpp
 constexpr int getMyValue()
diff --git a/docs/code-quality/c26800.md b/docs/code-quality/c26800.md
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C26800"]
 
 ## Remarks
 
-Warning C26800 is triggered when variable is used after it has been moved from. A variable is considered moved from after it was passed to a function as rvalue reference. There are some legitimate exceptions for uses such as assignment, destruction, and some state resetting functions such as `std::vector::clear`. After using a state resetting function, we are free to use the variable. This check only reasons about the local variables.
+Warning C26800 is triggered when variable is used after it has been moved from. A variable is considered moved from after it was passed to a function as rvalue reference. There are some legitimate exceptions for uses such as assignment, destruction, and some state resetting functions such as `std::vector::clear`. After using a state resetting function, we're free to use the variable. This check only reasons about the local variables.
 
 The following methods are considered state resetting methods:
 - Functions with the following substring in their name (not considering case sensitivity): "clear", "clean", "reset", "free", "destroy", "release", "dealloc", "assign"
@@ -46,7 +46,7 @@ Code analysis name: `USE_OF_A_MOVED_FROM_OBJECT`
 
 ## Examples
 
-The following code will generate C26800.
+The following code generates C26800.
 
 ```cpp
 #include <utility>
@@ -70,7 +70,7 @@ void test() {
 }
 ```
 
-The following code won't generate C26800.
+The following code doesn't generate C26800.
 
 ```cpp
 #include <utility>

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ void foo()`
`37`	`37`	`}`
`38`	`38`	```
`39`	`39`
`40`		-To fix the issues mark the flagged variables `constexpr`:
	`40`	+To fix the issues, mark the flagged variables `constexpr`:
`41`	`41`
`42`	`42`	```cpp
`43`	`43`	`constexpr int getMyValue()`