From e0d5813d56c19656d0c76cea68ba919e1a021500 Mon Sep 17 00:00:00 2001
From: Siddharth Velankar <17737361+soolabettu@users.noreply.github.com>
Date: Thu, 24 Jul 2025 17:29:27 -0400
Subject: [PATCH 1/3] Remove redundant statement

---
 Doc/library/concurrent.interpreters.rst | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/Doc/library/concurrent.interpreters.rst b/Doc/library/concurrent.interpreters.rst
index be9d565f8e0d38..f8c3f625e5f3e2 100644
--- a/Doc/library/concurrent.interpreters.rst
+++ b/Doc/library/concurrent.interpreters.rst
@@ -134,10 +134,9 @@ 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.
-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,
+concurrency, as 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,
 a model which is relatively easy to reason about.
 
 You can take advantage of that concurrency model in a single thread,

From c67b9d3b9a582249715e898851f4e783241362cf Mon Sep 17 00:00:00 2001
From: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Date: Fri, 25 Jul 2025 11:56:57 +0100
Subject: [PATCH 2/3] Update Doc/library/concurrent.interpreters.rst

---
 Doc/library/concurrent.interpreters.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Doc/library/concurrent.interpreters.rst b/Doc/library/concurrent.interpreters.rst
index f8c3f625e5f3e2..ee982434dcdba2 100644
--- a/Doc/library/concurrent.interpreters.rst
+++ b/Doc/library/concurrent.interpreters.rst
@@ -134,9 +134,10 @@ 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. 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,
+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,
 a model which is relatively easy to reason about.
 
 You can take advantage of that concurrency model in a single thread,

From 7283f88554f2b9a6937e53d1e661eda5bb9181be Mon Sep 17 00:00:00 2001
From: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Date: Fri, 25 Jul 2025 11:57:09 +0100
Subject: [PATCH 3/3] Update Doc/library/concurrent.interpreters.rst

---
 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 ee982434dcdba2..41ea6af3b226e9 100644
--- a/Doc/library/concurrent.interpreters.rst
+++ b/Doc/library/concurrent.interpreters.rst
@@ -135,7 +135,7 @@ efficiency, like threads.
 
 All that said, interpreters do naturally support certain flavors of
 concurrency.
-There's a powerful side effect of that isolation. It enables a
+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,
 a model which is relatively easy to reason about.