suggest rewording the traceback of the failing FT

Author: Xronophobe

chapter_12_organising_test_files.asciidoc

@@ -628,18 +628,24 @@ FAILED (errors=1)
 The order of the traceback is a little confusing, but we can more or less follow
 through what happened:
 
-<1> At line 15 in our FT, we go into our `self.wait_for` helper,
-    passing it the `lambda`-ified version of the `assertEqual`.
+<1> In our FT, we call our `self.wait_for` helper, where we pass
+    the `lambda`-ified version of `assertEqual`.
 
-<2> We go into `self.wait_for` in _base.py_,
-    where we can see that we're inside `fn()`,
-    which is the name for our lambda inside the helper.
+<2> We go into `self.wait_for` in `base.py`,
+    where we're calling (and returning) `fn()`, which refers to the passed
+    lambda function encapsulating our test assertion.
 
 <3> To explain where the exception has actually come from,
     the traceback takes us back into _test_list_item_validation.py_
     and inside the body of the `lambda` function,
     and tells us that the attempt to find the `.invalid-feedback` element
     that failed.
+// CSANAD: I changed two things here:
+//   First, I think it's better to remove the specific line number which may
+// vary due to personal formatting preferences (and following the pep8 puts
+// this on line 16 for me)
+//   Secondly, we say we go into self.wait_for in step#2. Here, in step#1 we
+// are only calling it. Overall, I tried making it clearer a bit.
 
 
 ((("functional programming")))