summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2018-06-15 13:27:48 -0700
committerAntoine Pitrou <pitrou@free.fr>2018-06-15 22:27:48 +0200
commit2ac5242352b0376700930d335e37feff7e04f68c (patch)
tree65b376dfd736e9458b33e40f9467860990dba16c
parentae4b2af42ce908cd3872dd4442c9805beb725167 (diff)
downloadcpython-git-2ac5242352b0376700930d335e37feff7e04f68c.tar.gz
doc: Fix small typos in library/multiprocessing (GH-698) (GH-7721)
(cherry picked from commit 5619ab2db3a6c62ffaa55e8826cf67b7459fc484) Co-authored-by: Sylvain Bellemare <sbellem@gmail.com>
-rw-r--r--Doc/library/multiprocessing.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 20d7974e29..a3cdfd74ea 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -135,7 +135,7 @@ start a *semaphore tracker* process which tracks the unlinked named
semaphores created by processes of the program. When all processes
have exited the semaphore tracker unlinks any remaining semaphores.
Usually there should be none, but if a process was killed by a signal
-there may some "leaked" semaphores. (Unlinking the named semaphores
+there may be some "leaked" semaphores. (Unlinking the named semaphores
is a serious matter since the system allows only a limited number, and
they will not be automatically unlinked until the next reboot.)
@@ -179,7 +179,7 @@ program. ::
Note that objects related to one context may not be compatible with
processes for a different context. In particular, locks created using
-the *fork* context cannot be passed to a processes started using the
+the *fork* context cannot be passed to processes started using the
*spawn* or *forkserver* start methods.
A library which wants to use a particular start method should probably