diff --git a/clang-tools-extra/docs/clang-tidy/checks/bugprone-too-small-loop-variable.rst b/clang-tools-extra/docs/clang-tidy/checks/bugprone-too-small-loop-variable.rst
--- a/clang-tools-extra/docs/clang-tidy/checks/bugprone-too-small-loop-variable.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/bugprone-too-small-loop-variable.rst
@@ -26,7 +26,7 @@
   }
 
 This algorithm works for small amount of objects, but will lead to freeze for a
-a larger user input.
+larger user input.
 
 .. option:: MagnitudeBitsUpperLimit
 
diff --git a/clang-tools-extra/docs/clang-tidy/checks/modernize-avoid-bind.rst b/clang-tools-extra/docs/clang-tidy/checks/modernize-avoid-bind.rst
--- a/clang-tools-extra/docs/clang-tidy/checks/modernize-avoid-bind.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/modernize-avoid-bind.rst
@@ -72,7 +72,7 @@
     return ignore_args(3, 3);
   }
 
-which will *not* compile, since the lambda does not contain an ``operator()`` that
+which will *not* compile, since the lambda does not contain an ``operator()``
 that accepts 2 arguments. With permissive parameter list, it instead generates
 
 .. code-block:: c++
diff --git a/clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst b/clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
--- a/clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst
@@ -138,7 +138,7 @@
 
    Specify the function used to reverse an iterator pair, the function should 
    accept a class with ``rbegin`` and ``rend`` methods and return a 
-   class with ``begin`` and ``end`` methods methods that call the ``rbegin`` and
+   class with ``begin`` and ``end`` methods that call the ``rbegin`` and
    ``rend`` methods respectively. Common examples are ``ranges::reverse_view``
    and ``llvm::reverse``.
    Default value is an empty string.
diff --git a/clang-tools-extra/docs/clang-tidy/checks/objc-nsinvocation-argument-lifetime.rst b/clang-tools-extra/docs/clang-tidy/checks/objc-nsinvocation-argument-lifetime.rst
--- a/clang-tools-extra/docs/clang-tidy/checks/objc-nsinvocation-argument-lifetime.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/objc-nsinvocation-argument-lifetime.rst
@@ -7,7 +7,7 @@
 argument object lifetimes. When passing Objective-C objects as parameters
 to the ``NSInvocation`` methods ``getArgument:atIndex:`` and
 ``getReturnValue:``, the values are copied by value into the argument pointer,
-which leads to to incorrect releasing behavior if the object pointers are
+which leads to incorrect releasing behavior if the object pointers are
 not declared ``__unsafe_unretained``.
 
 For code:
diff --git a/clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst b/clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
--- a/clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/openmp-exception-escape.rst
@@ -8,7 +8,7 @@
 
 As per the OpenMP specification, a structured block is an executable statement,
 possibly compound, with a single entry at the top and a single exit at the
-bottom. Which means, ``throw`` may not be used to to 'exit' out of 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.