Minor documentation fixes (#3762)

* Remove unnecessary newline (#3756) * Properly name Flow.timeout param in the documentation --------- Co-authored-by: Hanbit Kang <[email protected]>
Kotlin · Jun 22, 2023 · c5ce96a · c5ce96a
1 parent 1074e33
commit c5ce96a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/docs/topics/shared-mutable-state-and-concurrency.md b/docs/topics/shared-mutable-state-and-concurrency.md
@@ -195,8 +195,7 @@ state or to complex operations that do not have ready-to-use thread-safe impleme
 
 _Thread confinement_ is an approach to the problem of shared mutable state where all access to the particular shared
 state is confined to a single thread. It is typically used in UI applications, where all UI state is confined to 
-the single event-dispatch/application thread. It is easy to apply with coroutines by using a  
-single-threaded context. 
+the single event-dispatch/application thread. It is easy to apply with coroutines by using a single-threaded context. 
 
 <!--- CLEAR -->
 

diff --git a/kotlinx-coroutines-core/common/src/flow/operators/Delay.kt b/kotlinx-coroutines-core/common/src/flow/operators/Delay.kt
@@ -376,7 +376,7 @@ public fun <T> Flow<T>.sample(period: Duration): Flow<T> = sample(period.toDelay
  *
  * Note that delaying on the downstream doesn't trigger the timeout.
  *
- * @param timeout period. If non-positive, the flow is timed out immediately
+ * @param timeout Timeout duration. If non-positive, the flow is timed out immediately
  */
 @FlowPreview
 public fun <T> Flow<T>.timeout(