update links, add note on Bootstrap's recommendations

and fix typos

Author: Xronophobe

chapter_13_database_layer_validation.asciidoc

@@ -115,7 +115,7 @@ TIP: If you're new to Python, you may never have seen the `with` statement.
     It's used with what are called "context managers", which wrap a block of code,
     usually with some kind of setup, cleanup, or error-handling code.
     There's a good write-up in the
-    http://docs.python.org/release/2.5/whatsnew/pep-343.html[Python 2.5 release notes].
+    https://docs.python.org/release/2.5/whatsnew/pep-343.html[Python 2.5 release notes].
     ((("with statements")))
     ((("Python 3", "with statements")))
 
@@ -151,10 +151,11 @@ A Django Quirk: Model Save Doesn't Run Validation
 ((("model-layer validation", "running full validation")))
 And now we discover one of Django's little quirks.
 _This test should already pass_.
-f you take a look at the
-http://bit.ly/SuxPJO[docs for the Django model fields],
-you'll see that `TextField` actually defaults to `blank=False`, which means
-that it 'should' disallow empty values.
+If you take a look at the
+https://docs.djangoproject.com/en/4.2/ref/models/fields/#blank[docs for the Django model fields],
+you'll see under _Field options_ that the default setting for `blank` is `False`. Which means,
+since TextField is a type of Field, it 'should' disallow empty values.
+// CSANAD: I rephrased this a little, because `blank` is False for all `Field`s.
 
 ((("data integrity errors")))
 So why is the test still failing?
@@ -187,7 +188,7 @@ No changes detected
 ((("full_clean method")))Django
 does have a method to manually run full validation, however, called
 `full_clean` (more info in
-http://bit.ly/2u5SIxA[the docs]).
+https://docs.djangoproject.com/en/4.2/ref/models/instances/#django.db.models.Model.full_clean[the docs]).
 Let's hack it in to see it work:
 
 
@@ -221,7 +222,7 @@ Surfacing Model Validation Errors in the View
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 ((("model-layer validation", "surfacing errors in the view", id="MLVsurfac13")))
-Let"s try to enforce our model validation in the views layer
+Let's try to enforce our model validation in the views layer
 and bring it up through into our templates, so the user can see them.
 Here's how we can optionally display an error in our HTML--we check whether the template has
 been passed an error variable, and if so, we do this:
@@ -251,8 +252,15 @@ been passed an error variable, and if so, we do this:
 
 ((("Bootstrap", "documentation")))
 ((("form control classes (Bootstrap)")))
-Take a look at the http://getbootstrap.com/css/#forms[Bootstrap docs] for more
+Take a look at the https://getbootstrap.com/docs/5.3/forms/validation/#server-side[Bootstrap docs] for more
 info on form controls.
+// CSANAD: these are the new docs for Bootstrap, but for some reason they begin
+//         with saying "We recommend client-side validation" which is bad.
+// Client side validation is fine for faster UI aesthetics, sure. But they are
+// not emphasizing that it is only for faster feedback and for security,
+// whatever reaches the server should be validated on the server side before
+// accepting it as an input for literally anything... Maybe we should mention
+// this in a side note?
 
 Passing this error to the template is the job of the view function. Let's take
 a look at the unit tests in the `NewListTest` class.  I'm going to use two
@@ -416,7 +424,7 @@ self.assertContains(response, expected_error)
 ====
 
 ...will show us the cause—Django has
-https://docs.djangoproject.com/en/1.11/ref/templates/builtins/#autoescape[HTML-escaped]
+https://docs.djangoproject.com/en/4.2/ref/templates/builtins/#autoescape[HTML-escaped]
 the apostrophe:
 
 ----
@@ -964,7 +972,7 @@ a [keep-together]#parameter#:
 ====
 
 See the
-http://bit.ly/2uKaMzA[Django
+https://docs.djangoproject.com/en/4.2/topics/http/urls/#reverse-resolution-of-urls[Django
 docs on reverse URL resolution] for more info. We run the tests again, and check that they all pass:
 
 [subs="specialcharacters,macros"]
@@ -1043,7 +1051,7 @@ AttributeError: 'List' object has no attribute 'get_absolute_url'
 The implementation is to use Django's `reverse` function, which
 essentially does the reverse of what Django normally does with 'urls.py'
 (see the
-https://docs.djangoproject.com/en/1.11/topics/http/urls/#reverse-resolution-of-urls[docs]):
+https://docs.djangoproject.com/en/4.2/topics/http/urls/#reverse-resolution-of-urls[docs]):
 
 
 [role="sourcecode"]
@@ -1077,7 +1085,7 @@ def new_list(request):
 ====
 
 There's more info in the
-https://docs.djangoproject.com/en/1.11/topics/http/shortcuts/#redirect[Django
+https://docs.djangoproject.com/en/4.2/topics/http/shortcuts/#redirect[Django
 docs].  Quick check that the unit tests still pass:
 
 [subs="specialcharacters,macros"]