Fix duplicated words in Draft and Active PEPs

peps/pep-0001.rst

@@ -277,7 +277,7 @@ to provide a central place to discuss and review its contents, and the
 PEP should be updated so that the ``Discussions-To`` header links to it.
 
 The PEP authors (or sponsor, if applicable) may select any reasonable venue
-for the discussion, so long as the the following criteria are met:
+for the discussion, so long as the following criteria are met:
 
 * The forum is appropriate to the PEP's topic.
 * The thread is publicly available on the web so that all interested parties
@@ -358,7 +358,7 @@ The term "PEP-Delegate" is used under the Steering Council governance model
 for the PEP's designated decision maker,
 who is recorded in the "PEP-Delegate" field in the PEP's header.
 The term "BDFL-Delegate" is a deprecated alias for PEP-Delegate, a legacy of
-the time when when Python was led by `a BDFL <Python's BDFL_>`_.
+the time when Python was led by `a BDFL <Python's BDFL_>`_.
 Any legacy references to "BDFL-Delegate" should be treated as equivalent to
 "PEP-Delegate".
 

peps/pep-0653.rst

@@ -438,7 +438,7 @@ translates to::
 Non-conforming special attributes
 '''''''''''''''''''''''''''''''''
 
-All classes should ensure that the the values of ``__match_container__``, ``__match_class__``
+All classes should ensure that the values of ``__match_container__``, ``__match_class__``
 and ``__match_args__`` follow the specification.
 Therefore, implementations can assume, without checking, that the following are true::
 

peps/pep-0720.rst

@@ -156,7 +156,7 @@ the target system is the same as where the build is occurring, so introspection
 is usually used to guide the build.
 
 In this section, we try to document most of the ways this is accomplished. It
-should give a decent overview of of environment details that are required by
+should give a decent overview of environment details that are required by
 build systems.
 
 .. list-table::

peps/pep-0776.rst

@@ -472,7 +472,7 @@ and it is in use in Pyodide.
 
 Eventually, we hope to implement stack-switching-based signals so that it is
 possible to use signals in the main thread of node and the browser, as well as
-in in web pages that are not served with the shared memory headers. We will need
+in web pages that are not served with the shared memory headers. We will need
 to keep the shared memory based approach as well, both for backwards
 compatibility and because it is more efficient when it is possible. However,
 this is out of scope for this PEP.

peps/pep-0786.rst

@@ -179,7 +179,7 @@ integers in two's complement. This leads us to a couple of alternative formulati
 of formatting negative numbers.
 
 Observe that one can always extend a signed number's binary representation by
-extending the the leading digit as a prefix:
+extending the leading digit as a prefix:
 
 .. code-block:: text
 

peps/pep-0818.rst

@@ -744,7 +744,7 @@ The Python object ``jstypes.code.run_js`` is defined as follows:
 
 Unlike ``run_js``, the JavaScript object ``makePythonFunction`` is strictly for
 the sake of our pseudocode and will not be included as part of the API. We
-define define ``makePythonFunction`` as follows:
+define ``makePythonFunction`` as follows:
 
 .. code-block:: python
 

peps/pep-0824.rst

@@ -572,7 +572,7 @@ coalescing" operators, two options for the precedence emerge.
 
 1. A precedence between binary and comparison operators as seen in
    both Swift [#swift_precedence]_ and Kotlin [#kotlin_precedence]_
-   for their their "Nil-Coalescing" and "Elvis" operators respectively.
+   for their "Nil-Coalescing" and "Elvis" operators respectively.
 
 2. A precedence between the logical OR and conditional / ternary
    operators, see C# [#csharp_precedence]_, Dart [#dart_precedence]_ and