diff --git a/akka-docs/rst/java/stream/stream-flows-and-basics.rst b/akka-docs/rst/java/stream/stream-flows-and-basics.rst index 2e68327e57..46ed3e169b 100644 --- a/akka-docs/rst/java/stream/stream-flows-and-basics.rst +++ b/akka-docs/rst/java/stream/stream-flows-and-basics.rst @@ -234,7 +234,7 @@ consequences: * starting up a stream may take longer than before due to executing the fusion algorithm * passing elements from one processing stage to the next is a lot faster between fused stages due to avoiding the asynchronous messaging overhead - * fused stream processing stages do no longer run in parallel to each other, meaning that + * fused stream processing stages no longer run in parallel to each other, meaning that only up to one CPU core is used for each fused part The first point can be countered by pre-fusing and then reusing a stream blueprint as sketched below: diff --git a/akka-docs/rst/scala/stream/stream-flows-and-basics.rst b/akka-docs/rst/scala/stream/stream-flows-and-basics.rst index a2e7fa9236..4c840433b9 100644 --- a/akka-docs/rst/scala/stream/stream-flows-and-basics.rst +++ b/akka-docs/rst/scala/stream/stream-flows-and-basics.rst @@ -236,7 +236,7 @@ consequences: * starting up a stream may take longer than before due to executing the fusion algorithm * passing elements from one processing stage to the next is a lot faster between fused stages due to avoiding the asynchronous messaging overhead - * fused stream processing stages do no longer run in parallel to each other, meaning that + * fused stream processing stages no longer run in parallel to each other, meaning that only up to one CPU core is used for each fused part The first point can be countered by pre-fusing and then reusing a stream blueprint as sketched below: