address chapter13 review

move TIP, fix emdashes, add OK test output

Author: Xronophobe

chapter_13_database_layer_validation.asciidoc

@@ -270,7 +270,7 @@ if you are not convinced yet.
 Client-side validation will provide faster feedback on the UI, but
 https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html#client-side-vs-server-side-validation[it is not a security measure.]
 Server-side validation is indispensable for handling any input
-that gets processed by the server -- and it will also provide albeit slower,
+that gets processed by the server--and it will also provide albeit slower,
 feedback for the client side.]
 
 
@@ -580,7 +580,7 @@ Not quite, but they did get a little further.  Checking the line in which the
 error occurred -- 'line 31' in my case -- , we can
 // CSANAD: I think emphasizing what to look for in the error log is helpful.
 see that we've got past the first part of the test, and are now onto the second
-check -- that submitting a second empty item also shows an error.
+check--that submitting a second empty item also shows an error.
 
 ((("", startref="MLVsurfac13")))We've
 got some working code though, so let's have a commit:
@@ -592,12 +592,6 @@ $ *git commit -am "Adjust new list view to do model validation"*
 ----
 
 
-TIP: When working on a new feature, it's common to realize partway through that
-    a refactor of the application is needed. Adding an early return to the FT
-    you're currently working on allows you to perform this refactor against
-    passing FTs, even while the feature is still in progress.
-
-
 Let's put an early return in the FT to separate
 what we got working from those that still need to be dealt with:
 
@@ -633,6 +627,12 @@ We should also remind ourselves not to forget to remove this early return:
 
 And now, we can focus on making our code a little neater.
 
+TIP: When working on a new feature, it's common to realize partway through that
+    a refactor of the application is needed. Adding an early return to the FT
+    you're currently working on allows you to perform this refactor against
+    passing FTs, even while the feature is still in progress.
+
+
 
 === Django Pattern: Processing POST Requests in the Same View as Renders the Form
 
@@ -831,14 +831,21 @@ urlpatterns = [
 ----
 ====
 
-And that gets us to the `OK`.
+And that gets us to the green on the unit tests.
 
 ----
 OK
 ----
 
 
 Let's try a full FT run: they're all passing!
+
+----
+Ran 4 tests in 20 s
+
+OK
+----
+
 Our refactor of the `add_item` functionality is complete.
 We should commit there: