From 9c1b3afc3bc53b1e6a25a82a66337f606cbf8f2e Mon Sep 17 00:00:00 2001 From: Gareth Date: Wed, 21 Jun 2023 17:59:07 +0200 Subject: [PATCH] Minor grammar change under Structured Concurrency (#3689) --- docs/topics/coroutines-basics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/coroutines-basics.md b/docs/topics/coroutines-basics.md index b4a7c0a7ca..d7d6700342 100644 --- a/docs/topics/coroutines-basics.md +++ b/docs/topics/coroutines-basics.md @@ -71,7 +71,7 @@ as threads are expensive resources and blocking them is inefficient and is often ### Structured concurrency Coroutines follow a principle of -**structured concurrency** which means that new coroutines can be only launched in a specific [CoroutineScope] +**structured concurrency** which means that new coroutines can only be launched in a specific [CoroutineScope] which delimits the lifetime of the coroutine. The above example shows that [runBlocking] establishes the corresponding scope and that is why the previous example waits until `World!` is printed after a second's delay and only then exits.