diff --git a/topics/basics/architectural_overview/threading/coroutines/coroutine_edt_and_locks.md b/topics/basics/architectural_overview/threading/coroutines/coroutine_edt_and_locks.md
index ad18541b7..a7f9e5253 100644
--- a/topics/basics/architectural_overview/threading/coroutines/coroutine_edt_and_locks.md
+++ b/topics/basics/architectural_overview/threading/coroutines/coroutine_edt_and_locks.md
@@ -186,3 +186,5 @@ They are intended to be used by the IntelliJ Platform itself.
 Avoid using them in plugin code.
 
 Use it only as a temporal solution if it is hard to quickly rewrite code which checks for write intent lock.
+
+<include from="snippets.md" element-id="missingContent"/>
diff --git a/topics/basics/architectural_overview/threading/execution_contexts.md b/topics/basics/architectural_overview/threading/execution_contexts.md
index 52f0430a7..634858761 100644
--- a/topics/basics/architectural_overview/threading/execution_contexts.md
+++ b/topics/basics/architectural_overview/threading/execution_contexts.md
@@ -184,3 +184,5 @@ It is only possible to:
 
 The lack of an API for switching from suspending and blocking contexts to progress indicator is intentional.
 Cancellable and trackable tasks should be run in coroutines as the progress indicator is obsolete since 2024.1.
+
+<include from="snippets.md" element-id="missingContent"/>