[clang-tidy] Tidy up spelling, grammar, and inconsistencies in documentation (NFC)

Differential Revision: https://reviews.llvm.org/D112356

Author: salman-javed-nz

clang-tools-extra/docs/clang-tidy/Contributing.rst

@@ -131,8 +131,8 @@ are located in subdirectories of `clang-tidy/
 <https://github.com/llvm/llvm-project/tree/main/clang-tools-extra/clang-tidy/>`_
 and contain checks targeting a certain aspect of code quality (performance,
 readability, etc.), certain coding style or standard (Google, LLVM, CERT, etc.)
-or a widely used API (e.g. MPI). Their names are same as user-facing check
-groups names described :ref:`above <checks-groups-table>`.
+or a widely used API (e.g. MPI). Their names are the same as the user-facing
+check group names described :ref:`above <checks-groups-table>`.
 
 After choosing the module and the name for the check, run the
 ``clang-tidy/add_new_check.py`` script to create the skeleton of the check and
@@ -441,8 +441,8 @@ warnings and errors. The script provides multiple configuration flags.
 * To restrict the files examined you can provide one or more regex arguments
   that the file names are matched against.
   ``run-clang-tidy.py clang-tidy/.*Check\.cpp`` will only analyze clang-tidy
-  checks. It may also be necessary to restrict the header files warnings are
-  displayed from using the ``-header-filter`` flag. It has the same behavior
+  checks. It may also be necessary to restrict the header files that warnings
+  are displayed from using the ``-header-filter`` flag. It has the same behavior
   as the corresponding :program:`clang-tidy` flag.
 
 * To apply suggested fixes ``-fix`` can be passed as an argument. This gathers
@@ -475,7 +475,7 @@ It can also store that data as JSON files for further processing. Example output
 
 .. code-block:: console
 
-  $ clang-tidy -enable-check-profile -store-check-profile=.  -checks=-*,readability-function-size source.cpp
+  $ clang-tidy -enable-check-profile -store-check-profile=. -checks=-*,readability-function-size source.cpp
   $ # Note that there won't be timings table printed to the console.
   $ ls /tmp/out/
   20180516161318717446360-source.cpp.json

clang-tools-extra/docs/clang-tidy/checks/abseil-duration-conversion-cast.rst

@@ -27,5 +27,5 @@ Examples:
 
 
 Note: In the second example, the suggested fix could yield a different result,
-as the conversion to integer could truncate.  In practice, this is very rare,
+as the conversion to integer could truncate. In practice, this is very rare,
 and you should use ``absl::Trunc`` to perform this operation explicitly instead.

clang-tools-extra/docs/clang-tidy/checks/abseil-no-internal-dependencies.rst

@@ -5,7 +5,7 @@ abseil-no-internal-dependencies
 
 Warns if code using Abseil depends on internal details. If something is in a
 namespace that includes the word "internal", code is not allowed to depend upon
-it because it’s an implementation detail. They cannot friend it, include it,
+it because it's an implementation detail. They cannot friend it, include it,
 you mention it or refer to it in any way. Doing so violates Abseil's
 compatibility guidelines and may result in breakage. See
 https://abseil.io/about/compatibility for more information.

clang-tools-extra/docs/clang-tidy/checks/abseil-string-find-str-contains.rst

@@ -10,7 +10,7 @@ This improves readability and reduces the likelihood of accidentally mixing
 ``find()`` and ``npos`` from different string-like types.
 
 By default, "string-like types" includes ``::std::basic_string``,
-``::std::basic_string_view``, and ``::absl::string_view``.  See the
+``::std::basic_string_view``, and ``::absl::string_view``. See the
 StringLikeClasses option to change this.
 
 .. code-block:: c++

clang-tools-extra/docs/clang-tidy/checks/android-cloexec-open.rst

@@ -4,7 +4,7 @@ android-cloexec-open
 ====================
 
 A common source of security bugs is code that opens a file without using the
-``O_CLOEXEC`` flag.  Without that flag, an opened sensitive file would remain
+``O_CLOEXEC`` flag. Without that flag, an opened sensitive file would remain
 open across a fork+exec to a lower-privileged SELinux domain, leaking that
 sensitive data. Open-like functions including ``open()``, ``openat()``, and
 ``open64()`` should include ``O_CLOEXEC`` in their flags argument.

clang-tools-extra/docs/clang-tidy/checks/android-cloexec-pipe2.rst

@@ -3,7 +3,7 @@
 android-cloexec-pipe2
 =====================
 
-This checks ensures that pipe2() is called with the O_CLOEXEC flag. The check also
+This check ensures that pipe2() is called with the O_CLOEXEC flag. The check also
 adds the O_CLOEXEC flag that marks the file descriptor to be closed in child processes.
 Without this flag a sensitive file descriptor can be leaked to a child process,
 potentially into a lower-privileged SELinux domain.

clang-tools-extra/docs/clang-tidy/checks/boost-use-to-string.rst

@@ -8,7 +8,7 @@ This check finds conversion from integer type like ``int`` to ``std::string`` or
 ``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++

clang-tools-extra/docs/clang-tidy/checks/bugprone-branch-clone.rst

@@ -87,4 +87,4 @@ Unlike if statements, the check does not detect chains of conditional
 operators.
 
 Note: This check also reports situations where branches become identical only
-after preprocession.
+after preprocessing.

clang-tools-extra/docs/clang-tidy/checks/bugprone-easily-swappable-parameters.rst

@@ -116,7 +116,7 @@ noisiness.
     The value is a `;`-separated list of names.
     To ignore unnamed parameters, add `""` to the list verbatim (not the
     empty string, but the two quotes, potentially escaped!).
-    **This options is case-sensitive!**
+    **This option is case-sensitive!**
 
     By default, the following parameter names, and their Uppercase-initial
     variants are ignored:
@@ -154,7 +154,7 @@ noisiness.
       ``a < b``.
     * The parameters are further passed to the same function to the same
       parameter of that function, of the same overload.
-      E.g. ``f(a, 1)`` and ``f(b, 2)`` to some ``f(T, int)``.
+      e.g. ``f(a, 1)`` and ``f(b, 2)`` to some ``f(T, int)``.
 
       .. note::
 
@@ -202,7 +202,7 @@ an argument list, and C++ template instantiations.
 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:
 
@@ -241,7 +241,7 @@ not diagnosed.
     void exact(typename Vector<T>::element_type A,
                typename Vector<T>::element_type B) { /* ... */ }
 
-    // Skipped: The two parameters are both 'T' but we can not prove this
+    // Skipped: The two parameters are both 'T' but we cannot prove this
     // without actually instantiating.
     template <typename T>
     void falseNegative(T A, typename Vector<T>::element_type B) { /* ... */ }

clang-tools-extra/docs/clang-tidy/checks/bugprone-implicit-widening-of-multiplication-result.rst

@@ -8,7 +8,7 @@ widened, and suggests (with fix-it) to either silence the code by making
 widening explicit, or to perform the multiplication in a wider type,
 to avoid the widening afterwards.
 
-This is mainly useful when operating on a very large buffers.
+This is mainly useful when operating on very large buffers.
 For example, consider:
 
 .. code-block:: c++
@@ -22,7 +22,7 @@ For example, consider:
     }
   }
 
-This is fine in general, but iff ``width * height`` overflows,
+This is fine in general, but if ``width * height`` overflows,
 you end up wrapping back to the beginning of ``base``
 instead of processing the entire requested buffer.