From 2177d92aa559662e95bbc3ba7e2b9b549d7d3a55 Mon Sep 17 00:00:00 2001
From: soolabettu <17737361+soolabettu@users.noreply.github.com>
Date: Fri, 25 Jul 2025 11:50:53 -0400
Subject: [PATCH] gh-137090: Remove redundant statement in
 ``Doc/library/concurrent.interpreters.rst`` (GH-137091) (cherry picked from
 commit 1e69cd1634e4f0f8c375be85d11925bd12deef23)

Co-authored-by: soolabettu <17737361+soolabettu@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
---
 Doc/library/concurrent.interpreters.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/library/concurrent.interpreters.rst b/Doc/library/concurrent.interpreters.rst
index be9d565f8e0d38..41ea6af3b226e9 100644
--- a/Doc/library/concurrent.interpreters.rst
+++ b/Doc/library/concurrent.interpreters.rst
@@ -134,7 +134,7 @@ makes them similar to processes, but they still enjoy in-process
 efficiency, like threads.
 
 All that said, interpreters do naturally support certain flavors of
-concurrency, as a powerful side effect of that isolation.
+concurrency.
 There's a powerful side effect of that isolation.  It enables a
 different approach to concurrency than you can take with async or
 threads.  It's a similar concurrency model to CSP or the actor model,