small things in 16

Author: hjwp

chapter_16_javascript.asciidoc

@@ -240,7 +240,7 @@ at the bottom of our _base.html_ template:
 
 <4> It finds the error message element,
     and then hides it by setting its `style.display` to "none".
-    
+
 That's actually good enough to get our FT passing:
 
 [subs="specialcharacters,quotes"]
@@ -499,12 +499,13 @@ image::images/jasmine-in-browser-red.png["Jasmine browser-based spec runner show
 
 .Is the Jasmine Standalone Browser Test Runner Unconventional?
 *******************************************************************************
-In all honesty, I'm not sure. The JavaScript world moves so fast that
-even if I was sure when I wrote it, I'd be wrong by the time you read this.
+I think it probably is, to be honest.
+Although the JavaScript world moves so fast,
+I could be wrong by the time you read this.
 
 What I do know is that, along with moving very fast,
 JavaScript things can very quickly become very complicated.
-A lot of people are working with frameworks these days (React is the main one), 
+A lot of people are working with frameworks these days (React is the main one),
 and along with that comes TypeScript, transpilers, to say nothing of Node.js,
 `npm`, the `node_modules` folder, and a very steep learning curve.
 
@@ -516,7 +517,8 @@ and it lets us tests interactions with the DOM.
 That's enough to give us a basic environment in which to do TDD in JavaScript.
 
 If you decide to go further in the world of frontend,
-you probably will eventually get into the complexity of frameworks and transpilers,
+you probably will eventually get into the complexity of frameworks
+and TypeScript and transpilers,
 but the basics we work with here will still be a good foundation.
 
 If you want to take a small step further,
@@ -636,6 +638,7 @@ on-failure messages into individual `expect/toBe` expressions.
 If you refresh the browser, you should see that all passes:
 
 
+[[first-jasmine-output]]
 .Expected results from Jasmine in the browser
 ====
 [role="jasmine-output"]
@@ -650,7 +653,8 @@ Superlists tests
 ----
 ====
 
-(I'll show the Jasmine outputs as text, like the above, from now on,
+
+(I'll show the Jasmine outputs as text, as in <<first-jasmine-output>>, from now on,
 to avoid filling the chapter with screenshots.)
 
 
@@ -725,7 +729,7 @@ into _lists.js_:
 [role="sourcecode"]
 .src/lists/static/lists.js (ch16l014)
 ====
-[source,html]
+[source,javascript]
 ----
 const textInput = document.querySelector("#id_text");
 textInput.oninput = () => {
@@ -780,7 +784,7 @@ Let's add a couple of debug prints, or "console.logs":
 [role="sourcecode"]
 .src/lists/static/tests/Spec.js (ch16l015)
 ====
-[source,html]
+[source,javascript]
 ----
 console.log("Spec.js loading");
 
@@ -838,7 +842,8 @@ What do we see?
 * then we see a `beforeEach`, which is when our test fixture actually gets added to the DOM
 * then we see the first test run.
 
-This explains the problem - when _lists.js_, the input node doesn't exist yet.
+This explains the problem - when _lists.js_ loads,
+the input node doesn't exist yet.
 
 
 
@@ -1090,7 +1095,7 @@ describe("Superlists tests", () => {
 <5> Here's why `textInput` and `errorMsg` can't be constants:
     we're re-creating the DOM fixture in every `beforeEach`,
     so we need to re-fetch the elements each time.
-    
+
 
 Now we can apply some DRY to strip down our tests:
 
@@ -1099,7 +1104,7 @@ Now we can apply some DRY to strip down our tests:
 [role="sourcecode"]
 .src/lists/static/tests/Spec.js (ch16l023)
 ====
-[source,python]
+[source,javascript]
 ----
   it("sense-check our html fixture", () => {
     expect(errorMsg.checkVisibility()).toBe(true);
@@ -1235,7 +1240,7 @@ const initialize = (errorSelector, inputSelector) => {
 ----
 ====
 
-Phew, that gives us a failure:
+Phew, that does indeed fail:
 
 [role="jasmine-output"]
 [subs="specialcharacters,quotes"]
@@ -1409,7 +1414,8 @@ Superlists tests
 ----
 
 
-Let's do a little more refactoring.  If your editor is set up to do some JavaScript linting,
+Let's do a little more refactoring.
+If your editor is set up to do some JavaScript linting,
 you might have seen a warning saying:
 
 
@@ -1490,7 +1496,7 @@ And we can run the FT one more time, just for safety:
 
 
 [[columbo-onload]]
-=== Columbo Says: wait for Onload 
+=== Columbo Says: wait for Onload
 
 [quote, Columbo]
 ______________________________________________________________