Address review comments.

Author: Xazax-hun

docs/code-quality/c26441.md

@@ -19,7 +19,17 @@ 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 they should be extended. 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 ignores locks created as temporaries but assigned to named references to extend their lifetime.
+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 they should be extended. 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(); };
+
+void f() {
+    X{}; // warning C4834
+}
+```
+
+ The analyzer ignores locks created as temporaries but assigned to named references to extend their lifetime.
 
 Code analysis name: `NO_UNNAMED_GUARDS`
 

docs/code-quality/c26444.md

@@ -13,12 +13,11 @@ helpviewer_keywords: ["C26444"]
 
 [ES.84: Don't (try to) declare a local variable with no name](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-noname)
 
-Unnamed temporary objects with nontrivial behavior may point to either (a) inefficient code that allocates and immediately throws away resources or (b) to the code that unintentionally ignores nonprimitive data. Sometimes it may also indicate plainly wrong declaration.
+An unnamed variable declaration will create a temporary object that is discarded at the end of the statement. Such temporary objects with nontrivial behavior may point to either (a) inefficient code that allocates and immediately throws away resources or (b) to the code that unintentionally ignores nonprimitive data. Sometimes it may also indicate plainly wrong declaration.
 
 ## Remarks
 
-- This rule detects types with nontrivial destructors. Keep in mind that destructors can be compiler generated.
-- The warning can flag code that invokes a nontrivial constructor of a RAII type.
+- This rule detects types with a hand-written destructor or a compiler-generated destructor that transitively calls a hand-written destructor.
 - The logic skips temporaries if they're used in higher-level expressions. One example is temporaries that are passed as arguments or used to invoke a function.
 
 Code analysis name: `NO_UNNAMED_RAII_OBJECTS`