minor fix for typo and link (#3462)

Author: LiYing2010

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

@@ -61,7 +61,7 @@ Create a Kotlin [flow](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-cor
     * Use the [`runBlocking()`](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/run-blocking.html) block to wrap a coroutine.
     * Collect the emitted values using the [`collect()`](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/collect.html) function.
     * Use the [`delay()`](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/delay.html) function to imitate CPU-consuming code. It suspends the coroutine for 300 ms without blocking the thread.
-    * Print the collected value from the flow using the [`println()`](https://kotlinlang.org/api/latest/jvm/stdlib/stdlib/kotlin.io/println.html) function.
+    * Print the collected value from the flow using the [`println()`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.io/println.html) function.
 
     ```kotlin
     fun main() = runBlocking {

docs/topics/flow.md

@@ -1185,7 +1185,7 @@ The output here in this example is a good demonstration of how [flatMapLatest] w
 
 <!--- TEST ARBITRARY_TIME -->
 
-> Note that [flatMapLatest] cancels all the code in its block (`{ requestFlow(it) }` in this example when a new value
+> Note that [flatMapLatest] cancels all the code in its block (`{ requestFlow(it) }` in this example) when a new value
 > is received. 
 > It makes no difference in this particular example, because the call to `requestFlow` itself is fast, not-suspending,
 > and cannot be cancelled. However, a differnce in output would be visible if we were to use suspending functions