diff --git a/docs/getting-started-guides/docker.md b/docs/getting-started-guides/docker.md
index afcb4f63e764c..9b252ec58bd25 100644
--- a/docs/getting-started-guides/docker.md
+++ b/docs/getting-started-guides/docker.md
@@ -131,7 +131,7 @@ echo $ip
 Hit the webserver with this IP:
 
 ```shell{% raw %}
-kubectl get svc nginx --template={{.spec.clusterIP}}
+curl $ip
 {% endraw %}```
 
 On OS X, since docker is running inside a VM, run the following command instead:
@@ -145,14 +145,14 @@ See [here](/docs/getting-started-guides/docker-multinode/deployDNS/) for instruc
 
 ### Turning down your cluster
 
-1. Delete all the containers including the kubelet:
+* Delete all the containers including the kubelet:
 
-Many of these containers run under the management of the `kubelet` binary, which attempts to keep containers running, even if they fail.
-So, in order to turn down the cluster, you need to first kill the kubelet container, and then any other containers.
-
-You may use `docker kill $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution.
+```shell
+docker rm -f kubelet
+docker rm -f `docker ps | grep k8s | awk '{print $1}'`
+```
 
-2. Cleanup the filesystem:
+* Cleanup the filesystem:
 
 On OS X, first ssh into the docker VM: