Merge pull request #233 from zipperer/main

chapters 8 and 9: propose a few small edits

Author: hjwp

chapter_08_prettification.asciidoc

@@ -88,7 +88,7 @@ Here are a few things we might want:
 //      including Django documentation or learnpython.org
 //      Both look completely different today - not so ugly anymore
 
-* A nice large input field for adding new and existing lists
+* A nice large input field for adding to new and existing lists
 * A large, attention-grabbing, centered box to put it in
 
 ((("aesthetics, testing", seealso="design and layout testing")))

chapter_09_docker.asciidoc

@@ -61,7 +61,7 @@ and this is a very new draft.
 What that means is that I'd, really, really love feedback from readers.
 Please have a go at following along and let me know what you think!
 I'm [email protected], or you can open up
-https://github.com/hjwp/Book-TDD-Web-Dev-Python/issues[GitHub Issue]
+https://github.com/hjwp/Book-TDD-Web-Dev-Python/issues[GitHub Issues]
 or Pull Requests.
 
 Let me know how you got on, if you get stuck on anything,
@@ -861,6 +861,7 @@ The docker daemon lets you list all the currently running containers
 with `docker ps`:
 
 [role="skipme small-code"]
+[subs="quotes"]
 ----
 $ *docker ps*
 CONTAINER ID   IMAGE        COMMAND                  CREATED         STATUS         PORTS     NAMES
@@ -873,8 +874,9 @@ and a randomly-generated name (you can override that if you want to).
 We can use the ID or the name to kill the container with `docker kill`:
 
 [role="skipme"]
+[subs="quotes"]
 ----
-$ docker kill 0818e1b8e9bf
+$ *docker kill 0818e1b8e9bf*
 0818e1b8e9bf
 ----
 
@@ -904,7 +906,7 @@ What's going on here?  Time for a little debugging.
 
 
 
-=== Debugging a Container Networking Problems
+=== Debugging Container Networking Problems
 
 First, let's try and take a look ourselves, in our browser, by going to http://localhost:8888/:
 
@@ -955,7 +957,7 @@ Starting development server at http://127.0.0.1:8888/
 
 A quick run of the FT or check in our browser will show us that nope, that doesn't work either.
 Let's try an even lower-level smoke test, the traditional Unix utility `curl`.
-It's a command-line tool for making HTTP requests.  Try it on your own computer first:
+It's a command-line tool for making HTTP requests.footnote:[`curl` can make many other types of requests. For details see https://man7.org/linux/man-pages/man1/curl.1.html[curl manual].]  Try it on your own computer first:
 
 [role="ignore-errors"]
 [subs="specialcharacters,macros"]
@@ -1484,7 +1486,7 @@ Tests and small steps take some of the uncertainty out of deployment::
 
 Some typical pain points--networking, ports, static files, and the database::
     Moving from the local django development server to a container
-    is chance to rehearse the fiddliness of configuring networking
+    is a chance to rehearse the fiddliness of configuring networking
     in a deployed environment.
     It's also a chance to think about persistence and the database,
     and some configuration issues like static files.