@@ -182,7 +182,7 @@ reasons. Firstly, it's not ideal to be passing around the entire `this` agent
182core - it's much tidier just passing around the `state`, until you actually want
182core - it's much tidier just passing around the `state`, until you actually want
183to return it to Gall. Secondly, It's much easier to read when the poke handling
183to return it to Gall. Secondly, It's much easier to read when the poke handling
184logic is separated into its own arm. This is a fairly simple example but if your
184logic is separated into its own arm. This is a fairly simple example but if your
185−agent is more complex, handling multiple `mark`s and containing additional logic
185+agent is more complex, handling multiple marks and containing additional logic
186before it gets to the actual contents of the `vase`, structuring things this way
186before it gets to the actual contents of the `vase`, structuring things this way
187can be useful.
187can be useful.
@@ -206,9 +206,9 @@ some extra things:
206Aside from their use by Clay for storing files in the filesystem, they're also
206Aside from their use by Clay for storing files in the filesystem, they're also
207used extensively for exchanging data with the outside world, and for exchanging
207used extensively for exchanging data with the outside world, and for exchanging
208data between Gall agents. When data comes in from a remote ship, destined for a
208data between Gall agents. When data comes in from a remote ship, destined for a
209−particular Gall agent, it will be validated by the mark file in `/mar` that
209+particular Gall agent, it will be validated by the file in `/mar` that
210−corresponds to its `mark` before being delivered to the agent. If the remote
210+corresponds to its mark before being delivered to the agent. If the remote data
211−data has no corresponding mark in `/mar` or it fails validation, it will crash
211+has no corresponding mark file in `/mar` or it fails validation, it will crash
212before it touches the agent.
212before it touches the agent.
214A mark file is a door with exactly three arms. The door's sample is the data type the
214A mark file is a door with exactly three arms. The door's sample is the data type the
@@ -366,7 +366,7 @@ Type definitions:
366Mark files:
366Mark files:
368- Mark files live in the `/mar` directory of a desk.
368- Mark files live in the `/mar` directory of a desk.
369−- A `mark` like `%foo` corresponds to a file in `/mar` like `/mar/foo.hoon`
369+- A mark like `%foo` corresponds to a file in `/mar` like `/mar/foo.hoon`
370- Marks are file types in Clay, but are also used for passing data between
370- Marks are file types in Clay, but are also used for passing data between
371 agents as well as for external data generally.
371 agents as well as for external data generally.
372- A mark file is a door with a sample of the data type it handles and exactly three
372- A mark file is a door with a sample of the data type it handles and exactly three