From f05b2f5b41694a51aa0fdd4b6dc552e4ff345ab8 Mon Sep 17 00:00:00 2001
From: max <36980911+pr2502@users.noreply.github.com>
Date: Tue, 21 Jun 2022 21:44:09 +0200
Subject: [PATCH] Tutorial: specify match cases don't fall through (GH-93615)
 (cherry picked from commit dd5cf84f245abf84405833320b8f25dbc43b24d2)

Co-authored-by: max <36980911+pr2502@users.noreply.github.com>
---
 Doc/tutorial/controlflow.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Doc/tutorial/controlflow.rst b/Doc/tutorial/controlflow.rst
index f6e013b23e7e58..99a77e7addd774 100644
--- a/Doc/tutorial/controlflow.rst
+++ b/Doc/tutorial/controlflow.rst
@@ -253,8 +253,10 @@ at a more abstract level.  The :keyword:`!pass` is silently ignored::
 A :keyword:`match` statement takes an expression and compares its value to successive
 patterns given as one or more case blocks.  This is superficially
 similar to a switch statement in C, Java or JavaScript (and many
-other languages), but it can also extract components (sequence elements or
-object attributes) from the value into variables.
+other languages), but it's more similar to pattern matching in
+languages like Rust or Haskell. Only the first pattern that matches
+gets executed and it can also extract components (sequence elements
+or object attributes) from the value into variables.
 
 The simplest form compares a subject value against one or more literals::