diff --git a/akka-docs/src/main/paradox/java/stream/stream-composition.md b/akka-docs/src/main/paradox/java/stream/stream-composition.md
index 7179dce1b6..8c785f72a4 100644
--- a/akka-docs/src/main/paradox/java/stream/stream-composition.md
+++ b/akka-docs/src/main/paradox/java/stream/stream-composition.md
@@ -283,7 +283,7 @@ of combining materialized values without nesting and hierarchy involved.
 We have seen that we can use `named()` to introduce a nesting level in the fluid DSL (and also explicit nesting by using
 `create()` from `GraphDSL`). Apart from having the effect of adding a nesting level, `named()` is actually
 a shorthand for calling `withAttributes(Attributes.name("someName"))`. Attributes provide a way to fine-tune certain
-aspects of the materialized running entity. For example buffer sizes for asynchronous stagescan be controlled via
+aspects of the materialized running entity. For example buffer sizes for asynchronous stages can be controlled via
 attributes (see @ref:[Buffers for asynchronous stages](stream-rate.md#async-stream-buffers)). When it comes to hierarchic composition, attributes are inherited
 by nested modules, unless they override them with a custom value.
 
@@ -304,4 +304,4 @@ except the `map` stage which has again an explicitly provided attribute overridi
 |
 
 This diagram illustrates the inheritance process for the example code (representing the materializer default attributes
-as the color *red*, the attributes set on `nestedSink` as *blue* and the attributes set on `nestedFlow` as *green*).
\ No newline at end of file
+as the color *red*, the attributes set on `nestedSink` as *blue* and the attributes set on `nestedFlow` as *green*).