Documentation fixes (#25725)

* tread -> thread
This commit is contained in:
Matt Kohl 2018-10-04 09:37:42 +01:00 committed by Patrik Nordwall
parent 272cceb12b
commit c89b4a1884
2 changed files with 4 additions and 3 deletions

View file

@ -5,7 +5,7 @@ dispatcher configured through the `akka.stream.blocking-io-dispatcher`.
@@@ warning
Be aware that `asInputStream` and `asOutputStream` materialize `InputStream` and `OutputStream` respectively as
blocking API implementation. They will block tread until data will be available from upstream.
blocking API implementation. They will block the thread until data will be available from upstream.
Because of blocking nature these objects cannot be used in `mapMaterializeValue` section as it causes deadlock
of the stream materialization process.
For example, following snippet will fall with timeout exception:

View file

@ -74,7 +74,7 @@ dispatcher configured through the `akka.stream.blocking-io-dispatcher`.
@@@ warning
Be aware that `asInputStream` and `asOutputStream` materialize `InputStream` and `OutputStream` respectively as
blocking API implementation. They will block tread until data will be available from upstream.
blocking API implementation. They will block the thread until data will be available from upstream.
Because of blocking nature these objects cannot be used in `mapMaterializeValue` section as it causes deadlock
of the stream materialization process.
For example, following snippet will fall with timeout exception:
@ -89,6 +89,7 @@ For example, following snippet will fall with timeout exception:
@@@
| |Operator|Description|
|--|--|--|
|StreamConverters|<a name="asinputstream"></a>@ref[asInputStream](StreamConverters/asInputStream.md)|Create a sink which materializes into an `InputStream` that can be read to trigger demand through the sink.|