Commit 10d1b1f added a hint about which word would be found by
a certain regexp:

"A call to str.match(/\w+/) will find only the first word in the line
(var). That’s not it."

Unfortunately the result is incorrect: the regexp would find `let`, not
`var`.

Updating the hint should resolve any confusion. The example has been
tested in the console to ensure that the regexp does indeed return
`let`.

Strictly speaking, there is no error here,
as `typeof` does not produce errors with undefined variables.

Now this chapter is at the end of the general section.

FIX: delete extra space

Fix semicolons in 1.11.1 (Introduction: callbacks)

promisiefy -> promisify

Fix typo.

Update article.md typo

Fix a typo in 1.11.3 (Promises chaining)

Revert "Fix a typo in 1.11.3 (Promises chaining)"

Fix semicolons in 1.11.6  (Promisification)

Fix semicolons, remove old note in 1.11.8

Fix typo in 1.11.6 (Promisification)

Fix Optional chaining doc

Fix typo, add note in 1.12.2 (Async iteration)

…section

Change `var` to `let` in 7.16 regexp-sticky

Correct comment in 1.13.1

Fix typos in 'Proxy and Reflect'

Fix outdated note in 1.99.04 (Reference Type)

Correct solution explanation in 1.99.04 (Reference Type)

Fix link in 2.1.5 (Node properties...)

It can be more readable with same line of code. There was a lot of nested parenthesis.

Refs: javascript-tutorial/en.javascript.info#2252 (comment)

Fix a typo in 1.11.3 (Promises chaining)

Fix typo in 2.1.6 (Attributes and properties)

look like ninja code

fix typo in 06-promisify article.md

Fix typos in 2.1.4 (Searching elements)

FIX: delete extra space

Fix a typo in 1.6.1 task solution

Fix a possible typo in 1.6.1

OPT: change "false" to "falsy"

FIX: change ; to ,

Fix possible typos in 1.3.6 (Polyfills and transpilers)

Sync examples from 2 commits in 8.5 (Shadow DOM slots...)

Fix typo in 8.5 (Shadow DOM slots...)

Update article.md in section 2.8

2-ui / 2-events / 5-dispatch-events

In subchapter "Event constructor": first word use "Built-in" instead of "Build-in"

Fix typo in 9.1 (Patterns and flags)

* Fix typos.
* Update a support note.
* Add a reference for a yet unexplained pattern.

Replace unicode with Unicode all over the book

`\bHello\b` pattern was just analyzed in the previous paragraph,
so the current wording is a bit confusing.

See https://caniuse.com/mdn-javascript_builtins_regexp_property_escapes

Without the `g` flag, we cannot say that the price is skipped.
Without the `\b` assertion, we will have the part of the price in the result.

As the task uses multiline HTML
and the note at the end suggests using `s` flag,
the lazy quantifier would be safer.

Refs: https://bugs.chromium.org/p/v8/issues/detail?id=10765
Refs: https://bugs.chromium.org/p/v8/issues/detail?id=11021

Can be tested in the Goole Chrome Beta, Dev, and Canary branches now,
as well as in the Node.js v8-canary branch.

Fix some issues in 9.2 (Character classes)

Typos in Part 2, 2.5 and Part 3, 3.2

Fix typo in 9.17 (Methods of RegExp and String)

Fix typo in 9.16 (Sticky flag "y"...)

Update support note in 9.15 (Catastrophic backtracking)

Fix typo, clarify wording in 9.15 (Catastrophic backtracking)

Fix typo in 1.99.1 (Proxy and Reflect)

Make solution in 9.14 safer

Correct example in 9.14 (Lookahead and lookbehind)

Fix typos in 9.13 (Alternation (OR) |)

Fix typos in 9.11 (Capturing groups)

Fix typos in 9.10 (Greedy and lazy quantifiers)

Update support note in 9.8 (Sets and ranges [...])

Fix typo in 9.8 task solution (Sets and ranges [...])

Fix typo in 9.7 (Escaping, special characters)

Fix confusing wording in 9.6 (Word boundary: \b)

Fix "polyfills" typo

Typo "in any *of* language"