diff --git a/topics/basics/architectural_overview/threading/execution_contexts.topic b/topics/basics/architectural_overview/threading/execution_contexts.topic
index f5142a0c8..cf5e88fb1 100644
--- a/topics/basics/architectural_overview/threading/execution_contexts.topic
+++ b/topics/basics/architectural_overview/threading/execution_contexts.topic
@@ -53,7 +53,9 @@
While code executed in the Coroutine Execution Context should use suspending functions,
sometimes it is required to call non-suspending/blocking APIs that use methods such as
ProgressManager.checkCanceled()
or ModalityState.defaultModalityState()
.
- Since 2024.2, these methods work as expected without the need to switch to the Blocking Context.
+ Since 2024.2, these methods work as expected without the need to switch to the Blocking Context
+ explicitly with
+ blockingContext()
(in 2024.2+, it is effectively a no-operation function).