diff --git a/topics/basics/architectural_overview/coroutines/coroutine_dispatchers.md b/topics/basics/architectural_overview/coroutines/coroutine_dispatchers.md
index df637a045..d0c3bf2aa 100644
--- a/topics/basics/architectural_overview/coroutines/coroutine_dispatchers.md
+++ b/topics/basics/architectural_overview/coroutines/coroutine_dispatchers.md
@@ -67,14 +67,6 @@ In the IntelliJ Platform, the EDT dispatcher is also installed as `Dispatchers.M
 Use `Dispatchers.Main` only if the coroutine is IntelliJ Platform-context agnostic (e.g., when it can be executed outside the IntelliJ Platform context).
 Use `Dispatchers.EDT` when in doubt.
 
-### EDT Dispatcher and Write Intent Lock
-
-As explained in the [](threading_model.md#locks-and-edt) section, write intent lock is acquired on EDT implicitly.
-This behavior has changed in coroutine context in version 2024.3.
-
-Since 2024.3, write intent lock is not acquired implicitly in coroutines called on the EDT dispatcher.
-Coroutines must use [`readAction`/`writeAction`/`writeIntentReadAction`](%gh-ic%/platform/core-api/src/com/intellij/openapi/application/coroutines.kt) API to acquire a required lock explicitly.
-
 ## Dispatchers vs. Threads
 
 The dispatcher concept is a higher level of abstraction over threads.
diff --git a/topics/basics/architectural_overview/threading_model.md b/topics/basics/architectural_overview/threading_model.md
index 7408fb7cb..f3d648c56 100644
--- a/topics/basics/architectural_overview/threading_model.md
+++ b/topics/basics/architectural_overview/threading_model.md
@@ -130,11 +130,6 @@ Use other methods for pure UI operations.
 
 </tabs>
 
-> Since 2024.3, write intent lock is not acquired implicitly when code is run in coroutine context on the EDT dispatcher.
-> See [](coroutine_dispatchers.md#edt-dispatcher-and-write-intent-lock).
->
-{style="warning"}
-
 ## Accessing Data
 
 The IntelliJ Platform provides a simple API for accessing data under read or write locks in a form of read and write actions.