diff --git a/get-started/part2.md b/get-started/part2.md
index 1bae288a77..82a010991b 100644
--- a/get-started/part2.md
+++ b/get-started/part2.md
@@ -185,6 +185,8 @@ REPOSITORY            TAG                 IMAGE ID
 friendlyhello         latest              326387cea398
 ```
 
+> **Tip**: You can use the commands `docker images` or the newer `docker image ls` list images. They give you the same output.
+
 ## Run the app
 
 Run the app, mapping your machine's port 4000 to the container's published port
@@ -239,10 +241,10 @@ CONTAINER ID        IMAGE               COMMAND             CREATED
 
 You'll see that `CONTAINER ID` matches what's on `http://localhost:4000`.
 
-Now use `docker stop` to end the process, using the `CONTAINER ID`, like so:
+Now use `docker container stop` to end the process, using the `CONTAINER ID`, like so:
 
 ```shell
-docker stop 1fa4ab2cf395
+docker container stop 1fa4ab2cf395
 ```
 
 ## Share your image
diff --git a/get-started/part3.md b/get-started/part3.md
index fbd4a3bf11..4016f3a6d2 100644
--- a/get-started/part3.md
+++ b/get-started/part3.md
@@ -201,12 +201,18 @@ load-balancing; with each request, one of the 5 replicas is chosen, in a
 round-robin fashion, to respond. The container IDs will match your output from
 the previous command (`docker container ls -q`).
 
+(Windows 10 PowerShell should already have `curl` available, but if not you can
+grab a Linux terminal emulater like [Git
+BASH](https://git-for-windows.github.io/){: target="_blank" class="_"} if you
+want to try it out. It isn't critical to the taskflow here.)
+
 >**Note**: At this stage, it may take up to 30 seconds for the containers
 to respond to HTTP requests. This is not indicative of Docker or
 swarm performance, but rather an unmet Redis dependency that we will
 address later in the tutorial. For now, the visitor counter isn't working
 for the same reason; we haven't yet added a service to persist data.
 
+
 ## Scale the app
 
 You can scale the app by changing the `replicas` value in `docker-compose.yml`,
diff --git a/get-started/part4.md b/get-started/part4.md
index c0776c470c..deee71b499 100644
--- a/get-started/part4.md
+++ b/get-started/part4.md
@@ -343,8 +343,8 @@ And that's it, the app is deployed on a swarm cluster!
 
 Now you can use the same [docker commands you used in part
 3](/get-started/part3.md#run-your-new-load-balanced-app). Only this time you'll
-see that the containers have been distributed between both `myvm1` and `myvm2`.
-
+see that the services (and associated containers) have been distributed between
+both `myvm1` and `myvm2`.
 
 ```
 $ docker stack ps getstartedlab
@@ -357,6 +357,8 @@ ghii74p9budx  test_web.4  username/repo:tag  myvm1  Running
 0prmarhavs87  test_web.5  username/repo:tag  myvm2  Running
 ```
 
+You can also run `docker container ls` to view container IDs.
+
 > Connecting to VMs with `docker-machine env` and `docker-machine ssh`
 >
 > * To set your shell to talk to a different machine like `myvm2`, simply re-run