fix typos, word repetitions, missing characters

Author: Xronophobe

chapter_09_docker.asciidoc

@@ -325,7 +325,7 @@ and where testing fits in.
 
 **Third chapter: Automated deployment to real servers**
 
-* Gradually build up an Ansible playbook to deplor our containers on a real server
+* Gradually build up an Ansible playbook to deploy our containers on a real server
 
 * Again, use our FTs to check for any problems
 
@@ -386,7 +386,7 @@ and to use a real server instead.
     our "real" server.
 
 
-NOTE: A clarification: in these chapter,
+NOTE: A clarification: in these chapters,
     we run tests _against_ our Docker container, or _against_ our staging server,
     but that doesn't mean we run the tests _from_ Docker or _from_ our staging server.
     We still run the tests from our own laptop,
@@ -407,7 +407,7 @@ OK
 
 And now we can try them against our docker server URL,
 which once we've done the right docker magic,
-will be at _http://locahost:8888_
+will be at _http://localhost:8888_
 
 TIP: I'm deliberately choosing a different port to run Dockerised Django on (8888)
     from the default port that a local `manage.py runserver` would choose (8080),
@@ -436,7 +436,7 @@ test_can_start_a_todo_list
 selenium.common.exceptions.WebDriverException: Message: Reached error page: abo
 ut:neterror?e=connectionFailure&u=http%3A//localhost:8888/&c=UTF-8&
 f=regular&d=Firefox%20can%27t%20establish%20a%20connection%20to%20the%20server%
-20at%20locahost.
+20at%20localhost.
 
 
 Ran 1 tests in 5.518s
@@ -542,7 +542,7 @@ so I decided to stick with Docker. But you could definitely check it out!
 
 You can follow along all the instructions in the book
 by just substituing the `docker` binary for `podman` in all the CLI instructions,
-eg
+e.g.
 
 [role="skipme"]
 [subs="specialcharacters,quotes"]
@@ -711,7 +711,7 @@ rather than just manually pip installing things
 one by one, and having to remember to sync things
 between local dev and docker,
 we can "save" the list of packages we're using
-by creating a 'requirements.txt' filefootnote:[
+by creating a 'requirements.txt' file.footnote:[
 There are many other dependency management tools these days
 so requirements.txt is not the only way to do it,
 although it is one of the oldest and best established.
@@ -1116,13 +1116,13 @@ curl: (52) Empty reply from server
 ==== Essential Googling the Error Message
 
 The need to map ports and the `-p` argument to `docker run` are something you just learn,
-fairly on in learning Docker.  But the next debugging step is quite a bit more obscure
+fairly early on in learning Docker.  But the next debugging step is quite a bit more obscure
 (although admittedly Itamar does address it in his
 https://pythonspeed.com/articles/docker-connection-refused/[docker networking article],
 did I already mention how excellent it is?).
 
 
-But if we haven't read that, we can always resort to resort to the tried and tested "Googling the error message" technique instead
+But if we haven't read that, we can always resort to the tried and tested "Googling the error message" technique instead
 (<<googling-the-error>>).
 
 
@@ -1189,7 +1189,7 @@ Looking good!
 .On Debugging
 *******************************************************************************
 Let me let you in on a little secret.  I'm actually bad at debugging.
-We all have our psychological strengths and weakness,
+We all have our psychological strengths and weaknesses,
 and one of my weaknesses is
 that when I run into a problem I can't see an obvious solution to,
 I want to throw up my hands way too soon
@@ -1285,7 +1285,7 @@ Run 'python manage.py migrate' to apply them.
 
 NOTE: If you don't see this error,
     it's because your src folder had the database file in it, unlike mine.
-    For the sake of argument, run `rm src/db.sqlite` and re-run the build & run commands,
+    For the sake of argument, run `rm src/db.sqlite3` and re-run the build & run commands,
     and you should be able to repro the error.  I promise it's instructive!
 
 
@@ -1371,13 +1371,14 @@ Running migrations:
   Applying contenttypes.0001_initial... OK
 [...]
   Applying sessions.0001_initial... OK
-[...]
 $ *docker build -t superlists . && docker run \
   -p 8888:8888 \
   -v ./src/db.sqlite3:/src/db.sqlite3 \
   -it superlists*
 ----
 
+//CSANAD: sessions.0001_initial is the last migration on the last line, removed `[...]`
+
 TIP: if you see an error saying: `django.db.utils.OperationalError`: "unable to open database file",
     try stopping the container, `rm -rf src/db.sqlite3`, then re-run the migrate command
     _outside_ the container, and the rebuild and run your image.
@@ -1435,7 +1436,7 @@ Tests and small steps some of the uncertainty out of deployment::
     For developers, ops and infra work is always "fun",
     by which I mean a process full of uncertainty and surprises.
     My aim during this chapter was to show that a step-by-step approach
-    helps to minimse risk, especially when allied to a functional test suite
+    helps to minimise risk, especially when allied to a functional test suite
     that can help us to catch errors early.
 
 // TODO amend the rest