@@ -54,7 +54,7 @@ the eye to tell whether a token on the screen is a feature of the
54language, or a label in the program. For example, in Lisp a
54language, or a label in the program. For example, in Lisp a
55special form has the same syntax as a function call.
55special form has the same syntax as a function call.
57−The worst-case result of FLC is "DSL cancer". Every source file
57+The worst-case result of FLC is "DSL cancer." Every source file
58is effectively written in its own domain-specific language. To
58is effectively written in its own domain-specific language. To
59read a new file is to learn a new language -- "write-only code."
59read a new file is to learn a new language -- "write-only code."
@@ -139,10 +139,10 @@ Some twigs (simple leafy ones) have *only* irregular forms.
139A regular form starts with a *sigil*, which is either a
139A regular form starts with a *sigil*, which is either a
140*keyword* or a *rune* -- at the programmer's choice.
140*keyword* or a *rune* -- at the programmer's choice.
142−A *keyword* is `:` and then the stem label - eg, `:cons`.
142+A *keyword* is `:` and then the stem label - e.g., `:cons`.
144−A *rune* is a pair of ASCII punctuation marks (a digraph) - eg,
144+A *rune* is a pair of ASCII punctuation marks (a digraph) - e.g.,
145−`:-`. The first glyph in the rune indicates the category - eg,
145+`:-`. The first glyph in the rune indicates the category - e.g.,
146`:` runes make cells. Runes can be pronounced by their glyphs or
146`:` runes make cells. Runes can be pronounced by their glyphs or
147by their stem -- for `:-`, you can say either "colhep" or "cons".
147by their stem -- for `:-`, you can say either "colhep" or "cons".
@@ -196,7 +196,7 @@ both tall/flat mode switches and well-shaped gaps. (Hoon layout
196could probably be done automatically with reasonable quality.
196could probably be done automatically with reasonable quality.
197But it would at least take machine learning, not a rule engine.)
197But it would at least take machine learning, not a rule engine.)
199−There only two real *rules* in Hoon whitespace design: don't
199+There are only two real *rules* in Hoon whitespace design: don't
200go past 80 characters, and don't use (completely) blank lines.
200go past 80 characters, and don't use (completely) blank lines.
201Otherwise, if it looks good and is easy to read, it's good. But
201Otherwise, if it looks good and is easy to read, it's good. But
202the best way to learn the art is to do everything by convention
202the best way to learn the art is to do everything by convention