Address review comments.

Xazax-hun · Xazax-hun · commit 249bee176fbb · 2023-05-26T16:29:45.000-07:00
diff --git a/docs/code-quality/c26439.md b/docs/code-quality/c26439.md
@@ -10,11 +10,11 @@ ms.assetid: 9df2a1b0-ea94-4884-9d28-c1522ec33a1b
 
 > This kind of function may not throw. Declare it 'noexcept'.
 
-[**C++ Core Guidelines** F.6](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-noexcept): If your function must not throw, declare it noexcept
+[**C++ Core Guidelines** F.6](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-noexcept): If your function must not throw, declare it `noexcept`
 
-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.
+Some operations should never throw exceptions. Their implementations should be reliable and should handle possible errors conditions gracefully. They shouldn't 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 consumers can't make assumptions about its reliability.
 
-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.
+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 which reduces runtime performance.
 
 Code analysis name: `SPECIAL_NOEXCEPT`
 
@@ -31,7 +31,7 @@ Code analysis name: `SPECIAL_NOEXCEPT`
 
 ## Example
 
-The tool warns on all functions except the destructor because they're missing noexcept.
+The tool warns on all functions except the destructor because they're missing `noexcept`.
 
 ```cpp
 struct S
@@ -46,7 +46,7 @@ struct S
 };
 ```
 
-With noexcept decorating the same structure, all warnings are removed.
+With `noexcept` decorating the same structure, all warnings are removed.
 
 ```cpp
 struct S
diff --git a/docs/code-quality/c26455.md b/docs/code-quality/c26455.md
@@ -13,7 +13,7 @@ ms.custom: kr2b-contr-experiment
 
 > Default constructor should not throw. Declare it '`noexcept`' (f.6)
 
-The C++ Core Guidelines suggest that default constructors shouldn't do anything that can throw. If the default constructor is allowed to throw, other operations relying on creating default constructed objects may also throw.
+The C++ Core Guidelines suggest that default constructors shouldn't do anything that can throw. When the default constructor can throw, all code that rely on a properly instantiated object may also throw.
 
 ## Remarks
 
diff --git a/docs/code-quality/c26800.md b/docs/code-quality/c26800.md
@@ -11,10 +11,10 @@ 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're 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 is passed to a function as rvalue reference. There are some legitimate exceptions for 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"
+- Functions with the following case-insensitive substring in their name: "clear", "clean", "reset", "free", "destroy", "release", "dealloc", "assign"
 - Overloaded assignment operators, destructor
 
 This check respects the `std::swap` operation:
