Correct docs

- flatMapConcat is a shortcut for `map().flattenConcat()` and flatMapMerge is a shorcut for `map().flattenMerge()`

Author: yunjoo-park

docs/flow.md

@@ -1117,7 +1117,7 @@ as such, there is a family of flattening operators on flows.
 
 #### flatMapConcat
 
-Concatenating mode is implemented by [flatMapConcat] and [flattenConcat] operators. They are the most direct
+Concatenating mode is implemented by [map] and [flattenConcat] operators. They are the most direct
 analogues of the corresponding sequence operators. They wait for the inner flow to complete before
 starting to collect the next one as the following example shows:
 
@@ -1166,7 +1166,7 @@ The sequential nature of [flatMapConcat] is clearly seen in the output:
 
 Another flattening mode is to concurrently collect all the incoming flows and merge their values into
 a single flow so that values are emitted as soon as possible.
-It is implemented by [flatMapMerge] and [flattenMerge] operators. They both accept an optional 
+It is implemented by [map] and [flattenMerge] operators. They both accept an optional 
 `concurrency` parameter that limits the number of concurrent flows that are collected at the same time
 (it is equal to [DEFAULT_CONCURRENCY] by default). 
 

kotlinx-coroutines-core/common/src/flow/operators/Merge.kt

@@ -34,7 +34,7 @@ public val DEFAULT_CONCURRENCY: Int = systemProp(DEFAULT_CONCURRENCY_PROPERTY_NA
  * Transforms elements emitted by the original flow by applying [transform], that returns another flow,
  * and then concatenating and flattening these flows.
  *
- * This method is is a shortcut for `map(transform).flattenConcat()`. See [flattenConcat].
+ * This method is a shortcut for `map(transform).flattenConcat()`. See [flattenConcat].
  *
  * Note that even though this operator looks very familiar, we discourage its usage in a regular application-specific flows.
  * Most likely, suspending operation in [map] operator will be sufficient and linear transformations are much easier to reason about.