summaryrefslogtreecommitdiffstats
path: root/Doc/reference
diff options
context:
space:
mode:
authorRaymond Hettinger <rhettinger@users.noreply.github.com>2021-10-02 18:48:08 (GMT)
committerGitHub <noreply@github.com>2021-10-02 18:48:08 (GMT)
commitdb91b058d5d4fbff4185982095d90fe6a2741aed (patch)
tree7ef4237d739f1f707f1892fa961362acb807b1a8 /Doc/reference
parent0742abdc48886b74ed3b66985a54bb1c32802670 (diff)
downloadcpython-db91b058d5d4fbff4185982095d90fe6a2741aed.zip
cpython-db91b058d5d4fbff4185982095d90fe6a2741aed.tar.gz
cpython-db91b058d5d4fbff4185982095d90fe6a2741aed.tar.bz2
bpo-45346: Keep docs consistent regarding true and false values (GH-28697)
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 f24222f..5936cdf 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