summaryrefslogtreecommitdiffstats
path: root/Doc/reference
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2021-10-02 19:32:56 (GMT)
committerGitHub <noreply@github.com>2021-10-02 19:32:56 (GMT)
commit72089f33c0aed391f047b1cbaf19d8da1e51c167 (patch)
tree972aecf2f59602644e274b4145be3a261c81e766 /Doc/reference
parent22cf6a2f2347b7d4f11e45e557beace55acc79b5 (diff)
downloadcpython-72089f33c0aed391f047b1cbaf19d8da1e51c167.zip
cpython-72089f33c0aed391f047b1cbaf19d8da1e51c167.tar.gz
cpython-72089f33c0aed391f047b1cbaf19d8da1e51c167.tar.bz2
bpo-45346: Keep docs consistent regarding true and false values (GH-28697) (GH-28698)
Diffstat (limited to 'Doc/reference')
-rw-r--r--Doc/reference/compound_stmts.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/reference/compound_stmts.rst b/Doc/reference/compound_stmts.rst
index 25abc1b..41719be 100644
--- a/Doc/reference/compound_stmts.rst
+++ b/Doc/reference/compound_stmts.rst
@@ -585,8 +585,8 @@ Here's an overview of the logical flow of a match statement:
#. If the pattern succeeds, the corresponding guard (if present) is evaluated. In
this case all name bindings are guaranteed to have happened.
- * If the guard evaluates as truthy or missing, the ``block`` inside ``case_block`` is
- executed.
+ * If the guard evaluates as true or is missing, the ``block`` inside
+ ``case_block`` is executed.
* Otherwise, the next ``case_block`` is attempted as described above.
@@ -637,10 +637,10 @@ The logical flow of a ``case`` block with a ``guard`` follows:
#. If the pattern succeeded, evaluate the ``guard``.
- * If the ``guard`` condition evaluates to "truthy", the case block is
+ * If the ``guard`` condition evaluates as true, the case block is
selected.
- * If the ``guard`` condition evaluates to "falsy", the case block is not
+ * If the ``guard`` condition evaluates as false, the case block is not
selected.
* If the ``guard`` raises an exception during evaluation, the exception