@@ -50,13 +50,13 @@ Here's a brief summary of each of the vanes:
5050 unless you specifically wanted to read and write files.
5151
5252- **Dill**: Terminal driver vane. You would not typically interact with Dill
53− directly; printing messages to the terminal is usually done with hinting runes
53+ directly; printing debug messages to the terminal is usually done with hinting runes
5454 and functions rather than tasks to Dill, and CLI apps are mediated by a
5555 sub-module of the `%hood` system agent called `%drum`. CLI apps will not be touched
5656 on in this guide, but there's a separate [CLI
5757 Apps](/docs/hoon/guides/cli-tutorial) guide which covers them if you're
5858 interested.
59−- **Eyre**: Webserver vane. App front-ends are served via Eyre. It's possible to
59+- **Eyre**: Webserver vane. App web front-ends are served via Eyre. It's possible to
6060 handle HTTP requests directly in a Gall agent (see the [Eyre
6161 Guide](/docs/arvo/eyre/guide) for details), but usually you'd just serve a
6262 front-end [glob](/docs/userspace/dist/glob) via the `%docket` agent, so you'd
@@ -104,13 +104,13 @@ there's also:
104104 If one of the API calls fails, your Gall agent is potentially left in a
105105 strange intermediary state. Instead, you can put all the IO logic in a
106106 separate thread which is completely atomic. That way the Gall agent only has
107− to deal with the two conditions of success or failure. Writing threads are
107+ to deal with the two conditions of success or failure. Writing threads is
108108 covered in a [separate guide](/docs/userspace/threads/basics/fundamentals),
109109 which you might like to work through after completing the Gall Guide.
110110
111111- **Front-end**: Web UIs. It's possible for Gall agents to handle HTTP requests
112− directly and dynamically produce responses, but it's more typical to have a
113− separate [glob](/docs/userspace/dist/glob) of HTML, CSS, Javascript, images,
112+ directly and dynamically produce responses, but it's also possible to have a
113+ static [glob](/docs/userspace/dist/glob) of HTML, CSS, Javascript, images,
114114 etc, which are served to the client like an ordinary web app. Such front-end
115115 files are typically managed by the `%docket` agent which serves them via Eyre.
116116 The [software distribution guide](/docs/userspace/dist/guide) covers this in
@@ -151,7 +151,7 @@ some of these features in more detail later in the guide.
151151## Desk Anatomy
152152
153153The fundamental unit in Clay is a desk. Desks are kind of like git repositories.
154−Urbit includes a few default desks: `%base`, `%garden`, `%landscape`, `%webterm`
154+By default, new urbits come with the following desks included: `%base`, `%garden`, `%landscape`, `%webterm`
155155and `%bitcoin`.
156156
157157- `%base` - This desk contains the kernel as well as some core agents and utilities.
@@ -166,8 +166,7 @@ upstream that sponsored ships (moons in the case of a planet, planets in the
166166case of a star) sync their `%base` desk from. Any third-party apps you've
167167installed will also have their own desks.
168168
169−Each desk will typically have a few default directories. The directories are as
170−follows:
169+Desks are typically assumed to store their files according to the following directory structure:
171170
172171```
173172desk
@@ -176,7 +175,7 @@ desk
176175├── lib
177176├── mar
178177├── sur
179−├── sys <- on %base desk only
178+├── sys
180179├── ted
181180└── tests
182181```
@@ -190,7 +189,7 @@ desk
190189- `sys`: Kernel files and standard library. Only the `%base` desk has this
191190 directory, it's omitted entirely in all other desks.
192191- `ted`: Threads.
193−- `tests`: Unit tests, to be run by the `%test` thread. This is often omitted.
192+- `tests`: Unit tests, to be run by the `%test` thread. This is often omitted in distributed desks.
194193
195194This directory hierarchy is not strictly enforced, but most tools expect things
196195to be in their right place. Any of these folders can be omitted if they'd
@@ -251,7 +250,7 @@ You should now have a general idea of the different parts of Arvo, but how does
251250a Gall agent interact with these things?
252251
253252There are two basic ways of interacting with other parts of the system: by
254−scrying them, and by passing them messages and receiving messages in response.
253+scrying into them, and by passing them messages and receiving messages in response.
255254There are also two basic things to interact with: vanes, and other agents.
256255
257256- Scries: The scry system allows you to access the state of other agents and