summaryrefslogtreecommitdiff
path: root/Doc/library/imaplib.rst
diff options
context:
space:
mode:
authorMartin Panter <vadmium+py@gmail.com>2016-05-26 06:03:33 +0000
committerMartin Panter <vadmium+py@gmail.com>2016-05-26 06:03:33 +0000
commitf157982b2c66be30d94a3f3ce0dfc2d9ebd3bd19 (patch)
tree39c71ffdf07566b30f7dc3a64c0b76e99be6240a /Doc/library/imaplib.rst
parent3e04d5b3068ac67cc01a32b1d5a51ac79c9df5a1 (diff)
downloadcpython-git-f157982b2c66be30d94a3f3ce0dfc2d9ebd3bd19.tar.gz
Issue #27076: More doc and comment spelling fixes for 3.6, by Ville Skyttä
Diffstat (limited to 'Doc/library/imaplib.rst')
-rw-r--r--Doc/library/imaplib.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/imaplib.rst b/Doc/library/imaplib.rst
index f604cfba65..e33bac0778 100644
--- a/Doc/library/imaplib.rst
+++ b/Doc/library/imaplib.rst
@@ -507,7 +507,7 @@ An :class:`IMAP4` instance has the following methods:
allowed creation of such tags, and popular IMAP servers, such as Gmail,
accept and produce such flags. There are non-Python programs which also
create such tags. Although it is an RFC violation and IMAP clients and
- servers are supposed to be strict, imaplib nontheless continues to allow
+ servers are supposed to be strict, imaplib nonetheless continues to allow
such tags to be created for backward compatibility reasons, and as of
python 3.6, handles them if they are sent from the server, since this
improves real-world compatibility.