Various small fixes

marijnh · marijnh · commit 8a2ce39f3378 · 2018-02-07T18:10:09.000+01:00
Closes marijnh#299 Closes marijnh#293 Closes marijnh#294
diff --git a/01_values.md b/01_values.md
@@ -46,9 +46,9 @@ So that's the binary number 00001101, or 8 + 4 + 1, or 13.
 {{index memory, "volatile data storage", "hard drive"}}
 
 Imagine a sea of bits. An ocean of them. A typical modern computer has
-more than 30 billion bits in its volatile data storage. Nonvolatile
-storage (the hard disk or equivalent) tends to have yet a few orders
-of magnitude more.
+more than 30 billion bits in its volatile data storage (working
+memory). Nonvolatile storage (the hard disk or equivalent) tends to
+have yet a few orders of magnitude more.
 
 To be able to work with such quantities of bits without getting lost,
 we must separate them into chunks that represent pieces of
diff --git a/03_functions.md b/03_functions.md
@@ -425,12 +425,13 @@ console.log(chicken() + " came first.");
 The following code is allowed and executes without any problem:
 
 ```
+function square(x) { return x * x; }
 console.log(square(4, true, "hedgehog"));
 // → 16
 ```
 
-We defined `square` with only one ((parameter)). Yet when you call it
-like this, it doesn't complain. It ignores the extra arguments and
+We define `square` with only one ((parameter)). Yet when you call it
+with three, it doesn't complain. It ignores the extra arguments and
 computes the square of the first one.
 
 {{index undefined}}
diff --git a/08_error.md b/08_error.md
@@ -596,9 +596,9 @@ function transfer(from, amount) {
 }
 ```
 
-This version of the function tracks it progress, and if, when leaving,
-it notices that it was aborted at a point where it had created an
-inconsistent program state, it repairs the damage it did.
+This version of the function tracks its progress, and if, when
+leaving, it notices that it was aborted at a point where it had
+created an inconsistent program state, it repairs the damage it did.
 
 Note that, even though the `finally` code is run when an exception
 leaves the `try` block, it does not interfere with the exception.
diff --git a/11_async.md b/11_async.md
@@ -248,8 +248,8 @@ defineRequestType("note", (nest, content, source, done) => {
 The `defineRequestType` function defines a new type of request. The
 example adds support for `"note"` requests, which just send a note to
 a given nest. Our implementation just calls `console.log` so that we
-can verify that the request arrived. The `name` binding holds the name
-of this nest.
+can verify that the request arrived. The `name` property holds the
+name of the nest.
 
 {{index "asynchronous programming"}}
 
diff --git a/20_node.md b/20_node.md
@@ -262,10 +262,10 @@ $ node
 After running `npm install`, ((NPM)) will have created a directory
 called `node_modules`. Inside that directory will be an `ini`
 directory, which contains the ((library)). When we run `node` and call
-`require("figlet")`, this library is loaded, and we can call its
-`text` method to draw some big letters.
+`require("ini")`, this library is loaded, and we can call its `parse`
+property to parse a configuration file.
 
-By default NPM installs packages into the current directory, rather
+By default NPM installs packages under the current directory, rather
 than in a central place. If you are used to other package managers,
 this may seem unusual, but it has advantages—it puts each application
 in full control of the packages it installs, and makes it easier to
