Docs: 'still' is a better word than 'nonetheless' (#114598)

diff --git a/Doc/library/dataclasses.rst b/Doc/library/dataclasses.rst
index cde147d1cbb501b37b289fc5417fb96e3ae96f3c..88f2e0251b1e5192a029db52ab629c14c951ab98 100644 (file)
--- 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 1f774e64b0eae33e77b4253703ecb5735199ecba..d5c868def3b64f78fd5b32138000a120d28ff8fe 100644 (file)
--- 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 df8b07c6118599860fe957f1e92c18ad778b99e0..53c95ca1a05c9b47a2fe93eb50d16d2c2f04ddb4 100644 (file)
--- 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``.