diff --git a/engine/userguide/networking/get-started-overlay.md b/engine/userguide/networking/get-started-overlay.md
index c7b917b146..b1fd04f9ba 100644
--- a/engine/userguide/networking/get-started-overlay.md
+++ b/engine/userguide/networking/get-started-overlay.md
@@ -142,7 +142,7 @@ that machine options that are needed by the `overlay` network driver.
 		--engine-opt="cluster-advertise=eth1:2376" \
 		mhs-demo0
 
-	At creation time, you supply the Engine `daemon` with the ` --cluster-store` option. This option tells the Engine the location of the key-value store for the `overlay` network. The bash expansion `$(docker-machine ip mh-keystore)` resolves to the IP address of the Consul server you created in "STEP 1". The `--cluster-advertise` option advertises the machine on the network.
+	At creation time, you supply the Engine `daemon` with the `--cluster-store` option. This option tells the Engine the location of the key-value store for the `overlay` network. The bash expansion `$(docker-machine ip mh-keystore)` resolves to the IP address of the Consul server you created in "STEP 1". The `--cluster-advertise` option advertises the machine on the network.
 
 2. Create another host and add it to the swarm cluster.
 
@@ -372,13 +372,13 @@ to have external connectivity outside of their cluster.
 
 ### Extra Credit with Docker Compose
 
-Please refer to the Networking feature introduced in [Compose V2 format]
-(https://docs.docker.com/compose/networking/) and execute the
-multi-host networking scenario in the swarm cluster used above.
+Please refer to the Networking feature introduced in
+[Compose V2 format](/compose/networking/)
+and execute the multi-host networking scenario in the swarm cluster used above.
 
 ## Related information
 
 * [Understand Docker container networks](index.md)
 * [Work with network commands](work-with-networks.md)
 * [Docker Swarm overview](/swarm)
-* [Docker Machine overview](/machine)
\ No newline at end of file
+* [Docker Machine overview](/machine)