summaryrefslogtreecommitdiffstats
path: root/Doc/library/enum.rst
diff options
context:
space:
mode:
authorPablo Galindo <Pablogsal@gmail.com>2021-01-25 23:23:30 (GMT)
committerGitHub <noreply@github.com>2021-01-25 23:23:30 (GMT)
commitc92cd0f3c8bab4e26a95cd29c127668907ff0869 (patch)
tree1fe3ee8dd8d7a6fe3754bffb0d88e6d413720497 /Doc/library/enum.rst
parent7c8e0b03366e053e0673f1f2ae31eb464fae8c57 (diff)
downloadcpython-c92cd0f3c8bab4e26a95cd29c127668907ff0869.zip
cpython-c92cd0f3c8bab4e26a95cd29c127668907ff0869.tar.gz
cpython-c92cd0f3c8bab4e26a95cd29c127668907ff0869.tar.bz2
Fix minor typo in the rest format in the enum docs (GH-24335)
Diffstat (limited to 'Doc/library/enum.rst')
-rw-r--r--Doc/library/enum.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/enum.rst b/Doc/library/enum.rst
index b27c552..4d6f2c3 100644
--- a/Doc/library/enum.rst
+++ b/Doc/library/enum.rst
@@ -1364,7 +1364,7 @@ The code sample::
True
There is a new boundary mechanism that controls how out-of-range / invalid
-bits are handled: ``STRICT``, ``CONFORM``, ``EJECT`', and ``KEEP``:
+bits are handled: ``STRICT``, ``CONFORM``, ``EJECT``, and ``KEEP``:
* STRICT --> raises an exception when presented with invalid values
* CONFORM --> discards any invalid bits