Fix "note that" comma everywhere
diff --git a/docs/channels.md b/docs/channels.md
index 35c4eb5..88bbcf7 100644
--- a/docs/channels.md
+++ b/docs/channels.md
@@ -341,7 +341,7 @@
<!--- TEST -->
-Note, that you can build the same pipeline using
+Note that you can build the same pipeline using
[`iterator`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.sequences/iterator.html)
coroutine builder from the standard library.
Replace `produce` with `iterator`, `send` with `yield`, `receive` with `next`,
@@ -445,7 +445,7 @@
<!--- TEST lines.size == 10 && lines.withIndex().all { (i, line) -> line.startsWith("Processor #") && line.endsWith(" received ${i + 1}") } -->
-Note, that cancelling a producer coroutine closes its channel, thus eventually terminating iteration
+Note that cancelling a producer coroutine closes its channel, thus eventually terminating iteration
over the channel that processor coroutines are doing.
Also, pay attention to how we explicitly iterate over channel with `for` loop to perform fan-out in `launchProcessor` code.
@@ -627,7 +627,7 @@
<!--- TEST -->
-Note, that sometimes channels may produce executions that look unfair due to the nature of the executor
+Note that sometimes channels may produce executions that look unfair due to the nature of the executor
that is being used. See [this issue](https://github.com/Kotlin/kotlinx.coroutines/issues/111) for details.
### Ticker channels
diff --git a/docs/composing-suspending-functions.md b/docs/composing-suspending-functions.md
index 456d269..e2358fb 100644
--- a/docs/composing-suspending-functions.md
+++ b/docs/composing-suspending-functions.md
@@ -162,7 +162,7 @@
<!--- TEST ARBITRARY_TIME -->
This is twice as fast, because we have concurrent execution of two coroutines.
-Note, that concurrency with coroutines is always explicit.
+Note that concurrency with coroutines is always explicit.
### Lazily started async
@@ -219,7 +219,7 @@
the programmer on when exactly to start the execution by calling [start][Job.start]. We first
start `one`, then start `two`, and then await for the individual coroutines to finish.
-Note, that if we have called [await][Deferred.await] in `println` and omitted [start][Job.start] on individual
+Note that if we have called [await][Deferred.await] in `println` and omitted [start][Job.start] on individual
coroutines, then we would have got the sequential behaviour as [await][Deferred.await] starts the coroutine
execution and waits for the execution to finish, which is not the intended use-case for laziness.
The use-case for `async(start = CoroutineStart.LAZY)` is a replacement for the
@@ -249,7 +249,7 @@
</div>
-Note, that these `xxxAsync` functions are **not** _suspending_ functions. They can be used from anywhere.
+Note that these `xxxAsync` functions are **not** _suspending_ functions. They can be used from anywhere.
However, their use always implies asynchronous (here meaning _concurrent_) execution of their action
with the invoking code.
@@ -264,7 +264,7 @@
import kotlin.system.*
//sampleStart
-// note, that we don't have `runBlocking` to the right of `main` in this example
+// note that we don't have `runBlocking` to the right of `main` in this example
fun main() {
val time = measureTimeMillis {
// we can initiate async actions outside of a coroutine
diff --git a/docs/coroutine-context-and-dispatchers.md b/docs/coroutine-context-and-dispatchers.md
index 960e1e8..2b7547b 100644
--- a/docs/coroutine-context-and-dispatchers.md
+++ b/docs/coroutine-context-and-dispatchers.md
@@ -267,7 +267,7 @@
<!--- TEST -->
-Note, that this example also uses `use` function from the Kotlin standard library to release threads that
+Note that this example also uses `use` function from the Kotlin standard library to release threads that
are created with [newSingleThreadContext] when they are no longer needed.
### Job in the context
@@ -299,7 +299,7 @@
<!--- TEST lines.size == 1 && lines[0].startsWith("My job is \"coroutine#1\":BlockingCoroutine{Active}@") -->
-Note, that [isActive] in [CoroutineScope] is just a convenient shortcut for
+Note that [isActive] in [CoroutineScope] is just a convenient shortcut for
`coroutineContext[Job]?.isActive == true`.
### Children of a coroutine
diff --git a/docs/select-expression.md b/docs/select-expression.md
index f8604a1..acef4b6 100644
--- a/docs/select-expression.md
+++ b/docs/select-expression.md
@@ -376,7 +376,7 @@
</div>
Now the main function awaits for the first of them to complete and counts the number of deferred values
-that are still active. Note, that we've used here the fact that `select` expression is a Kotlin DSL,
+that are still active. Note that we've used here the fact that `select` expression is a Kotlin DSL,
so we can provide clauses for it using an arbitrary code. In this case we iterate over a list
of deferred values to provide `onAwait` clause for each deferred value.
diff --git a/docs/shared-mutable-state-and-concurrency.md b/docs/shared-mutable-state-and-concurrency.md
index 26005ee..86c932a 100644
--- a/docs/shared-mutable-state-and-concurrency.md
+++ b/docs/shared-mutable-state-and-concurrency.md
@@ -553,7 +553,7 @@
Actor is more efficient than locking under load, because in this case it always has work to do and it does not
have to switch to a different context at all.
-> Note, that an [actor] coroutine builder is a dual of [produce] coroutine builder. An actor is associated
+> Note that an [actor] coroutine builder is a dual of [produce] coroutine builder. An actor is associated
with the channel that it receives messages from, while a producer is associated with the channel that it
sends elements to.