Merge remote-tracking branch 'rita/patch-5'

Author: hjwp

chapter_10_production_readiness.asciidoc

@@ -1,5 +1,5 @@
 [[chapter_10_production_readiness]]
-== Making our App Production-Ready
+== Making Our App Production-Ready
 
 .A Note for Early Release Readers
 ****
@@ -201,7 +201,7 @@ Ran 3 tests in 10.718s
 OK
 ----
 
-Phew.  Let's commit that
+Phew.  Let's commit that:
 
 [subs="specialcharacters,quotes"]
 ----
@@ -387,12 +387,13 @@ See http://www.clearlytech.com/2014/01/04/12-factor-apps-plain-english/[
 Another common way of handling this
 is to have different versions of _settings.py_ for dev and prod.
 That can work fine too, but it can get confusing to manage.
-Environment variables also have the advantage of working for non-Django stuff too...
+Environment variables also have the advantage of working for non-Django stuff too.
 ]
 
 
 ==== Setting DEBUG=True and SECRET_KEY
 
+//RITA: What do you mean by "this"? Please add a word or two for context.
 There's lots of ways you might do this.
 Here's what I propose; it may seem a little fiddly,
 but I'll provide a little justification for each choice.
@@ -470,7 +471,7 @@ $ pass:specialcharacters,quotes[*docker build -t superlists . && docker run \
 KeyError: 'DJANGO_SECRET_KEY'
 ----
 
-Ooops, and I forgot to set said secret key env var,
+Oops. I forgot to set said secret key env var,
 mere seconds after having dreamt it up!
 
 
@@ -505,7 +506,7 @@ AssertionError: 'To-Do' not found in 'Bad Request (400)'
 
 ==== ALLOWED_HOSTS is Required When Debug Mode is Turned Off
 
-Not quite!  Let's take a look manually: <<django-400-error>>.
+It's not quite working yet!  Let's take a look manually: <<django-400-error>>.
 
 [[django-400-error]]
 .An ugly 400 error
@@ -563,7 +564,7 @@ else:
 ====
 
 This is a setting that we want to change,
-depending on whether our docker image is running locally,
+depending on whether our Docker image is running locally,
 or on a server, so we'll use the `-e` flag again:
 
 
@@ -581,7 +582,7 @@ $ *docker build -t superlists . && docker run \
 ==== Collectstatic is Required when Debug is Turned Off
 
 An FT run (or just looking at the site) reveals that we've had a regression
-in our static files.
+in our static files:
 
 [role="small-code"]
 [subs="specialcharacters,macros"]
@@ -759,7 +760,7 @@ Traceback (most recent call last):
 django.db.utils.OperationalError: no such table: lists_list
 ----
 
-Re-create the datase with `./src/manage.py migrate` and we'll be back to a working state.
+Re-create the database with `./src/manage.py migrate` and we'll be back to a working state.
 
 Don't forget to commit our changes to _settings.py_,
 and I think we can call it job done!
@@ -768,6 +769,8 @@ when considering production-readiness,
 we've worked in small steps and used our tests all the way along,
 and we're now ready to deploy our container to a real server!
 
+Find out how, in our next exciting installment...
+
 
 [role="pagebreak-before less_space"]
 .Production-Readiness Config