From 6974e19341174b854f4c6d7a5ccc258c58a89aa2 Mon Sep 17 00:00:00 2001 From: Yakov Burtsev Date: Wed, 9 Mar 2022 09:58:15 +0100 Subject: [PATCH] Fix a typo (#3213) --- docs/topics/coroutine-context-and-dispatchers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/coroutine-context-and-dispatchers.md b/docs/topics/coroutine-context-and-dispatchers.md index c5a869dff8..4e5ed02b87 100644 --- a/docs/topics/coroutine-context-and-dispatchers.md +++ b/docs/topics/coroutine-context-and-dispatchers.md @@ -306,7 +306,7 @@ However, this parent-child relation can be explicitly overriden in one of two wa 1. When a different scope is explicitly specified when launching a coroutine (for example, `GlobalScope.launch`), then it does not inherit a `Job` from the parent scope. -2. When a different `Job` object is passed as the context for the new coroutine (as show in the example below), +2. When a different `Job` object is passed as the context for the new coroutine (as shown in the example below), then it overrides the `Job` of the parent scope. In both cases, the launched coroutine is not tied to the scope it was launched from and operates independently.