Update the wording for Dispatchers.Unconfined

ansman · web-flow · commit 7594ef81d644 · 2023-02-01T09:48:27.000-05:00
In my recent PR (Kotlin#3607) I changed the example for `Dispatchers.Unconfined` but the rest of the documentation still mentions two `withContext` which isn't correct any longer.
diff --git a/kotlinx-coroutines-core/common/src/Dispatchers.common.kt b/kotlinx-coroutines-core/common/src/Dispatchers.common.kt
@@ -64,7 +64,7 @@ public expect object Dispatchers {
      * println("Done")
      * ```
      * Can print both "1 2 3" and "1 3 2". This is an implementation detail that can be changed.
-     * However, it is guaranteed that "Done" will be printed only when both `withContext` calls are completed.
+     * However, it is guaranteed that "Done" will be printed only the `withContext` call is completed.
      *
      * If you need your coroutine to be confined to a particular thread or a thread-pool after resumption,
      * but still want to execute it in the current call-frame until its first suspension, you can use

Original file line number	Diff line number	Diff line change
`@@ -64,7 +64,7 @@ public expect object Dispatchers {`
`64`	`64`	`* println("Done")`
`65`	`65`	* ```
`66`	`66`	`* Can print both "1 2 3" and "1 3 2". This is an implementation detail that can be changed.`
`67`		- * However, it is guaranteed that "Done" will be printed only when both `withContext` calls are completed.
	`67`	+ * However, it is guaranteed that "Done" will be printed only the `withContext` call is completed.
`68`	`68`	`*`
`69`	`69`	`* If you need your coroutine to be confined to a particular thread or a thread-pool after resumption,`
`70`	`70`	`* but still want to execute it in the current call-frame until its first suspension, you can use`