diff --git a/get-started/part4.md b/get-started/part4.md
index a265960b6d..2431f20456 100644
--- a/get-started/part4.md
+++ b/get-started/part4.md
@@ -338,7 +338,7 @@ myvm2   -        hyperv   Running   tcp://192.168.200.181:2376           v17.06.
 
 Now that you have `myvm1`, you can use its powers as a swarm manager to
 deploy your app by using the same `docker stack deploy` command you used in part
-3 to `myvm1`, and your local copy of `docker-compose.yml.`. This command may take a few seconds
+3 to `myvm1`, and your local copy of `docker-compose.yml`. This command may take a few seconds
 to complete and the deployment takes some time to be available. Use the
 `docker service ps <service_name>` command on a swarm manager to verify that
 all services have been redeployed.
@@ -415,7 +415,7 @@ You can access your app from the IP address of **either** `myvm1` or `myvm2`.
 
 The network you created is shared between them and load-balancing. Run
 `docker-machine ls` to get your VMs' IP addresses and visit either of them on a
-browser, hitting refresh (or just `curl` them).
+browser on port 4000, hitting refresh (or just `curl` them).
 
 ![Hello World in browser](images/app-in-browser-swarm.png)