From: Jeroen Ruigrok van der Werven <asmodai@in-nomine.org>
Date: Thu, 17 Apr 2008 12:39:45 +0000 (+0000)
Subject: Be consistent in the use of read-only.
X-Git-Tag: v2.6a3~174
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ea7fa726305a39aa59660c93fd26c0cc916a8c0e;p=python

Be consistent in the use of read-only.
---

diff --git a/Doc/library/mmap.rst b/Doc/library/mmap.rst
index d2a6d1e4b4..a9a4ad8121 100644
--- a/Doc/library/mmap.rst
+++ b/Doc/library/mmap.rst
@@ -26,7 +26,7 @@ still needs to be closed when done).
 For both the Unix and Windows versions of the constructor, *access* may be
 specified as an optional keyword parameter. *access* accepts one of three
 values: :const:`ACCESS_READ`, :const:`ACCESS_WRITE`, or :const:`ACCESS_COPY`
-to specify readonly, write-through or copy-on-write memory respectively.
+to specify read-only, write-through or copy-on-write memory respectively.
 *access* can be used on both Unix and Windows.  If *access* is not specified,
 Windows mmap returns a write-through mapping.  The initial memory values for
 all three access types are taken from the specified file.  Assignment to an