nginx: removing one step from readme no longer necessary...

Author: andrecp

README.md

@@ -1,7 +1,8 @@
 ### Django tutorial using Docker, Nginx, Gunicorn and PostgreSQL.
 
-Trying to learn Django, Gunicorn, Docker and Nginx all at the same time?
-This is the right repo!
+This is Django tutorial in steroids, I wanted to go through the tutorial using a configuration that is more close to production.
+
+I am running the django app with gunicorn, using postgres as the database, the django app is behind nginx and everything is running out of Docker containers orchastrated with docker-compose.
 
 At the moment I am in the [Part 2 of Django tutorial](https://docs.djangoproject.com/en/1.8/intro/tutorial02/), will continue the quest and update the git repo accordingly. (Getting docker-compose and nginx right took some time)
 
@@ -12,7 +13,7 @@ I am running this on a Macbook air running Yosemite with boot2docker.
 1. git clone this repo
 2. boot2docker up
 3. sh rebuild_docker.sh
-4. run migrations in your Django instance: docker-compose run django /bin/sh -c 'cd mysite;python manage.py migrate'
+4. run migrations in your Django instance: ```docker-compose run django /bin/sh -c 'cd mysite;python manage.py migrate'```
 5. access it in your browser! http://192.168.59.103/ for me, run boot2docker ip to know where it is running.
 
 #### [docker-compose.yml](https://github.com/andrecp/django-tutorial-docker-nginx-postgres/blob/master/docker-compose.yml)
@@ -21,21 +22,28 @@ Compose is a tool for defining and running multi-container applications with Doc
 https://docs.docker.com/compose/
 
 We have three containers: Nginx, Postgres and a Django App.
+
 * django
-    Built from ./Dockerfile, running gunicorn to serve our django app.
+
+  - Built from ./Dockerfile, running gunicorn to serve our django app.
+
 * postgres
-    Just the basic image from DockerRegistry
+    - Just the basic image from DockerRegistry.
+
 * nginx
-    We are building it from nginx/Dockerfile, in our nginx/nginx.conf we are basically bypassing django and serving static files which gunicorn doesn't do for us.
+    - We are building it from nginx/Dockerfile. In our nginx/nginx.conf we are basically proxying django to gunicorn and serving static files which gunicorn doesn't do for us.
 
 #### rebuild_docker.sh
 Created to make life easier:
-1. docker-compose build
-    Builds your docker-compose file
-2. docker-compose up -d
-    Runs your containers on detached mode
-3. docker-compose ps
-    Check if they are all running
+
+1. Build your docker-compose file.
+  - docker-compose build
+
+2. Runs your containers on detached mode.
+  - docker-compose up -d
+
+3. Check if they are all running.
+  - docker-compose ps
 
 #### Important
 This project first started as me following the awesome introduction from Andrew T. Baker at the PyCon US 2015 [link](http://docker.atbaker.me/)