added a deploy script and terminology section

Author: prakhar1989

README.md

@@ -49,6 +49,7 @@ This document contains a series of several sections, each of which explains a pa
     -	[Setting up your computer](#setup)
 -   [1.0 Playing with Busybox](#busybox)
     -   [1.1 Docker Run](#dockerrun)
+    -   [1.2 Terminology](#terminology)
 -   [Additional Resources](#resources)
 -   [References](#references)
 
@@ -107,7 +108,7 @@ ___________
 
 <a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="busybox"></a>
-## Playing with Busybox
+## 1.0 Playing with Busybox
 Now that we have everything setup, it's time to get our hands dirty. In this section, we are going to run a [Busybox](https://en.wikipedia.org/wiki/BusyBox) (a lightweight linux distribution) container on our system and get a taste of the `docker run` command.
 
 To get started, let's run the following in our terminal 
@@ -164,14 +165,25 @@ Running the `run` command with the `-it` flags attaches us to an interactive tty
 
 > **Danger Zone**: If you're feeling particularly adventureous you can try `rm -rf bin` in the container. Make sure you run this command in the container and **not** in your laptop. Doing this will not make any other commands like `ls`, `echo` work. Once everything stop working you can exit the container and then run it back up again with the `docker run -it busybox sh` command. Since docker creates a new container everytime, everything should start working back again.
 
-The `docker run` command is going to be command you'll be using the most so it makes sense to explore it in more detail.
+So that was a whirlwind tour of the mighty `docker run` command which would most likely be the command you'll most often. Hence it makes sense to spend some time getting comfortable with it. To find out more about `run`, use `docker run --help` to see a list of all flags it supports. As we proceed further, we'll see a few more variants of `docker run`.
+
+<a id="terminology"></a>
+### 1.2 Terminology
+In the last section, we used a lot of docker-specific jargon which might be confusing to some. So before we go further, let me clarify some terminology that is used frequently in the docker ecosystem.
+
+- *Images* - The blueprints of our application. Form the basis of containers.
+- *Containers* - Created from docker images and run the actual application.
+- *Docker Daemon* - The background service running on the host that manages building, running and distributing docker containers
+- *Docker Client* - The command line tool that allows the user to interact with the daemon.
+- *Docker hub* - A [registry](https://hub.docker.com/explore/) of docker images. 
 
 
 ___________
 <a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="resources"></a>
 ## Additional Resources
 - [Hello Docker Workshop](http://docker.atbaker.me/)
+- [Building a microservice with Node.js and Docker](https://www.youtube.com/watch?v=PJ95WY2DqXo)
 
 <a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="references"></a>

deploy

@@ -0,0 +1,8 @@
+#!/bin/bash
+
+git checkout gh-pages
+git merge master -m "merging master"
+git push origin gh-pages
+git checkout master
+
+echo "Deployed on http://prakhar.me/docker-curriculum"

index.html

@@ -361,6 +361,7 @@ <h2 id="table-of-contents">Table of Contents</h2>
 </li>
 <li><a href="#busybox">1.0 Playing with Busybox</a><ul>
 <li><a href="#dockerrun">1.1 Docker Run</a></li>
+<li><a href="#terminology">1.2 Terminology</a></li>
 </ul>
 </li>
 <li><a href="#resources">Additional Resources</a></li>
@@ -411,7 +412,7 @@ <h5 id="java">Java</h5>
 <hr />
 <p><a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="busybox"></a></p>
-<h2 id="playing-with-busybox">Playing with Busybox</h2>
+<h2 id="10-playing-with-busybox">1.0 Playing with Busybox</h2>
 <p>Now that we have everything setup, it's time to get our hands dirty. In this section, we are going to run a <a href="https://en.wikipedia.org/wiki/BusyBox">Busybox</a> (a lightweight linux distribution) container on our system and get a taste of the <code>docker run</code> command.</p>
 <p>To get started, let's run the following in our terminal </p>
 <pre><code>$ docker pull busybox
@@ -463,13 +464,24 @@ <h3 id="11-docker-run">1.1 Docker Run</h3>
 <blockquote>
 <p><strong>Danger Zone</strong>: If you're feeling particularly adventureous you can try <code>rm -rf bin</code> in the container. Make sure you run this command in the container and <strong>not</strong> in your laptop. Doing this will not make any other commands like <code>ls</code>, <code>echo</code> work. Once everything stop working you can exit the container and then run it back up again with the <code>docker run -it busybox sh</code> command. Since docker creates a new container everytime, everything should start working back again.</p>
 </blockquote>
-<p>The <code>docker run</code> command is going to be command you'll be using the most so it makes sense to explore it in more detail.</p>
+<p>So that was a whirlwind tour of the mighty <code>docker run</code> command which would most likely be the command you'll most often. Hence it makes sense to spend some time getting comfortable with it. To find out more about <code>run</code>, use <code>docker run --help</code> to see a list of all flags it supports. As we proceed further, we'll see a few more variants of <code>docker run</code>.</p>
+<p><a id="terminology"></a></p>
+<h3 id="12-terminology">1.2 Terminology</h3>
+<p>In the last section, we used a lot of docker-specific jargon which might be confusing to some. So before we go further, let me clarify some terminology that is used frequently in the docker ecosystem.</p>
+<ul>
+<li><em>Images</em> - The blueprints of our application. Form the basis of containers.</li>
+<li><em>Containers</em> - Created from docker images and run the actual application.</li>
+<li><em>Docker Daemon</em> - The background service running on the host that manages building, running and distributing docker containers</li>
+<li><em>Docker Client</em> - The command line tool that allows the user to interact with the daemon.</li>
+<li><em>Docker hub</em> - A <a href="https://hub.docker.com/explore/">registry</a> of docker images. </li>
+</ul>
 <hr />
 <p><a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="resources"></a></p>
 <h2 id="additional-resources">Additional Resources</h2>
 <ul>
 <li><a href="http://docker.atbaker.me/">Hello Docker Workshop</a></li>
+<li><a href="https://www.youtube.com/watch?v=PJ95WY2DqXo">Building a microservice with Node.js and Docker</a></li>
 </ul>
 <p><a href="#table-of-contents" class="top" id="preface">Top</a>
 <a id="references"></a></p>