"[...] that is, ones not technically on the Web"

Add a liaison/segue sentence here (after this one) that says "Browsers, in fact, were not designed with triple scripts in mind at all."

"Web browsers"

huh?

Just say "It expects the read call to resolve to the file contents."?

Find a better way to say this. E.g. "The subdirectory for Part 1 from the project archive source tree"

And of course there's a bug here. This should be [1, 0, 0, 1].

We can afford to emphasize the TYPE family constants here by saying something like:

Or, to put it another way, given a statement let stats = checker.getStats(), the following results are true:

stats[LineChecker.TYPE_NONE] // evaluates to `1`
stats[LineChecker.TYPE_CR]   // evaluates to `0`
stats[LineChecker.TYPE_LF]   // evaluates to `0`
stats[LineChecker.TYPE_CRLF] // evaluates to `1`

"properties"

"... by getStats."

Note that the example cited is "a single line of text". We should emphasize that this isn't what we mean when we say that this is the default for DOS-style text files. (Of course DOS supports multi-line text files. It's just that the last line will have no CRLF sequence.)

should be "IETF"

nit: should be "to roll back" here

Bad link (currently points to @chrisaldrich's profile page)

typo?

Should have probably written "this entire section (including the preceding code block and the one that follows)".

"to speak"

"blocks containing our flavored pseudocode"

MarketWatch doesn't have editors?

these should be em dashes

should be "limits"

should be "Engelbart"

should be "than"

Capitalize “Smart Dimension” for consistency of style.

For clarity, this is better lowercase to differentiate between design tree options and concepts like “Plane”.

lets (no apostrophe)

lc “designs”

lc “designs”

Lowercase “graphics card”

Redundant with the phrase “all sorts of products.”

More simply, “SolidWorks is typically used to design mechanical assemblies comprising fewer than 200 parts,”

Missing a space after “CAD”.

You will learn how to start a new part file, the different file types, the user interface, and different setting and view options.

missing an "until" here

typo for "exists"

Two things that still need to be addressed in section 7:

• the top module is special
• an uncluttered root directory is good practice

s/.*/Let's discuss an implementation strategy/

"fewer"

Lots of punctuation mistakes in these two "sentences"—one being that this isn't really two sentences, since the second is a fragment, but it could be fixed by swapping the period for a colon or em dash.

Alt, you mean? (No Windows here; can't test, but it seems like that would be the right way to do it.)

The formatting of this link is messed up.

Typo; should "philanthropic".

"JavaScript" (or "JS")

"JavaScript" (or "JS")

Typo; should be "revisit".

As noted above (see https://hypothes.is/a/oHvCzI1DEeuC9IvJw8DOYw), g-blocks are most appropriate.

Should be /// export for the same reason as above. (See https://hypothes.is/a/oHvCzI1DEeuC9IvJw8DOYw.)

Should be using //? here, now that g-blocks are a thing.

"before"? We only just mentioned it!

typo (should be "my")

• strike "as"
• s/tolerant/tolerate/

Is this a typo or is this "two prime"?