salman-javed-nz updated this revision to Diff 381706.
salman-javed-nz added a comment.
Standardize to US English spelling for words such as "behavior" and
"specialization".
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D112356/new/
https://reviews.llvm.org/D112356
Files:
clang-tools-extra/docs/clang-tidy/checks/boost-use-to-string.rst
clang-tools-extra/docs/clang-tidy/checks/bugprone-easily-swappable-parameters.rst
clang-tools-extra/docs/clang-tidy/checks/bugprone-macro-parentheses.rst
clang-tools-extra/docs/clang-tidy/checks/bugprone-not-null-terminated-result.rst
clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-init-variables.rst
clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-virtual-class-destructor.rst
clang-tools-extra/docs/clang-tidy/checks/hicpp-signed-bitwise.rst
clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
clang-tools-extra/docs/clang-tidy/checks/modernize-use-default-member-init.rst
clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
clang-tools-extra/docs/clang-tidy/checks/readability-redundant-declaration.rst
clang-tools-extra/docs/clang-tidy/checks/readability-suspicious-call-argument.rst
Index: clang-tools-extra/docs/clang-tidy/checks/readability-suspicious-call-argument.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/readability-suspicious-call-argument.rst
+++ clang-tools-extra/docs/clang-tidy/checks/readability-suspicious-call-argument.rst
@@ -51,7 +51,7 @@
foo(b, src);
-The abbreviations to recognise can be configured with the
+The abbreviations to recognize can be configured with the
:ref:`Abbreviations<opt_Abbreviations>` check option.
This heuristic is case-insensitive.
Index: clang-tools-extra/docs/clang-tidy/checks/readability-redundant-declaration.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/readability-redundant-declaration.rst
+++ clang-tools-extra/docs/clang-tidy/checks/readability-redundant-declaration.rst
@@ -16,7 +16,7 @@
extern int X;
-Such redundant declarations can be removed without changing program behaviour.
+Such redundant declarations can be removed without changing program behavior.
They can for instance be unintentional left overs from previous refactorings
when code has been moved around. Having redundant declarations could in worst
case mean that there are typos in the code that cause bugs.
Index: clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
+++ clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
@@ -10,7 +10,7 @@
possibly compound, with a single entry at the top and a single exit at the
bottom. Which means, ``throw`` may not be used to 'exit' out of the
structured block. If an exception is not caught in the same structured block
-it was thrown in, the behaviour is undefined.
+it was thrown in, the behavior is undefined.
FIXME: this check does not model SEH, ``setjmp``/``longjmp``.
Index: clang-tools-extra/docs/clang-tidy/checks/modernize-use-default-member-init.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/modernize-use-default-member-init.rst
+++ clang-tools-extra/docs/clang-tidy/checks/modernize-use-default-member-init.rst
@@ -36,7 +36,7 @@
.. option:: UseAssignment
- If this option is set to `true` (default is `false`), the check will initialise
+ If this option is set to `true` (default is `false`), the check will initialize
members with an assignment. For example:
.. code-block:: c++
Index: clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
+++ clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
@@ -165,7 +165,7 @@
There are certain situations where the tool may erroneously perform
transformations that remove information and change semantics. Users of the tool
-should be aware of the behaviour and limitations of the check outlined by
+should be aware of the behavior and limitations of the check outlined by
the cases below.
Comments inside loop headers
Index: clang-tools-extra/docs/clang-tidy/checks/hicpp-signed-bitwise.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/hicpp-signed-bitwise.rst
+++ clang-tools-extra/docs/clang-tidy/checks/hicpp-signed-bitwise.rst
@@ -4,7 +4,7 @@
====================
Finds uses of bitwise operations on signed integer types, which may lead to
-undefined or implementation defined behaviour.
+undefined or implementation defined behavior.
The according rule is defined in the `High Integrity C++ Standard, Section 5.6.1 <http://www.codingstandard.com/section/5-6-shift-operators/>`_.
Index: clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-virtual-class-destructor.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-virtual-class-destructor.rst
+++ clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-virtual-class-destructor.rst
@@ -5,7 +5,7 @@
Finds virtual classes whose destructor is neither public and virtual
nor protected and non-virtual. A virtual class's destructor should be specified
-in one of these ways to prevent undefined behaviour.
+in one of these ways to prevent undefined behavior.
This check implements
`C.35 <http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rc-dtor-virtual>`_
Index: clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-init-variables.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-init-variables.rst
+++ clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-init-variables.rst
@@ -4,7 +4,7 @@
================================
Checks whether there are local variables that are declared without an initial
-value. These may lead to unexpected behaviour if there is a code path that reads
+value. These may lead to unexpected behavior if there is a code path that reads
the variable before assigning to it.
Only integers, booleans, floats, doubles and pointers are checked. The fix
Index: clang-tools-extra/docs/clang-tidy/checks/bugprone-not-null-terminated-result.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/bugprone-not-null-terminated-result.rst
+++ clang-tools-extra/docs/clang-tidy/checks/bugprone-not-null-terminated-result.rst
@@ -6,7 +6,7 @@
Finds function calls where it is possible to cause a not null-terminated result.
Usually the proper length of a string is ``strlen(src) + 1`` or equal length of
this expression, because the null terminator needs an extra space. Without the
-null terminator it can result in undefined behaviour when the string is read.
+null terminator it can result in undefined behavior when the string is read.
The following and their respective ``wchar_t`` based functions are checked:
@@ -61,7 +61,7 @@
obtain the capacity of the destination array then the new function could be
the safe version (ending with ``cpy_s``).
-- If the new function is could be safe version and C++ files are analysed and
+- If the new function is could be safe version and C++ files are analyzed and
the destination array is plain ``char``/``wchar_t`` without ``un/signed`` then
the length of the destination array can be omitted.
Index: clang-tools-extra/docs/clang-tidy/checks/bugprone-macro-parentheses.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/bugprone-macro-parentheses.rst
+++ clang-tools-extra/docs/clang-tidy/checks/bugprone-macro-parentheses.rst
@@ -4,10 +4,10 @@
==========================
-Finds macros that can have unexpected behaviour due to missing parentheses.
+Finds macros that can have unexpected behavior due to missing parentheses.
Macros are expanded by the preprocessor as-is. As a result, there can be
-unexpected behaviour; operators may be evaluated in unexpected order and
+unexpected behavior; operators may be evaluated in unexpected order and
unary operators may become binary operators, etc.
When the replacement list has an expression, it is recommended to surround
Index: clang-tools-extra/docs/clang-tidy/checks/bugprone-easily-swappable-parameters.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/bugprone-easily-swappable-parameters.rst
+++ clang-tools-extra/docs/clang-tidy/checks/bugprone-easily-swappable-parameters.rst
@@ -202,7 +202,7 @@
Most of these cases, which are otherwise swappable from a caller's standpoint,
have no way of getting "fixed" at the definition point.
In the case of C++ templates, only primary template definitions and explicit
-specialisations are matched and analysed.
+specializations are matched and analyzed.
None of the following cases produce a diagnostic:
Index: clang-tools-extra/docs/clang-tidy/checks/boost-use-to-string.rst
===================================================================
--- clang-tools-extra/docs/clang-tidy/checks/boost-use-to-string.rst
+++ clang-tools-extra/docs/clang-tidy/checks/boost-use-to-string.rst
@@ -8,7 +8,7 @@
``std::to_string`` and ``std::to_wstring``.
It doesn't replace conversion from floating points despite the ``to_string``
-overloads, because it would change the behaviour.
+overloads, because it would change the behavior.
.. code-block:: c++
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
