Docs: chore: "Debug suspend functions" after proofread

Author: PetrakovichVictoria

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

@@ -108,7 +108,7 @@ If you use `suspend` functions, in the debugger, you might see the "was optimise
 ![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.
+It is difficult to debug code with optimised variables 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).

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

@@ -109,7 +109,7 @@ If you use `suspend` functions, in the debugger, you might see the "was optimise
 ![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.
+It is difficult to debug code with optimised variables 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).