More acrolinx suggestions.

Author: Xazax-hun

docs/code-quality/c26441.md

@@ -19,7 +19,7 @@ The standard library provides locks to help control concurrent access to resourc
 
 This diagnostic only analyzes the standard lock types `std::scoped_lock`, `std::unique_lock`, and `std::lock_guard`. Warning [C26444](c26444.md) covers other unnamed RAII types.
 
-The analyzer only analyzes simple calls to constructors. More complex initializer expressions may lead to inaccurate results in the form of missed warnings. The analyzer ignores locks passed as arguments to function calls or returned from function calls. It is unable to determine if those locks are deliberately trying to protect that function call or if their [lifetime should be extended](https://abseil.io/tips/107). To provide similar protection for types returned by a function call, annotate them with `[[nodiscard]]`. You can also annotate constructors with `[[nodiscard]]` to avoid unnamed objects of that type:
+The analyzer only analyzes simple calls to constructors. More complex initializer expressions may lead to inaccurate results in the form of missed warnings. The analyzer ignores locks passed as arguments to function calls or returned from function calls. It's unable to determine if those locks are deliberately trying to protect that function call or if their [lifetime should be extended](https://abseil.io/tips/107). To provide similar protection for types returned by a function call, annotate them with `[[nodiscard]]`. You can also annotate constructors with `[[nodiscard]]` to avoid unnamed objects of that type:
 
 ```cpp
 struct X { [[nodiscard]] X(); };
@@ -35,7 +35,7 @@ Code analysis name: `NO_UNNAMED_GUARDS`
 
 ## Example
 
-In this example the name of the scoped lock is missing.
+In this example, the name of the scoped lock is missing.
 
 ```cpp
 void print_diagnostic(std::string_view text)