Updated Docker ReadMe

Author: mdmintz

Docker_README.md

@@ -6,41 +6,41 @@
 
     docker-machine create --driver virtualbox seleniumbase
 
-#### 3. If your Docker environment ever goes down for any reason, you can bring it back up with a restart:
+##### (If your Docker environment ever goes down for any reason, you can bring it back up with a restart.)
 
     docker-machine restart seleniumbase
 
-#### 4. Configure your shell:
+#### 3. Configure your shell:
 
     eval "$(docker-machine env seleniumbase)"
 
-#### 5. Go to the SeleniumBase home directory. (That's where "Dockerfile" is located)
+#### 4. Go to the SeleniumBase home directory. (That's where "Dockerfile" is located)
 
-#### 6. Create your Docker image from your Dockerfile: (Get ready to wait awhile)
+#### 5. Create your Docker image from your Dockerfile: (Get ready to wait awhile)
 
     docker build -t seleniumbase .
 
-#### 7. Run a test inside your Docker: (Once the test completes after a few seconds, you'll automatically exit the Docker shell)
+#### 6. Run a test inside your Docker: (Once the test completes after a few seconds, you'll automatically exit the Docker shell)
 
     docker run seleniumbase ./run_docker_test_in_firefox.sh
 
-#### 8. Now run the same test with Chrome inside your Docker:
+#### 7. Now run the same test with Chrome inside your Docker:
 
     docker run seleniumbase ./run_docker_test_in_chrome.sh
 
-#### 9. You can also enter Docker and stay inside the shell:
+#### 8. You can also enter Docker and stay inside the shell:
 
     docker run -i -t seleniumbase
 
-#### 10. Now you can run the example test from inside the Docker shell: (This time with PhantomJS)
+#### 9. Now you can run the example test from inside the Docker shell:
 
-    ./run_docker_test_in_phantomjs.sh
+    ./run_docker_test_in_chrome.sh
 
-#### 11. When you're satisfied, you may exit the Docker shell:
+#### 10. When you're satisfied, you may exit the Docker shell:
 
     exit
 
-#### 12. (Optional) Since Docker images and containers take up a lot of space, you may want to clean up your machine from time to time when they’re not being used:
+#### 11. (Optional) Since Docker images and containers take up a lot of space, you may want to clean up your machine from time to time when they’re not being used:
 http://stackoverflow.com/questions/17236796/how-to-remove-old-docker-containers
 Here are a few of those cleanup commands:
 
@@ -57,7 +57,7 @@ Finally, if you want to wipe out your SeleniumBase Docker virtualbox, use these
     docker-machine kill seleniumbase
     docker-machine rm seleniumbase
 
-#### 13. (Optional) More reading on Docker can be found here:
+#### 12. (Optional) More reading on Docker can be found here:
 * https://docs.docker.com
 * https://docs.docker.com/mac/started/
 * https://docs.docker.com/installation/mac/

docker/ReadMe.md

@@ -6,41 +6,41 @@
 
     docker-machine create --driver virtualbox seleniumbase
 
-#### 3. If your Docker environment ever goes down for any reason, you can bring it back up with a restart:
+##### (If your Docker environment ever goes down for any reason, you can bring it back up with a restart.)
 
     docker-machine restart seleniumbase
 
-#### 4. Configure your shell:
+#### 3. Configure your shell:
 
     eval "$(docker-machine env seleniumbase)"
 
-#### 5. Go to the SeleniumBase home directory. (That's where "Dockerfile" is located)
+#### 4. Go to the SeleniumBase home directory. (That's where "Dockerfile" is located)
 
-#### 6. Create your Docker image from your Dockerfile: (Get ready to wait awhile)
+#### 5. Create your Docker image from your Dockerfile: (Get ready to wait awhile)
 
     docker build -t seleniumbase .
 
-#### 7. Run a test inside your Docker: (Once the test completes after a few seconds, you'll automatically exit the Docker shell)
+#### 6. Run a test inside your Docker: (Once the test completes after a few seconds, you'll automatically exit the Docker shell)
 
     docker run seleniumbase ./run_docker_test_in_firefox.sh
 
-#### 8. Now run the same test with Chrome inside your Docker:
+#### 7. Now run the same test with Chrome inside your Docker:
 
     docker run seleniumbase ./run_docker_test_in_chrome.sh
 
-#### 9. You can also enter Docker and stay inside the shell:
+#### 8. You can also enter Docker and stay inside the shell:
 
     docker run -i -t seleniumbase
 
-#### 10. Now you can run the example test from inside the Docker shell: (This time with PhantomJS)
+#### 9. Now you can run the example test from inside the Docker shell:
 
-    ./run_docker_test_in_phantomjs.sh
+    ./run_docker_test_in_chrome.sh
 
-#### 11. When you're satisfied, you may exit the Docker shell:
+#### 10. When you're satisfied, you may exit the Docker shell:
 
     exit
 
-#### 12. (Optional) Since Docker images and containers take up a lot of space, you may want to clean up your machine from time to time when they’re not being used:
+#### 11. (Optional) Since Docker images and containers take up a lot of space, you may want to clean up your machine from time to time when they’re not being used:
 http://stackoverflow.com/questions/17236796/how-to-remove-old-docker-containers
 Here are a few of those cleanup commands:
 
@@ -57,7 +57,7 @@ Finally, if you want to wipe out your SeleniumBase Docker virtualbox, use these
     docker-machine kill seleniumbase
     docker-machine rm seleniumbase
 
-#### 13. (Optional) More reading on Docker can be found here:
+#### 12. (Optional) More reading on Docker can be found here:
 * https://docs.docker.com
 * https://docs.docker.com/mac/started/
 * https://docs.docker.com/installation/mac/