diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
index 14292cb..6967bd1 100644
--- a/Doc/c-api/init.rst
+++ b/Doc/c-api/init.rst
@@ -802,7 +802,7 @@
 Asynchronous Notifications
 ==========================
 
-A mechanism is provided to make asynchronous notifications to the the main
+A mechanism is provided to make asynchronous notifications to the main
 interpreter thread.  These notifications take the form of a function
 pointer and a void argument.
 
diff --git a/Doc/howto/cporting.rst b/Doc/howto/cporting.rst
index 3451f5c..9b66650 100644
--- a/Doc/howto/cporting.rst
+++ b/Doc/howto/cporting.rst
@@ -96,7 +96,7 @@
 Python level, but actually corresponds to 2.x's :func:`long` type.  In the
 C-API, ``PyInt_*`` functions are replaced by their ``PyLong_*`` neighbors.  The
 best course of action here is using the ``PyInt_*`` functions aliased to
-``PyLong_*`` found in :file:`intobject.h`.  The the abstract ``PyNumber_*`` APIs
+``PyLong_*`` found in :file:`intobject.h`.  The abstract ``PyNumber_*`` APIs
 can also be used in some cases. ::
 
    #include "Python.h"
diff --git a/Doc/library/abc.rst b/Doc/library/abc.rst
index d591daa..9f70b02 100644
--- a/Doc/library/abc.rst
+++ b/Doc/library/abc.rst
@@ -134,7 +134,7 @@
    A class that has a metaclass derived from :class:`ABCMeta`
    cannot be instantiated unless all of its abstract methods and
    properties are overridden.
-   The abstract methods can be called using any of the the normal 'super' call
+   The abstract methods can be called using any of the normal 'super' call
    mechanisms.
 
    Dynamically adding abstract methods to a class, or attempting to modify the
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index a36836e..8abf146 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -1857,7 +1857,7 @@
 any :class:`~multiprocessing.Process` object that the current process creates.
 This means that (by default) all processes of a multi-process program will share
 a single authentication key which can be used when setting up connections
-between the themselves.
+between themselves.
 
 Suitable authentication keys can also be generated by using :func:`os.urandom`.
 
diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst
index 700146b..cfc219c 100644
--- a/Doc/library/pdb.rst
+++ b/Doc/library/pdb.rst
@@ -268,7 +268,7 @@
    full speed, only stopping at the next line in the current function.)
 
 unt(il)
-   Continue execution until the line with the the line number greater than the
+   Continue execution until the line with the line number greater than the
    current one is reached or when returning from current frame.
 
    .. versionadded:: 2.6
diff --git a/Doc/library/ssl.rst b/Doc/library/ssl.rst
index 30f1fea..1804fcf 100644
--- a/Doc/library/ssl.rst
+++ b/Doc/library/ssl.rst
@@ -261,7 +261,7 @@
    If there is no certificate for the peer on the other end of the
    connection, returns ``None``.
 
-   If the the parameter ``binary_form`` is :const:`False`, and a
+   If the parameter ``binary_form`` is :const:`False`, and a
    certificate was received from the peer, this method returns a
    :class:`dict` instance.  If the certificate was not validated, the
    dict is empty.  If the certificate was validated, it returns a dict
diff --git a/Doc/library/ttk.rst b/Doc/library/ttk.rst
index e0ca59a..f38664e 100644
--- a/Doc/library/ttk.rst
+++ b/Doc/library/ttk.rst
@@ -1381,7 +1381,7 @@
 options/values are:
 
  * side: whichside
-    Specifies which side of the cavity to place the the element; one of
+    Specifies which side of the cavity to place the element; one of
     top, right, bottom or left. If omitted, the element occupies the
     entire cavity.
 
diff --git a/Doc/whatsnew/2.6.rst b/Doc/whatsnew/2.6.rst
index 150d54f..1ffad38 100644
--- a/Doc/whatsnew/2.6.rst
+++ b/Doc/whatsnew/2.6.rst
@@ -1672,7 +1672,7 @@
   :attr:`__self__`, and :attr:`im_func` is also available as :attr:`__func__`.
   The old names are still supported in Python 2.6, but are gone in 3.0.
 
-* An obscure change: when you use the the :func:`locals` function inside a
+* An obscure change: when you use the :func:`locals` function inside a
   :keyword:`class` statement, the resulting dictionary no longer returns free
   variables.  (Free variables, in this case, are variables referenced in the
   :keyword:`class` statement  that aren't attributes of the class.)