chapter 5: propose changes for what I take to be typos

Author: Andrew-Zipperer

chapter_05_post_and_database.asciidoc

@@ -355,7 +355,7 @@ def home_page(request):
 OK that gets our unit tests passing, but it's not really what we want.footnote:[
 But we _did_ learn about `request.method` and `request.POST` right?
 I know it might seem that I'm overdoing it,
-but doing things in tiny little really does have a lot of advantages,
+but doing things in tiny little steps really does have a lot of advantages,
 and one of them is that you can really think about (or in this case, learn)
 one thing at a time.]
 
@@ -633,7 +633,7 @@ on applying DRY too quickly.
 
 
 Now we get to the `self.fail('Finish the test!')`.
-If get rid of that and finish writing our FT,
+If we get rid of that and finish writing our FT,
 to add the check for adding a second item to the table
 (copy and paste is our friend),
 we begin to see that our first cut solution really isn't going to, um, cut it:
@@ -964,7 +964,7 @@ django.db.utils.OperationalError: no such table: lists_item
 ----
 
 In Django, the ORM's job is to model and read and write from database tables,
-but there's a second system that's in charge,of actually _creating_
+but there's a second system that's in charge of actually _creating_
 the tables in the database called "migrations".
 Its job is to let you to add, remove, and modify tables and columns,
 based on changes you make to your _models.py_ files.