From e4077cc14f47474ffb4a1dc35dcd4344c424382d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A1szl=C3=B3=20van=20den=20Hoek?= Date: Fri, 23 Jun 2017 12:07:07 +0200 Subject: [PATCH] fix typo (mather -> matter) (#23221) --- akka-docs/src/main/paradox/scala/stream/stages-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/scala/stream/stages-overview.md b/akka-docs/src/main/paradox/scala/stream/stages-overview.md index 42003e7c36..b409c55b68 100644 --- a/akka-docs/src/main/paradox/scala/stream/stages-overview.md +++ b/akka-docs/src/main/paradox/scala/stream/stages-overview.md @@ -1096,7 +1096,7 @@ operation at the same time (usually handling the completion of a @scala[`Future` Pass incoming elements to a function that return a @scala[`Future`] @java[`CompletionStage`] result. When the @scala[`Future`] @java[`CompletionStage`] arrives the result is passed downstream. Up to `n` elements can be processed concurrently, but regardless of their completion time the incoming -order will be kept when results complete. For use cases where order does not mather `mapAsyncUnordered` can be used. +order will be kept when results complete. For use cases where order does not matter `mapAsyncUnordered` can be used. If a @scala[`Future`] @java[`CompletionStage`] fails, the stream also fails (unless a different supervision strategy is applied)