PEP 622: Fix Typos (#1457)

pep-0543.rst

@@ -1195,7 +1195,7 @@ Errors
 ~~~~~~
 
 This module would define four base classes for use with error handling. Unlike
-many of the the other classes defined here, these classes are not abstract, as
+many of the other classes defined here, these classes are not abstract, as
 they have no behaviour. They exist simply to signal certain common behaviours.
 Backends should subclass these exceptions in their own packages, but needn't
 define any behaviour for them.

pep-0550.rst

@@ -1129,7 +1129,7 @@ This allows the values of context variables to be properly garbage
 collected.
 
 This generic caching approach is similar to what the current C
-implementation of ``decimal`` does to cache the the current decimal
+implementation of ``decimal`` does to cache the current decimal
 context, and has similar performance characteristics.
 
 

pep-0553.rst

@@ -83,7 +83,7 @@ and it can be set to a different function to change the debugger that
 ``sys.breakpointhook()`` so that you can always easily reset
 ``sys.breakpointhook()`` to the default value (e.g. by doing
 ``sys.breakpointhook = sys.__breakpointhook__``).  This is exactly the same as
-how the the existing ``sys.displayhook()`` / ``sys.__displayhook__`` and
+how the existing ``sys.displayhook()`` / ``sys.__displayhook__`` and
 ``sys.excepthook()`` / ``sys.__excepthook__`` work [hooks]_.
 
 The signature of the built-in is ``breakpoint(*args, **kws)``.  The positional

pep-0614.rst

@@ -164,7 +164,7 @@ clear without imposing further restrictions and grammar complications.
 Named Expressions *Need Not* Be Parenthesized
 '''''''''''''''''''''''''''''''''''''''''''''
 
-Here, the the choice of syntax is unambiguous.  :pep:`572` explains
+Here, the choice of syntax is unambiguous.  :pep:`572` explains
 why it requires parentheses around top-level expression statements:
 
     This rule is included to simplify the choice for the user between

pep-0622.rst

@@ -428,7 +428,7 @@ Combining multiple patterns
 ---------------------------
 
 Multiple alternative patterns can be combined into one using ``|``. This means
-the the whole pattern matches if at least one alternative matches.
+the whole pattern matches if at least one alternative matches.
 Alternatives are tried from left to right and have short-circuit property,
 subsequent patterns are not tried if one matched. Examples::
 

pep-8013.rst

@@ -214,11 +214,11 @@ A vote of no confidence proceeds as follows:
 * if no nominator or seconder is available, no further action is
   taken
 * voting opens immediately
-* each core developer may add a +1 vote (remove the the CoA member) or
-  a -1 vote (keep the the CoA member) by modifying a document in a
+* each core developer may add a +1 vote (remove the CoA member) or
+  a -1 vote (keep the CoA member) by modifying a document in a
   private github repository
 * after seven days, voting closes
-* if +1 votes exceed -1 votes, the the CoA member is removed from
+* if +1 votes exceed -1 votes, the CoA member is removed from
   python-committers and any nominated PEPs are reverted
 * if requested by the remaining members of the CoA, or if only one
   member of the CoA remains, a new election to replace the removed