[clang-tools-extra] [clang-tidy] Minor documentation wording for performance-noexcept-move-constructor (PR #157384)

[Nicolas van Kempen via cfe-commits]

https://github.com/nicovank created https://github.com/llvm/llvm-project/pull/157384


Fix #157343.


>From 9d425a009d17385cc9bf1b9649084e68fde65c9f Mon Sep 17 00:00:00 2001
From: Nicolas van Kempen <nvankemp at gmail.com>
Date: Mon, 8 Sep 2025 00:44:15 -0400
Subject: [PATCH] [clang-tidy] Minor documentation wording for
 performance-noexcept-move-constructor

Fix #157343.
---
 .../clang-tidy/checks/performance/noexcept-move-constructor.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst b/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst
index 05f1d85f1af5a..eb605c5b0a53b 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst
@@ -9,5 +9,5 @@ marked with ``noexcept`` or marked with ``noexcept(expr)`` where ``expr``
 evaluates to ``false`` (but is not a ``false`` literal itself).
 
 Move constructors of all the types used with STL containers, for example,
-need to be declared ``noexcept``. Otherwise STL will choose copy constructors
+should be declared ``noexcept``. Otherwise STL may choose copy constructors
 instead. The same is valid for move assignment operations.