fix typos

Author: Xronophobe

chapter_19_spiking_custom_auth.asciidoc

@@ -111,7 +111,7 @@ and convince yourself that it really does work.
 
 ((("spiking and de-spiking", "branching your VCS")))
 ((("Git", "creating branches")))
-This spike is going to be a bit more involved that the last one,
+This spike is going to be a bit more involved than the last one,
 so we'll be a little more rigorous with our version control.
 
 Before embarking on a spike it's a good idea to start a new branch,
@@ -178,15 +178,15 @@ and a logout link for users who are already authenticated:
 ((("Django framework", "sending emails", id="DFemail18")))
 ((("send_mail function", id="sendmail18")))
 ((("emails, sending from Django", id="emails18")))
-The login theory will be something like this:
+The login in theory will be something like this:
 
 - When someone wants to log in, we generate a unique secret token for them,
   store it in the database linked to their email, and send it to them.
 
 - The user then checks their email,
   which will have a link to a URL that includes that token.
 
-- When they click that link, we check whether the token exists in database,
+- When they click that link, we check whether the token exists in the database,
   and if so, they are logged in as the associated user.
 
 // https://docs.djangoproject.com/en/5.0/topics/auth/customizing/
@@ -296,7 +296,7 @@ with our 'base.html' in the real version.)
 
 The https://docs.djangoproject.com/en/5.1/topics/email/[django docs on email]
 explain how `send_mail()` works, as well as how you configure it
-by telling Django what email to server to use,
+by telling Django what email server to use,
 and how to authenticate with it.
 I'm just using my Gmailfootnote:[
 Didn't I just spend a whole intro banging on about the privacy implications
@@ -542,7 +542,7 @@ $ pass:quotes[*python src/manage.py migrate*]
 Running migrations:
   Applying accounts.0002_listuser... OK
 ----
-/ch18l009-1
+//ch18l009-1
 
 
 ==== Finishing the Custom Django Auth
@@ -562,11 +562,14 @@ Hmm, we can't quite cross off anything yet.
 Turns out the steps we _thought_ we'd go through
 aren't quite the same as the steps we're _actually_ going through
 (this is not uncommon as I'm sure you know).
+// CSANAD: I find it vague like this. Maybe it would be helpful to clarify what
+// it is that "we are actually going through" and what it was that
+// "we thought we'd go through".
 
 Still, we're almost there--our last step will combine recognising the token
 and then actually logging the user in.
 Once we've done this,
-we'll be able to pretty much strike off all the items on our scratchpad:
+we'll be able to pretty much strike off all the items on our scratchpad.
 
 
 So here's the view that actually handles the click through from the link in the