diff --git a/akka-docs/rst/scala/code/docs/stream/io/StreamTcpDocSpec.scala b/akka-docs/rst/scala/code/docs/stream/io/StreamTcpDocSpec.scala
index cb8c8bd62b..0c5ec69e3e 100644
--- a/akka-docs/rst/scala/code/docs/stream/io/StreamTcpDocSpec.scala
+++ b/akka-docs/rst/scala/code/docs/stream/io/StreamTcpDocSpec.scala
@@ -133,8 +133,8 @@ class StreamTcpDocSpec extends AkkaSpec {
         .via(replParser)
 
       connection.join(repl).run()
+      //#repl-client
     }
-    //#repl-client
 
     serverProbe.expectMsg("Hello world")
     serverProbe.expectMsg("What a lovely day")
diff --git a/akka-docs/rst/scala/stream/stream-io.rst b/akka-docs/rst/scala/stream/stream-io.rst
index d43f941c2b..1131687c6e 100644
--- a/akka-docs/rst/scala/stream/stream-io.rst
+++ b/akka-docs/rst/scala/stream/stream-io.rst
@@ -52,7 +52,7 @@ Let's say we know a server has exposed a simple command line interface over TCP,
 and would like to interact with it using Akka Streams over TCP. To open an outgoing connection socket we use
 the ``outgoingConnection`` method:
 
-ąio/StreamTcpDocSpec.scala#repl-client
+.. includecode:: ../code/docs/stream/io/StreamTcpDocSpec.scala#repl-client
 
 The ``repl`` flow we use to handle the server interaction first prints the servers response, then awaits on input from
 the command line (this blocking call is used here just for the sake of simplicity) and converts it to a