Rita edits ch 10

Author: ritaf-ORM

chapter_10_production_readiness.asciidoc

@@ -1,5 +1,5 @@
 [[chapter_10_production_readiness]]
-== Making our App Production-Ready
+== Making Our App Production-Ready
 
 Our container is working fine but it's not production-ready.
 Let's try to get it there, using the tests to keep us safe.
@@ -21,7 +21,7 @@ This chapter is still very fresh,
 but the content is all there,
 so you should be able to follow along.
 
-But as always I really, really need fedback.
+But as always I really, really need feedback.
 So please hit me up at [email protected], or via
 https://github.com/hjwp/Book-TDD-Web-Dev-Python/issues[GitHub Issues]
 and Pull Requests.
@@ -58,6 +58,7 @@ an ORM, all sorts of middleware, the admin site...
 "What else do you want, a pony?" Well, Gunicorn stands for "Green Unicorn",
 which I guess is what you'd want next if you already had a pony...
 
+//RITA: Was cmdg intentional?
 //001
 cmdg
 
@@ -182,7 +183,7 @@ Ran 3 tests in 10.718s
 OK
 ----
 
-Phew.  Let's commit that
+Phew.  Let's commit that:
 
 [subs="specialcharacters,quotes"]
 ----
@@ -218,12 +219,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.
@@ -301,7 +303,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!
 
 
@@ -335,7 +337,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
@@ -393,7 +395,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:
 
 
@@ -410,7 +412,7 @@ $ *docker build -t superlists . && \
 ==== 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"]
@@ -456,7 +458,7 @@ OK
 
 We have a container that we're ready to ship to production!
 
-Find out how in the next exciting installment...
+Find out how in the next exciting chapter installment...