Docs: update: Debug suspend functions as separate section

Author: PetrakovichVictoria

docs/topics/coroutines-basics.md

@@ -105,21 +105,28 @@ 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).
+>
+{type="note"}
 
 <!--- TEST
 Hello
 World!
 -->
 
-> 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.
+## Debug suspend functions
+
+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="tip"}
+{type="warning"}
 
 ## Scope builder