Small tweaks from No Starch's proofreading

Author: marijnh

08_error.md

@@ -934,11 +934,11 @@ console.log(box.locked);
 // → true
 ```
 
+if}}
+
 For extra points, make sure that if you call `withBoxUnlocked` when
 the box is already unlocked, the box stays unlocked.
 
-if}}
-
 {{hint
 
 {{index "locked box (exercise)", "finally keyword", "try keyword"}}

09_regexp.md

@@ -1043,8 +1043,8 @@ holding the section's settings.
 {{index "carriage return", "line break", "newline character"}}
 
 Since the format has to be processed ((line)) by line, splitting up
-the file into separate lines is a good start. We used
-`string.split("\n")` to do this in [Chapter ?](data#split).
+the file into separate lines is a good start. We saw
+the `split` method in [Chapter ?](data#split).
 Some operating systems, however, use not just a newline character to
 separate lines but a carriage return character followed by a newline
 (`"\r\n"`). Given that the `split` method also allows a regular

10_modules.md

@@ -599,12 +599,12 @@ scenario where the file's content comes from some other source.
 
 Relatedly, stateful objects are sometimes useful or even necessary,
 but if something can be done with a function, use a function. Several
-of the INI file readers on NPM provide an interface style that require
-you to first create an object, then load the file into your object,
-and finally use specialized methods to get at the results. This type
-of thing is common in the object-oriented tradition, and it's
-terrible. Instead of making a single function call and moving on, you
-have to perform the ritual of moving your object through various
+of the INI file readers on NPM provide an interface style that
+requires you to first create an object, then load the file into your
+object, and finally use specialized methods to get at the results.
+This type of thing is common in the object-oriented tradition, and
+it's terrible. Instead of making a single function call and moving on,
+you have to perform the ritual of moving your object through various
 states. And because the data is now wrapped in a specialized object
 type, all code that interacts with it has to know about that type,
 creating unnecessary interdependencies.