[Python-checkins] [3.9] [doc] Fix typos found using codespell (GH-28744) (GH-28759)

[ambv]

https://github.com/python/cpython/commit/edef03aaa8993901e63e901448ec2be8b2801ca7
commit: edef03aaa8993901e63e901448ec2be8b2801ca7
branch: 3.9
author: Christian Clauss <cclauss at me.com>
committer: ambv <lukasz at langa.pl>
date: 2021-10-06T15:57:39+02:00
summary:

[3.9] [doc] Fix typos found using codespell (GH-28744) (GH-28759)

files:
M Doc/c-api/call.rst
M Doc/faq/design.rst
M Doc/library/ast.rst
M Doc/library/test.rst
M Doc/library/types.rst

diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst
index 31dc9c8031fdb..739b5e97d1515 100644
--- a/Doc/c-api/call.rst
+++ b/Doc/c-api/call.rst
@@ -185,7 +185,7 @@ Object Calling API
 Various functions are available for calling a Python object.
 Each converts its arguments to a convention supported by the called object –
 either *tp_call* or vectorcall.
-In order to do as litle conversion as possible, pick one that best fits
+In order to do as little conversion as possible, pick one that best fits
 the format of data you have available.
 
 The following table summarizes the available functions;
diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index d2b868ebb8290..d0aee4e607268 100644
--- a/Doc/faq/design.rst
+++ b/Doc/faq/design.rst
@@ -715,7 +715,7 @@ Why don't generators support the with statement?
 For technical reasons, a generator used directly as a context manager
 would not work correctly.  When, as is most common, a generator is used as
 an iterator run to completion, no closing is needed.  When it is, wrap
-it as "contextlib.closing(generator)" in the 'with' statment.
+it as "contextlib.closing(generator)" in the 'with' statement.
 
 
 Why are colons required for the if/while/def/class statements?
diff --git a/Doc/library/ast.rst b/Doc/library/ast.rst
index 39a08416bad72..149179d5bfd5d 100644
--- a/Doc/library/ast.rst
+++ b/Doc/library/ast.rst
@@ -1552,7 +1552,7 @@ and classes for traversing abstract syntax trees:
    If source contains a null character ('\0'), :exc:`ValueError` is raised.
 
     .. warning::
-      Note that succesfully parsing souce code into an AST object doesn't
+      Note that successfully parsing source code into an AST object doesn't
       guarantee that the source code provided is valid Python code that can
       be executed as the compilation step can raise further :exc:`SyntaxError`
       exceptions. For instance, the source ``return 42`` generates a valid
diff --git a/Doc/library/test.rst b/Doc/library/test.rst
index c4abcfffa1f14..16f908c8e8708 100644
--- a/Doc/library/test.rst
+++ b/Doc/library/test.rst
@@ -457,7 +457,7 @@ The :mod:`test.support` module defines the following functions:
 .. function:: unlink(filename)
 
    Call :func:`os.unlink` on *filename*.  On Windows platforms, this is
-   wrapped with a wait loop that checks for the existence fo the file.
+   wrapped with a wait loop that checks for the existence of the file.
 
 
 .. function:: rmdir(filename)
@@ -1145,7 +1145,7 @@ The :mod:`test.support` module defines the following functions:
    Context manager catching :class:`threading.Thread` exception using
    :func:`threading.excepthook`.
 
-   Attributes set when an exception is catched:
+   Attributes set when an exception is caught:
 
    * ``exc_type``
    * ``exc_value``
diff --git a/Doc/library/types.rst b/Doc/library/types.rst
index 81a2b7b987970..b6df39258e66e 100644
--- a/Doc/library/types.rst
+++ b/Doc/library/types.rst
@@ -229,7 +229,7 @@ Standard names are defined for the following types:
 
       .. note::
          A future version of Python may stop setting this attribute by default.
-         To guard against this potential change, preferrably read from the
+         To guard against this potential change, preferably read from the
          :attr:`__spec__` attribute instead or use
          ``getattr(module, "__loader__", None)`` if you explicitly need to use
          this attribute.
@@ -254,7 +254,7 @@ Standard names are defined for the following types:
 
       .. note::
          A future version of Python may stop setting this attribute by default.
-         To guard against this potential change, preferrably read from the
+         To guard against this potential change, preferably read from the
          :attr:`__spec__` attribute instead or use
          ``getattr(module, "__package__", None)`` if you explicitly need to use
          this attribute.