Fix various typos, spelling and grammar errors

Errors detected using Topy (https://github.com/intgr/topy), all changes
verified by hand.

pep-0004.txt

@@ -197,7 +197,7 @@ Deprecated modules
                    Removed from the library reference in Python 2.5.
 
     Module name:   mpz
-    Rationale:     Third-party packages provide similiar features
+    Rationale:     Third-party packages provide similar features
                    and wrap more of GMP's API.
     Date:          10-Aug-2004
     Documentation: This module has been documented as obsolete since

pep-0007.txt

@@ -165,7 +165,7 @@ Documentation Strings
       #define PyDoc_STRVAR(name, str) PyDoc_VAR(name) = PyDoc_STR(str)
       #endif
 
-* The first line of each fuction docstring should be a "signature
+* The first line of each function docstring should be a "signature
   line" that gives a brief synopsis of the arguments and return value.
   For example::
 

pep-0008.txt

@@ -1298,7 +1298,7 @@ annotations are changing.
   are now encouraged.  For example, marking up a large third party
   library or application with PEP 484 style type annotations,
   reviewing how easy it was to add those annotations, and observing
-  whether their presence increases code understandabilty.
+  whether their presence increases code understandability.
 
 - The Python standard library should be conservative in adopting such
   annotations, but their use is allowed for new code and for big

pep-0100.txt

@@ -106,7 +106,7 @@ Unicode Default Encoding
     the encoding defined by the current locale.  The locale module is
     used to extract the encoding from the locale default settings
     defined by the OS environment (see locale.py).  If the encoding
-    cannot be determined, is unkown or unsupported, the code defaults
+    cannot be determined, is unknown or unsupported, the code defaults
     to setting the <default encoding> to 'ascii'.  To enable this
     code, edit the site.py file or place the appropriate code into the
     sitecustomize.py module of your Python installation.

pep-0101.txt

@@ -474,7 +474,7 @@ How to Make A Release
   permissions.  (Or ask Ewa, who coordinated the effort for the new newbsite
   with RevSys.)
 
-  XXX This is completely out of date for Django based python.org.
+  XXX This is completely out of date for Django-based python.org.
 
   This page will probably come in handy:
 

pep-0103.txt

@@ -440,7 +440,7 @@ Read `how to recover from upstream rebase
 <https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase>`_.
 It is in ``git help rebase``.
 
-On the other hand don't be too afraid about commit editing. You can
+On the other hand, don't be too afraid about commit editing. You can
 safely edit, reorder, remove, combine and split commits that haven't
 been pushed yet. You can even push commits to your own (backup) repo,
 edit them later and force-push edited commits to replace what have

pep-0201.txt

@@ -233,7 +233,7 @@ Subsequent Change to zip()
         date, rain, high, low = zip(*csv.reader(file("weather.csv")))
 
     rearranges columnar data so that each field is collected into
-    individual tuples for straight-forward looping and summarization:
+    individual tuples for straightforward looping and summarization:
 
         print "Total rainfall", sum(rain)
 

pep-0204.txt

@@ -274,7 +274,7 @@ Rejection
     proposal altogether. The new syntax and its intentions were deemed
     not obvious enough.
 
-    [ TBD: Guido, ammend/confirm this, please. Preferably both; this
+    [ TBD: Guido, amend/confirm this, please. Preferably both; this
       is a PEP, it should contain *all* the reasons for rejection
       and/or reconsideration, for future reference. ]
 

pep-0205.txt

@@ -123,7 +123,7 @@ Aspects of the Solution Space
     operations on the referents and catching some special exception
     raised when an invalid weak reference is used.
 
-    However, a number of users favor the proxy appoach simply because
+    However, a number of users favor the proxy approach simply because
     the weak reference looks so much like the original object.
 
 
@@ -422,7 +422,7 @@ Appendix -- Dianne Hackborn's vref proposal (1995)
     return a type error, until they can be fixed.
 
     Finally, there are some other additional capabilities that this
-    system could provide.  One that seems particularily interesting to
+    system could provide.  One that seems particularly interesting to
     me involves allowing the Python programmer to add "destructor"
     function to a vref -- this Python function would be called
     immediately prior to the referenced object being deallocated,

pep-0209.txt

@@ -113,7 +113,7 @@ Proposal
         d.  Record access
 
         In some fields of science, data is stored in files as binary
-        records.  For example in astronomy, photon data is stored as a
+        records.  For example, in astronomy, photon data is stored as a
         1 dimensional list of photons in order of arrival time.  These
         records or C-like structures contain information about the
         detected photon, such as its arrival time, its position on the
@@ -415,14 +415,14 @@ Open Issues
     3.  How is scalar coercion implemented?
 
     Python has fewer numeric types than Numeric which can cause
-    coercion problems.  For example when multiplying a Python scalar
+    coercion problems.  For example, when multiplying a Python scalar
     of type float and a Numeric array of type float, the Numeric array
     is converted to a double, since the Python float type is actually
     a double.  This is often not the desired behavior, since the
     Numeric array will be doubled in size which is likely to be
     annoying, particularly for very large arrays.  We prefer that the
     array type trumps the python type for the same type class, namely
-    integer, float, and complex.  Therefore an operation between a
+    integer, float, and complex.  Therefore, an operation between a
     Python integer and an Int16 (short) array will return an Int16
     array.  Whereas an operation between a Python float and an Int16
     array would return a Float64 (double) array.  Operations between
@@ -444,7 +444,7 @@ Open Issues
 
     There are two approaches to implementing records depending on your
     point-of-view.  The first is two divide arrays into separate
-    classes depending on the behavior of their types.  For example
+    classes depending on the behavior of their types.  For example,
     numeric arrays are one class, strings a second, and records a
     third, because the range and type of operations of each class
     differ.  As such, a record array is not a new type, but a

pep-0213.txt

@@ -15,7 +15,7 @@ Introduction
      It is possible (and even relatively common) in Python code and 
      in extension modules to "trap" when an instance's client code 
      attempts to set an attribute and execute code instead. In other 
-     words it is possible to allow users to use attribute assignment/
+     words, it is possible to allow users to use attribute assignment/
      retrieval/deletion syntax even though the underlying implementation 
      is doing some computation rather than directly modifying a
      binding.

pep-0216.txt

@@ -52,8 +52,8 @@ Python Docstring Goals
     a bit problematic, sometimes: for example, some are reluctant to have
     too long docstrings, because they do not want to take much space in
     the runtime. In addition, because of the current lack of tools, people
-    read objects' docstrings by "print"ing them, so a tendancy to make them
-    brief and free of markups has sprung up. This tendancy hinders writing
+    read objects' docstrings by "print"ing them, so a tendency to make them
+    brief and free of markups has sprung up. This tendency hinders writing
     better documentation-extraction tools, since it causes docstrings to
     contain little information, which is hard to parse.
 

pep-0217.txt

@@ -48,7 +48,7 @@ Solution
 
 Jython Issues
 
-    The method Py.printResult will be similarily changed.
+    The method Py.printResult will be similarly changed.
 
 
 Local Variables:

pep-0219.txt

@@ -53,7 +53,7 @@ Background
     coroutines and microthreads can be implemented in Python in a way
     that involves almost no overhead.  This PEP, therefor, offers a
     way for making Python able to realistically manage thousands of
-    separate "threads" of activity (vs. todays limit of perhaps dozens
+    separate "threads" of activity (vs. today's limit of perhaps dozens
     of separate threads of activity).
 
     Another justification for this PEP (explored in PEP 220) is that

pep-0221.txt

@@ -21,7 +21,7 @@ Introduction
 
 Rationale
 
-    This PEP proposes an extention of Python syntax regarding the
+    This PEP proposes an extension of Python syntax regarding the
     `import' and `from <module> import' statements.  These statements
     load in a module, and either bind that module to a local name, or
     binds objects from that module to a local name.  However, it is
@@ -81,7 +81,7 @@ Implementation details
     `global' directives.
 
     The special case of `from module import *' remains a special case,
-    in that it cannot accomodate an `as' clause, and that no STORE
+    in that it cannot accommodate an `as' clause, and that no STORE
     opcodes are generated; the objects imported are loaded directly
     into the local namespace. This also means that names imported in
     this fashion are always local, and do not follow the `global'
@@ -91,7 +91,7 @@ Implementation details
     generalize the expression given after the `as' clause.  Rather
     than a single name, it could be allowed to be any expression that
     yields a valid l-value; anything that can be assigned to.  The
-    change to accomodate this is minimal, as the patch[2] proves, and
+    change to accommodate this is minimal, as the patch[2] proves, and
     the resulting generalization allows a number of new constructs
     that run completely parallel with other Python assignment
     constructs. However, this idea has been rejected by Guido, as

pep-0225.txt

@@ -375,7 +375,7 @@ Semantics of new operators
        - whatever the decision is taken, codes using existing
          interfaces should not be broken for a very long time.
 
-    Therefore not much is lost, and much flexibility retained, if the
+    Therefore, not much is lost, and much flexibility retained, if the
     semantic flavors of these two sets of operators are not dictated
     by the core language.  The application packages are responsible
     for making the most suitable choice.  This is already the case for
@@ -502,7 +502,7 @@ Miscellaneous issues:
 
           a = b.i(1,2,-1,-2) * c.i(4,-2,3,-1)   # a_ijkl = b_ijmn c_lnkm
 
-      Therefore one objectwise multiplication is sufficient.
+      Therefore, one objectwise multiplication is sufficient.
 
     - Bitwise operators. 
 
@@ -723,7 +723,7 @@ Credits and archives
         http://www.python.org/pipermail/python-list/2000-July/
         http://www.python.org/pipermail/python-list/2000-August/
 
-    The names of contributers are too numerous to mention here,
+    The names of contributors are too numerous to mention here,
     suffice to say that a large proportion of ideas discussed here are
     not our own.
 

pep-0231.txt

@@ -332,7 +332,7 @@ Examples
         assert c.a is not a
 
 
-        # no acquisiton on _ names
+        # no acquisition on _ names
         class E(Implicit):
             _color = 'purple'
 

pep-0240.txt

@@ -31,7 +31,7 @@ Rationale
     Rational numbers are useful for exact and unsurprising arithmetic.
     They give the correct results people have been taught in various
     math classes.  Making the "obvious" non-integer type one with more
-    predictable semantics will surprise new programmers less then
+    predictable semantics will surprise new programmers less than
     using floating point numbers. As quite a few posts on c.l.py and
     on [email protected] have shown, people often get bit by strange
     semantics of floating point numbers: for example, round(0.98, 2)

pep-0245.txt

@@ -60,7 +60,7 @@ The Problem
       based on implementation introspection, but often that also
       fails.  For example, defining __getitem__ implies both a
       sequence and a mapping (the former with sequential, integer
-      keys).  There is no way for the developer to be explict about
+      keys).  There is no way for the developer to be explicit about
       which protocols the object intends to implement.
 
     - Python is limited, from the developer's point of view, by the
@@ -74,10 +74,10 @@ The Problem
 
     - Python's dynamic typing is very flexible and powerful, but it
       does not have the advantage of static typed languages that
-      provide type checking.  Static typed langauges provide you with
-      much more type saftey, but are often overly verbose because
+      provide type checking.  Static typed languages provide you with
+      much more type safety, but are often overly verbose because
       objects can only be generalized by common subclassing and used
-      specificly with casting (for example, in Java).
+      specifically with casting (for example, in Java).
 
     There are also a number of documentation problems that interfaces
     try to solve.
@@ -319,7 +319,7 @@ Interface Assertion
 
 Formal Interface Syntax
 
-    Python syntax is defined in a modified BNF grammer notation
+    Python syntax is defined in a modified BNF grammar notation
     described in the Python Reference Manual [8].  This section
     describes the proposed interface syntax using this grammar:
 

pep-0247.txt

@@ -68,7 +68,7 @@ Specification
         hashing object, measured in bytes.  If the hash has a variable
         output size, this output size must be chosen when the hashing
         object is created, and this attribute must contain the
-        selected size.  Therefore None is *not* a legal value for this
+        selected size.  Therefore, None is *not* a legal value for this
         attribute.
 
 

pep-0249.txt

@@ -944,7 +944,7 @@ render execution impossible.
 
 For these cases and in order to simplify error handling when dealing
 with databases, database module authors may choose to implement user
-defineable error handlers. This section describes a standard way of
+definable error handlers. This section describes a standard way of
 defining these error handlers.
 
 .. _Connection.errorhandler:

pep-0255.txt

@@ -198,7 +198,7 @@ Specification:  Return
     function return, executing the appropriate finally clauses (if any
     exist).  Then a StopIteration exception is raised, signalling that the
     iterator is exhausted.   A StopIteration exception is also raised if
-    control flows off the end of the generator without an explict return.
+    control flows off the end of the generator without an explicit return.
 
     Note that return means "I'm done, and have nothing interesting to
     return", for both generator functions and non-generator functions.
@@ -377,7 +377,7 @@ Q & A
        yield is a control construct.  It's also believed that efficient
        implementation in Jython requires that the compiler be able to
        determine potential suspension points at compile-time, and a new
-       keyword makes that easy.  The CPython referrence implementation also
+       keyword makes that easy.  The CPython reference implementation also
        exploits it heavily, to detect which functions *are* generator-
        functions (although a new keyword in place of "def" would solve that
        for CPython -- but people asking the "why a new keyword?" question

pep-0258.txt

@@ -206,7 +206,7 @@ the Reader has finished processing, the Publisher_ calls
 and all default transforms are stored.
 
 Each transform is a class in a module in the ``docutils/transforms/``
-package, a subclass of ``docutils.tranforms.Transform``.  Transform
+package, a subclass of ``docutils.transforms.Transform``.  Transform
 classes each have a ``default_priority`` attribute which is used by
 the Transformer to apply transforms in order (low to high).  The
 default priority can be overridden when adding transforms to the

pep-0259.txt

@@ -116,7 +116,7 @@ Rejected
     this idea any further.  Frequently heard arguments against
     included:
 
-    - It it likely to break thousands of CGI scripts.
+    - It is likely to break thousands of CGI scripts.
 
     - Enough magic already (also: no more tinkering with 'print'
       please).

pep-0261.txt

@@ -109,7 +109,7 @@ Proposed Solution
 
             Surrogates could be easily created this way but the user
             still needs to be careful about slicing, indexing, printing 
-            etc. Therefore some have suggested that Unicode
+            etc. Therefore, some have suggested that Unicode
             literals should not support surrogates.
 
 

pep-0268.txt

@@ -128,7 +128,7 @@ authentication scheme is typically set up hierarchically: the
 credentials for ``/path`` can be tried for ``/path/subpath``. The
 Digest authentication scheme has explicit support for the hierarchical
 setup. The ``httpx.Credentials`` object will store credentials for
-multiple protection spaces, and can be looked up in two differents
+multiple protection spaces, and can be looked up in two different
 ways:
 
 1. looked up using ``(host, port, path)`` -- this lookup scheme is

pep-0273.txt

@@ -190,11 +190,11 @@ Custom Imports
 Implementation
 
     A C implementation is available as SourceForge patch 492105.
-    Superceded by patch 652586 and current CVS.
+    Superseded by patch 652586 and current CVS.
     http://python.org/sf/492105
 
     A newer version (updated for recent CVS by Paul Moore) is 645650.
-    Superceded by patch 652586 and current CVS.
+    Superseded by patch 652586 and current CVS.
     http://python.org/sf/645650
 
     A competing implementation by Just van Rossum is 652586, which is

pep-0275.txt

@@ -178,7 +178,7 @@ Solution 2: Adding a switch statement to Python
                   else: 
                       print "D'oh!"
 
-         into (ommitting POP_TOP's and SET_LINENO's):
+         into (omitting POP_TOP's and SET_LINENO's):
 
            6  LOAD_FAST         0 (x)
            9  LOAD_CONST        1 (switch-table-1)
@@ -218,7 +218,7 @@ Solution 2: Adding a switch statement to Python
         behaviour (as does the switch statement in C). Each case
         defines a complete and independent suite; much like in a
         if-elif-else statement. This also enables using break in
-        switch statments inside loops.
+        switch statements inside loops.
 
         If the interpreter finds that the switch variable x is
         not hashable, it should raise a TypeError at run-time

pep-0276.txt

@@ -320,7 +320,7 @@ Issues:
       issue by using a variation of what is outlined in the
       specification section of this proposal.  Instead of adding
       an __iter__ method to class int, change the for-loop handling
-      code to convert (in essense) from
+      code to convert (in essence) from
 
           for i in n:  # when isinstance(n,int) is 1
 
@@ -384,14 +384,14 @@ Issues:
     - and more.
 
     It should be noted that there was much debate but not an
-    overwhelming concensus for any of these larger-scale suggestions.
+    overwhelming consensus for any of these larger-scale suggestions.
 
     Clearly, PEP 276 does not propose such a large-scale change
     and instead focuses on a specific problem area.  Towards the
     end of the discussion period, several posters expressed favor
     for the narrow focus and simplicity of PEP 276 vis-a-vis the more
     ambitious suggestions that were advanced.  There did appear to be
-    concensus for the need for a PEP for any such larger-scale,
+    consensus for the need for a PEP for any such larger-scale,
     alternative suggestion.  In light of this recognition, details of
     the various alternative suggestions are not discussed here further.