Skip to content

[3.9] Fix typos in the Doc directory #28744 #28759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 6, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Doc/c-api/call.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down
2 changes: 1 addition & 1 deletion Doc/faq/design.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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?
Expand Down
2 changes: 1 addition & 1 deletion Doc/library/ast.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions Doc/library/test.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down Expand Up @@ -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``
Expand Down
4 changes: 2 additions & 2 deletions Doc/library/types.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
Expand Down