From dfea716bc182c25339bac8a48b126aa9856a8b62 Mon Sep 17 00:00:00 2001 From: Dorian Cussen Date: Fri, 10 Sep 2021 13:33:20 +0100 Subject: [PATCH] Update 04_Suspend.md Fix from non-existant option declaration. --- Introduction to Coroutines and Channels/04_Suspend.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Introduction to Coroutines and Channels/04_Suspend.md b/Introduction to Coroutines and Channels/04_Suspend.md index 76f220c..9d10683 100644 --- a/Introduction to Coroutines and Channels/04_Suspend.md +++ b/Introduction to Coroutines and Channels/04_Suspend.md @@ -144,7 +144,7 @@ The coroutine resumes only after the corresponding response is received: ![](./assets/4-suspend/SuspendRequests.png) While the response is waiting to be received, the thread is free to be occupied with other tasks. -That's why when users are loaded via the `COROUTINE` option, the UI stays responsive, despite all the requests +That's why when users are loaded via the `SUSPEND` option, the UI stays responsive, despite all the requests taking place on the main UI thread. The log confirms that all the requests are sent on the main UI thread: