Merge pull request #2 from Resseguie/typo-fixes

simple typo fixes

Author: odewahn

public/building-images-with-dockerfiles.md

@@ -105,6 +105,5 @@ Notice that in this example we're running the Flask app directly when we start t
 Dockerfiles provide a relatively simple way to create a base image.  And, because you can use the FROM command to chain Dockerfiles together into increasingly complex images, you can do quite a lot, even with Docker's (refreshingly!) minimal command set.  But, if you already have an existing IA tool (and you should!), such as [Chef](http://www.getchef.com/), [Puppet](http://puppetlabs.com/), [Ansible](http://www.ansible.com/home), [Salt](http://www.saltstack.com/), it's very unlikely you could or even should rewrite everything.  So, if you're in this situation what can you do?
 
 
-
 I HAVE NO IDEA!  I NEED TO RESEARCH THIS MORE, BUT I THINK YOU CAN USE A TOOL LIKE [Packer](http://www.packer.io/). MAYBE I CAN CONVINCE Jeroen Janssens to do something with [his Ansible stuff](https://github.com/jeroenjanssens/data-science-at-the-command-line/tree/master/dst/build)
 

public/docker-images.md

@@ -59,6 +59,6 @@ Each line in the history corresponds to a commit of the image's filesystem.  The
 
 There are a couple of key things to understand about the layers in a docker images:
 
-* They can be reused.  Docker keeps track of all the layers you've pulled.  So, if two images happen to have a layer in common (for example, if two images are built form the same base box), Docker will reuse the common parts, and only pull the diffs.
+* They can be reused.  Docker keeps track of all the layers you've pulled.  So, if two images happen to have a layer in common (for example, if two images are built from the same base box), Docker will reuse the common parts, and only pull the diffs.
 * The layers are always additive, which can lead to really big sizes if you're not careful.  For example, if you download a large file, make a commit, delete the file, and then make another commit, that large file will still be present in the layer history.  We'll come back to this idea again, so don't worry if it doesn't make too much sense right now.  Just remember that layers are always additive.
 

public/dockerhub.md

@@ -12,15 +12,15 @@ There are two key ways to interact with the Docker Hub:
 * The Web interface, where you can register, manage image metadata (description, etc), add or remove collaborators, and so forth.  This is similar to GitHub.
 * The docker command line tool, where you can pull, push, or search for images.  This is similar to git.
 
-There are a number of features specific Docker.  One of the most interesting, [trusted builds](http://blog.docker.com/2013/11/introducing-trusted-builds/), allow you to create signed images based on a Dockerfile in GitHub or BitBucket.  As with a CI/CD tool, the trusted build is triggered by a post commit hook on your repo so that your image will also be up to date with your codebase. In addition, the image is flagged with a "trusted build" badge so that you can verity its source.
+There are a number of features specific to Docker.  One of the most interesting, [trusted builds](http://blog.docker.com/2013/11/introducing-trusted-builds/), allow you to create signed images based on a Dockerfile in GitHub or BitBucket.  As with a CI/CD tool, the trusted build is triggered by a post commit hook on your repo so that your image will also be up to date with your codebase. In addition, the image is flagged with a "trusted build" badge so that you can verity its source.
 
 ## Create an account
 
-The first to using Docker hub is to sign up, which you can do on their [Signup page](https://hub.docker.com/account/signup/).  You'll be asked for an email address, username, and a password.  Once you login, you'll see a project dashboard that's similar to other hosting sites:
+The first step to using Docker Hub is to sign up, which you can do on their [Signup page](https://hub.docker.com/account/signup/).  You'll be asked for an email address, username, and a password.  Once you log in, you'll see a project dashboard that's similar to other hosting sites:
 
 <img src="images/docker-hub.png"/>
 
-Once you've set up your account, you use the `docker login` command from your terminal so that you can pull and push images from your account.  (Note that you can also register with this command, as well, if you want to not use the site.)  Once you login, your docker will store your credentials in a file called `.dockercfg` in your home directory.
+Once you've set up your account, you use the `docker login` command from your terminal so that you can pull and push images from your account.  (Note that you can also register with this command, as well, if you want to not use the site.)  Once you log in, Docker will store your credentials in a file called `.dockercfg` in your home directory.
 
 ## Searching for images
 
@@ -82,14 +82,14 @@ As discussed in the chapter on images, you can also pull only the layers of the
 
 ## Pushing an Image
 
-Let's try to push an image to the hub.  Unlike the previous `search` and `pull` commands, you must be logged in to push.  If you're not already logged in, Docker will prompt you for your credentials
+Let's try to push an image to the Hub.  Unlike the previous `search` and `pull` commands, you must be logged in to push.  If you're not already logged in, Docker will prompt you for your credentials
 
 ```
 $ docker push simple_flask:latest
 2014/09/03 12:42:10 You cannot push a "root" repository. Please rename your repository in <user>/<repo> (ex: odewahn/simple_flask:latest)
 ```
 
-This rather self-explanatory error occurs because we didn't specify a username when we created the image.  To push to the Docker Hub, though, you must specify a username.  (Unless you're luck enough to be making Docker's official images, in which case you probably don't need this book!).  So, let's add our username using the `docker tag` command:
+This rather self-explanatory error occurs because we didn't specify a username when we created the image.  To push to the Docker Hub, though, you must specify a username.  (Unless you're lucky enough to be making Docker's official images, in which case you probably don't need this book!)  So, let's add our username using the `docker tag` command:
 
 ```
 $ docker tag simple_flask odewahn/simple_flask

public/example.md

@@ -9,7 +9,7 @@ Now that we've got the basics, let's make something a tiny bit more realistic: a
 * Start a new container based on our image
 * Access our app using a browser
 
-Again, the point here is not to show the best way to set up an environment, but instead to illustrate the Docker commands and what they do.  I'll code development environments in more detail later.
+Again, the point here is not to show the best way to set up an environment, but instead to illustrate the Docker commands and what they do.  I'll cover development environments in more detail later.
 
 ## Start the "simple\_flask" container
 

public/ipython-notebook.md

@@ -42,7 +42,7 @@ $ boot2docker stop
 
 ## Start a container
 
-Once you've got the image built, you're almost there.  Change int the directory that contains your notebooks and run this command.  *NB: you need Docker 1.3+ on a Mac or Linux for this to work* :
+Once you've got the image built, you're almost there.  Change into the directory that contains your notebooks and run this command.  *NB: you need Docker 1.3+ on a Mac or Linux for this to work* :
 
 ```
 docker run -it           \