summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorSylvain Bellemare <sbellem@gmail.com>2017-03-24 08:26:07 (GMT)
committerINADA Naoki <methane@users.noreply.github.com>2017-03-24 08:26:07 (GMT)
commit5619ab2db3a6c62ffaa55e8826cf67b7459fc484 (patch)
treea5692ff9068fad5cc2ac4f7fc3baae95a8576471 /Doc
parent8a543c0bc7347d5b333f334d157bf4a7cd33c14a (diff)
downloadcpython-5619ab2db3a6c62ffaa55e8826cf67b7459fc484.zip
cpython-5619ab2db3a6c62ffaa55e8826cf67b7459fc484.tar.gz
cpython-5619ab2db3a6c62ffaa55e8826cf67b7459fc484.tar.bz2
doc: Fix small typos in library/multiprocessing (GH-698)
Diffstat (limited to 'Doc')
-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 96d1424..6b4a8cb 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