Merge branch 'main' of github.com:zipperer/Book-TDD-Web-Dev-Python into zipperer-main

Author: hjwp

chapter_04_philosophy_and_refactoring.asciidoc

@@ -716,7 +716,7 @@ NOTE: This is another distinction between FTs and unit tests;
     we use them as the primary tool for testing our UI,
     and the HTML that implements it.
 
-So, wanted an `<h1>`:
+So, we wanted an `<h1>`:
 
 [role="sourcecode"]
 .lists/templates/home.html (ch04l008)
@@ -916,7 +916,7 @@ but it should be enough to reassure ourselves that things are working.
 To get that functional test to green,
 we then enter into the lower-level unit tests cycle,
 where we put together all the moving parts required,
-add tests for all the edge cases.
+and add tests for all the edge cases.
 Any time we get to green & refactored at the unit tests level,
 we can pop back up to the FT level to guide us towards the
 next thing we need to work.

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.

chapter_06_explicit_waits_1.asciidoc

@@ -445,7 +445,7 @@ to separate the timing and re-raising logic from the test assertions.
 But we'll wait until we need it in multiple places.
 
 NOTE: If you've used Selenium before, you may know that it has a few
-    https://www.selenium.dev/documentation/webdriver/waits/#explicit-wait[helper functions to do waits].
+    https://www.selenium.dev/documentation/webdriver/waits/#explicit-waits[helper functions to do waits].
     I'm not a big fan of them, though not for any objective reason really.
     Over the course of the book we'll build a couple of wait helper tools
     which I think will make for nice, readable code,