some additions to chapter14

add TODO to reorder steps, mention pycache, remove chapter update warning, add commit to the end of the chapter

Author: Xronophobe

chapter_14_simple_form.asciidoc

@@ -1,16 +1,6 @@
 [[chapter_14_simple_form]]
 == A Simple Form
 
-.🚧 Warning, Chapter update in progress
-*******************************************************************************
-This chapter is currently in the process of being rewritten for the 3e.
-
-The code listings should all be valid,
-and work with Python3.12 + Django 4,
-but I haven't reviewed the chapter text in detail yet.
-
-*******************************************************************************
-
 
 At the end of the last chapter,
 we were left with the thought that there was too much duplication
@@ -615,9 +605,9 @@ with `id_text` and `text`, respectively:
 $ *grep -r id_new_item src/lists/*
 ----
 
-Good, there are no references to `id_new_item` left.
-// CSANAD: we could mention *.pyc files under __pycache__ would probably still
-//         show up in the results.
+Good, there are no references to `id_new_item` left--except maybe in some
+`*.pyc` files. If you see these, Python generates them for faster execution
+and they will be regenerated when the code changes.
 What about `name`/ `item_text`?
 
 [subs="specialcharacters,macros"]
@@ -678,6 +668,9 @@ element: .invalid-feedback; [...]
 [...]
 ----
 
+// TODO re-order the steps for this chapter: it would be better to start with
+// the `id_text` related errors first, and only then fix the validation.
+
 Let's start with the latter.
 Checking _views.py_ and the `new_list` view we can see
 it's because if we detect a validation error,
@@ -1361,7 +1354,13 @@ Ran 4 tests in 14.367s
 OK
 ----
 
-Great!  Our two views are now looking very much like "normal" Django views:
+Great!  Let's commit our changes:
+[subs="specialcharacters,quotes"]
+----
+$ *git commit -am "implement custom save method for the form"*
+----
+
+Our two views are now looking very much like "normal" Django views:
 they take information from a user's request,
 combine it with some custom logic or information from the URL (`list_id`),
 pass it to a form for validation and possible saving,