=doc Correct minor typo (#20897)
* Correct minor typo * Fix minor typos
This commit is contained in:
parent
334959edd1
commit
625413e413
4 changed files with 6 additions and 6 deletions
|
|
@ -177,7 +177,7 @@ Triggering the flow of elements programmatically
|
|||
In other words, even if the stream would be able to flow (not being backpressured) we want to hold back elements until a
|
||||
trigger signal arrives.
|
||||
|
||||
This recipe solves the problem by simply zipping the stream of ``Message`` elments with the stream of ``Trigger``
|
||||
This recipe solves the problem by simply zipping the stream of ``Message`` elements with the stream of ``Trigger``
|
||||
signals. Since ``Zip`` produces pairs, we simply map the output stream selecting the first element of the pair.
|
||||
|
||||
.. includecode:: ../code/docs/stream/javadsl/cookbook/RecipeManualTrigger.java#manually-triggered-stream
|
||||
|
|
@ -227,7 +227,7 @@ a special ``reduce`` operation that collapses multiple upstream elements into on
|
|||
the speed of the upstream unaffected by the downstream.
|
||||
|
||||
When the upstream is faster, the reducing process of the ``conflate`` starts. Our reducer function simply takes
|
||||
the freshest element. This cin a simple dropping operation.
|
||||
the freshest element. This in a simple dropping operation.
|
||||
|
||||
.. includecode:: ../code/docs/stream/javadsl/cookbook/RecipeSimpleDrop.java#simple-drop
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Introduction
|
|||
Motivation
|
||||
==========
|
||||
|
||||
The way we consume services from the internet today includes many instances of
|
||||
The way we consume services from the Internet today includes many instances of
|
||||
streaming data, both downloading from a service as well as uploading to it or
|
||||
peer-to-peer data transfers. Regarding data as a stream of elements instead of
|
||||
in its entirety is very useful because it matches the way computers send and
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ Triggering the flow of elements programmatically
|
|||
In other words, even if the stream would be able to flow (not being backpressured) we want to hold back elements until a
|
||||
trigger signal arrives.
|
||||
|
||||
This recipe solves the problem by simply zipping the stream of ``Message`` elments with the stream of ``Trigger``
|
||||
This recipe solves the problem by simply zipping the stream of ``Message`` elements with the stream of ``Trigger``
|
||||
signals. Since ``Zip`` produces pairs, we simply map the output stream selecting the first element of the pair.
|
||||
|
||||
.. includecode:: ../code/docs/stream/cookbook/RecipeManualTrigger.scala#manually-triggered-stream
|
||||
|
|
@ -222,7 +222,7 @@ a special ``reduce`` operation that collapses multiple upstream elements into on
|
|||
the speed of the upstream unaffected by the downstream.
|
||||
|
||||
When the upstream is faster, the reducing process of the ``conflate`` starts. Our reducer function simply takes
|
||||
the freshest element. This cin a simple dropping operation.
|
||||
the freshest element. This in a simple dropping operation.
|
||||
|
||||
.. includecode:: ../code/docs/stream/cookbook/RecipeSimpleDrop.scala#simple-drop
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Introduction
|
|||
Motivation
|
||||
==========
|
||||
|
||||
The way we consume services from the internet today includes many instances of
|
||||
The way we consume services from the Internet today includes many instances of
|
||||
streaming data, both downloading from a service as well as uploading to it or
|
||||
peer-to-peer data transfers. Regarding data as a stream of elements instead of
|
||||
in its entirety is very useful because it matches the way computers send and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue