Docs: update tip about -Xdebug to disable "was optimise out" effect

Author: PetrakovichVictoria

docs/images/variable-optimised-out.png

@@ -105,14 +105,16 @@ suspend fun doWorld() {
 ```
 {kotlin-runnable="true" kotlin-min-compiler-version="1.3"}
 
-> You can get the full code [here](../../kotlinx-coroutines-core/jvm/test/guide/example-basic-02.kt).
+You can get the full code [here](../../kotlinx-coroutines-core/jvm/test/guide/example-basic-02.kt).
+
+> If you use `suspend` functions, in the debugger, you might see the "was optimised out" text next to a variable's name:
+> ![Variable "a" was optimised out](variable-optimised-out.png)
+> This text means that the variable's lifetime was decreased, and the variable doesn't exist anymore.
+> Debugging code with optimised variables is hard because you don't see their values.
+> You can disable this behavior with the `-Xdebug` compiler option.
+> __Never use this flag in production__: `-Xdebug` can [cause memory leaks](https://youtrack.jetbrains.com/issue/KT-48678/Coroutine-debugger-disable-was-optimised-out-compiler-feature#focus=Comments-27-6015585.0-0).
 >
-{type="note"}
-
-<!--- TEST
-Hello
-World!
--->
+{type="tip"}
 
 ## Scope builder
 

docs/topics/coroutines-basics.md

@@ -99,11 +99,4 @@ The tutorial assumes you have prior knowledge of the [coroutines](coroutines-gui
     * The second coroutine has computed its value and disappeared.
     * The third coroutine is calculating the value of `b` – it has the **RUNNING** status.
 
-> You can disable a "was optimised out" feature via the `-Xdebug` compiler option.
-> The "was optimised out" feature optimizes variables when you use suspend functions.
-> However, debugging a code with optimized variables is hard because you don't see their values.
-> Be careful: disabling this feature via `-Xdebug` can [cause memory leaks](https://youtrack.jetbrains.com/issue/KT-48678/Coroutine-debugger-disable-was-optimised-out-compiler-feature#focus=Comments-27-6015585.0-0).
->
-{type="tip"}
-
 Using IntelliJ IDEA debugger, you can dig deeper into each coroutine to debug your code.

docs/topics/debug-coroutines-with-idea.md

@@ -102,13 +102,6 @@ Create a Kotlin [flow](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-cor
 
     ![Debug the coroutine](flow-debug-2.png)
 
-> You can disable a "was optimised out" feature via the `-Xdebug` compiler option.
-> The "was optimised out" feature optimizes variables when you use suspend functions.
-> However, debugging a code with optimized variables is hard because you don't see their values.
-> Be careful: disabling this feature via `-Xdebug` can [cause memory leaks](https://youtrack.jetbrains.com/issue/KT-48678/Coroutine-debugger-disable-was-optimised-out-compiler-feature#focus=Comments-27-6015585.0-0).
->
-{type="tip"}
-
 ## Add a concurrently running coroutine
 
 1. Open the `Main.kt` file in `src/main/kotlin`.