diff --git a/akka-docs/src/main/paradox/stream/stream-composition.md b/akka-docs/src/main/paradox/stream/stream-composition.md
index ebef7a762e..2d967b0f11 100644
--- a/akka-docs/src/main/paradox/stream/stream-composition.md
+++ b/akka-docs/src/main/paradox/stream/stream-composition.md
@@ -54,8 +54,8 @@ parameters.
 Please note that when combining a `Flow` using that method, the termination signals are not carried 
 "through" as the `Sink` and `Source` are assumed to be fully independent. If however you want to construct
 a `Flow` like this but need the termination events to trigger "the other side" of the composite flow, you can use
-`CoupledTerminationFlow.fromSinkAndSource` which does just that. For example the cancelation of the composite flows 
-source-side will then lead to completion of its sink-side. Read `CoupledTerminationFlow`'s scaladoc for a 
+`Flow.fromSinkAndSourceCoupled` or `Flow.fromSinkAndSourceCoupledMat` which does just that. For example the cancelation of the composite flows 
+source-side will then lead to completion of its sink-side. Read @apidoc[Flow]'s API documentation for a 
 detailed explanation how this works.
 
 The example `BidiFlow` demonstrates that internally a module can be of arbitrary complexity, and the exposed