Fix typo: are support -> are supported

LouisCAD · qwwdfsad · commit aad393b6aae1 · 2019-04-09T19:51:55.000+03:00
diff --git a/kotlinx-coroutines-core/common/src/flow/Flow.kt b/kotlinx-coroutines-core/common/src/flow/Flow.kt
@@ -27,7 +27,7 @@ import kotlinx.coroutines.*
  *
  * Flow does not carry information whether it is a cold stream (that can be collected multiple times and
  * triggers its evaluation every time collection is executed) or hot one, but conventionally flow represents a cold stream.
- * Transitions between hot and cold streams are support via channels and corresponding API: [flowViaChannel], [broadcastIn], [produceIn].
+ * Transitions between hot and cold streams are supported via channels and corresponding API: [flowViaChannel], [broadcastIn], [produceIn].
  *
  * Flow is a **pure** concept: it encapsulates its own execution context and never propagates it to the downstream, thus making
  * reasoning about execution context of particular transformations or terminal operations trivial.

Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,7 @@ import kotlinx.coroutines.*`
`27`	`27`	`*`
`28`	`28`	`* Flow does not carry information whether it is a cold stream (that can be collected multiple times and`
`29`	`29`	`* triggers its evaluation every time collection is executed) or hot one, but conventionally flow represents a cold stream.`
`30`		`- * Transitions between hot and cold streams are support via channels and corresponding API: [flowViaChannel], [broadcastIn], [produceIn].`
	`30`	`+ * Transitions between hot and cold streams are supported via channels and corresponding API: [flowViaChannel], [broadcastIn], [produceIn].`
`31`	`31`	`*`
`32`	`32`	`* Flow is a pure concept: it encapsulates its own execution context and never propagates it to the downstream, thus making`
`33`	`33`	`* reasoning about execution context of particular transformations or terminal operations trivial.`