summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2024-01-26 13:42:49 (GMT)
committerGitHub <noreply@github.com>2024-01-26 13:42:49 (GMT)
commit30b7b4f73cd876732244de06d079a2caf2a7b95c (patch)
tree105a8f7678d5e5212925ce64b0b247a0e389fac6
parent8710faeac28e65c65862359413e8341492f529af (diff)
downloadcpython-30b7b4f73cd876732244de06d079a2caf2a7b95c.zip
cpython-30b7b4f73cd876732244de06d079a2caf2a7b95c.tar.gz
cpython-30b7b4f73cd876732244de06d079a2caf2a7b95c.tar.bz2
Docs: 'still' is a better word than 'nonetheless' (#114598)
-rw-r--r--Doc/library/dataclasses.rst2
-rw-r--r--Doc/library/imaplib.rst2
-rw-r--r--Doc/using/cmdline.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/Doc/library/dataclasses.rst b/Doc/library/dataclasses.rst
index cde147d..88f2e02 100644
--- a/Doc/library/dataclasses.rst
+++ b/Doc/library/dataclasses.rst
@@ -141,7 +141,7 @@ Module contents
then :func:`dataclass` *may* add an implicit :meth:`~object.__hash__` method.
Although not recommended, you can force :func:`dataclass` to create a
:meth:`~object.__hash__` method with ``unsafe_hash=True``. This might be the case
- if your class is logically immutable but can nonetheless be mutated.
+ if your class is logically immutable but can still be mutated.
This is a specialized use case and should be considered carefully.
Here are the rules governing implicit creation of a :meth:`~object.__hash__`
diff --git a/Doc/library/imaplib.rst b/Doc/library/imaplib.rst
index 1f774e6..d5c868d 100644
--- a/Doc/library/imaplib.rst
+++ b/Doc/library/imaplib.rst
@@ -531,7 +531,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 nonetheless continues to allow
+ servers are supposed to be strict, imaplib still 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.
diff --git a/Doc/using/cmdline.rst b/Doc/using/cmdline.rst
index df8b07c..53c95ca 100644
--- a/Doc/using/cmdline.rst
+++ b/Doc/using/cmdline.rst
@@ -623,7 +623,7 @@ Setting the environment variable ``TERM`` to ``dumb`` will disable color.
If the environment variable ``FORCE_COLOR`` is set, then color will be
enabled regardless of the value of TERM. This is useful on CI systems which
-aren’t terminals but can none-the-less display ANSI escape sequences.
+aren’t terminals but can still display ANSI escape sequences.
If the environment variable ``NO_COLOR`` is set, Python will disable all color
in the output. This takes precedence over ``FORCE_COLOR``.