@@ -21,7 +21,7 @@ import kotlinx.coroutines.experimental.intrinsics.*
2121import kotlin.coroutines.experimental.*
2222
2323/* *
24- * Defines start option for coroutines builders.
24+ * Defines start options for coroutines builders.
2525 * It is used in `start` parameter of [launch], [async], and other coroutine builder functions.
2626 *
2727 * The summary of coroutine start options is:
@@ -42,7 +42,7 @@ public enum class CoroutineStart {
4242 * function, so starting coroutine with [Unconfined] dispatcher by [DEFAULT] is the same as using [UNDISPATCHED].
4343 *
4444 * If coroutine [Job] is cancelled before it even had a chance to start executing, then it will not start its
45- * execution at all, but complete with an exception.
45+ * execution at all, but will complete with an exception.
4646 *
4747 * Cancellability of coroutine at suspension points depends on the particular implementation details of
4848 * suspending functions. Use [suspendCancellableCoroutine] to implement cancellable suspending functions.
@@ -56,12 +56,12 @@ public enum class CoroutineStart {
5656 * (like [launch] and [async]).
5757 *
5858 * If coroutine [Job] is cancelled before it even had a chance to start executing, then it will not start its
59- * execution at all, but complete with an exception.
59+ * execution at all, but will complete with an exception.
6060 */
6161 LAZY ,
6262
6363 /* *
64- * Atomically (in non-cancellable way) schedules coroutine for execution according to its context.
64+ * Atomically (i.e., in a non-cancellable way) schedules coroutine for execution according to its context.
6565 * This is similar to [DEFAULT], but the coroutine cannot be cancelled before it starts executing.
6666 *
6767 * Cancellability of coroutine at suspension points depends on the particular implementation details of
@@ -70,12 +70,12 @@ public enum class CoroutineStart {
7070 ATOMIC ,
7171
7272 /* *
73- * Immediately executes coroutine until its first suspension point _in the current thread_ as if it the
73+ * Immediately executes coroutine until its first suspension point _in the current thread_ as if the
7474 * coroutine was started using [Unconfined] dispatcher. However, when coroutine is resumed from suspension
7575 * it is dispatched according to the [CoroutineDispatcher] in its context.
7676 *
7777 * This is similar to [ATOMIC] in the sense that coroutine starts executing even if it was already cancelled,
78- * but the difference is that it start executing in the same thread.
78+ * but the difference is that it starts executing in the same thread.
7979 *
8080 * Cancellability of coroutine at suspension points depends on the particular implementation details of
8181 * suspending functions as in [DEFAULT].
0 commit comments