[3.12] Fix a few typos found in the docs (GH-127126) (GH-127185)

(cherry picked from commit 39e60aeb38)
This commit is contained in:
Rafael Fontenelle 2024-11-25 16:48:00 -03:00 committed by GitHub
parent a4d6b905dd
commit 3806772b3d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 4 additions and 4 deletions

View file

@ -133,7 +133,7 @@ Entry points
Details of a collection of installed entry points. Details of a collection of installed entry points.
Also provides a ``.groups`` attribute that reports all identifed entry Also provides a ``.groups`` attribute that reports all identified entry
point groups, and a ``.names`` attribute that reports all identified entry point groups, and a ``.names`` attribute that reports all identified entry
point names. point names.

View file

@ -282,7 +282,7 @@ processes:
of corruption from processes using different ends of the pipe at the same of corruption from processes using different ends of the pipe at the same
time. time.
The :meth:`~Connection.send` method serializes the the object and The :meth:`~Connection.send` method serializes the object and
:meth:`~Connection.recv` re-creates the object. :meth:`~Connection.recv` re-creates the object.
Synchronization between processes Synchronization between processes
@ -819,7 +819,7 @@ For an example of the usage of queues for interprocess communication see
used for receiving messages and ``conn2`` can only be used for sending used for receiving messages and ``conn2`` can only be used for sending
messages. messages.
The :meth:`~multiprocessing.Connection.send` method serializes the the object using The :meth:`~multiprocessing.Connection.send` method serializes the object using
:mod:`pickle` and the :meth:`~multiprocessing.Connection.recv` re-creates the object. :mod:`pickle` and the :meth:`~multiprocessing.Connection.recv` re-creates the object.
.. class:: Queue([maxsize]) .. class:: Queue([maxsize])

View file

@ -966,7 +966,7 @@ The :mod:`socket` module also offers various network-related services:
These addresses should generally be tried in order until a connection succeeds These addresses should generally be tried in order until a connection succeeds
(possibly tried in parallel, for example, using a `Happy Eyeballs`_ algorithm). (possibly tried in parallel, for example, using a `Happy Eyeballs`_ algorithm).
In these cases, limiting the *type* and/or *proto* can help eliminate In these cases, limiting the *type* and/or *proto* can help eliminate
unsuccessful or unusable connecton attempts. unsuccessful or unusable connection attempts.
Some systems will, however, only return a single address. Some systems will, however, only return a single address.
(For example, this was reported on Solaris and AIX configurations.) (For example, this was reported on Solaris and AIX configurations.)