@@ -125,15 +125,15 @@ Hoon and Nock have several unusual properties:
125125 environment are just Nock trees. We even have a statically typed
126126 metacircular interpreter called <code>+mule</code>. We run userspace code
127127 metacircularly with negligible performance overhead because of Urbit's
128− jet system. In Lisp "eval is evil" is a common saying but, in Urbit,
128+ jet system. In Lisp, "eval is evil" is a common saying, but in Urbit,
129129 eval is a first-class feature.
130130
131131- **Universally serializable**. There's one serialization format, called
132132 "jam", for any piece of code or data in the system. This makes it so
133133 that deserialization has just one function, a few hundred lines of C,
134134 as its security attack surface. It also facilitates portability of
135− the virtual machine state, and it turns out to be useful in a bunch of
136− places in the system.
135+ the virtual machine state, since this function can be called on the
136+ top-level VM state itself to generate a portable snapshot.
137137
138138- **Jetted**. A jet is a piece of code that the Nock interpreter has that
139139 reimplements a Nock function in some other, faster language. The `+dec`
@@ -183,8 +183,8 @@ Hoon and Nock have several unusual properties:
183183 consists of the standard library (itself a stack of cores), and
184184 possibly a "sample" (function argument).
185185
186−- **The type system has several unusual features**. It's intentional, in
187− the sense that all constructs are first-class and can be down-cast to
186+- **The type system has several unusual features**. It's intensional, in
187+ the sense that all constructs are first-class and can be up-cast to
188188 `noun`, Hoon's "any" or "top" type that matches all Nock nouns. Types
189189 are also used as scopes, so they store all of Hoon's variable names
190190 and docstrings. The type system uses an unusual macro-like feature