@@ -176,7 +176,7 @@ Typically, updates to an operating system are given via a pre-compiled binary,
176which is why some updates will work on some systems but not on others where the
176which is why some updates will work on some systems but not on others where the
177hardware and environment may differ. This is not so on Arvo - because it is an
177hardware and environment may differ. This is not so on Arvo - because it is an
178[interpreter](#solid-state-interpreter), Arvo may update itself by receiving
178[interpreter](#solid-state-interpreter), Arvo may update itself by receiving
179−source code from your sponsor over [Ames](@/docs/tutorials/arvo/ames.md), our
179+source code from your sponsor over [Ames](@/docs/arvo/ames/ames.md), our
180network. As Hoon compiles down to Nock, which is an axiomatic representation of
180network. As Hoon compiles down to Nock, which is an axiomatic representation of
181a deterministic computer, this code is guaranteed to run identically on your machine as it
181a deterministic computer, this code is guaranteed to run identically on your machine as it
182would on anybody else's.
182would on anybody else's.
@@ -444,7 +444,7 @@ A short summary of the purpose of each these arms are as follows:
444 - `+poke` is the transition function that `move`s Arvo from one state to the
444 - `+poke` is the transition function that `move`s Arvo from one state to the
445 next. It is the most fundamental arm in the entire system. It is a typed
445 next. It is the most fundamental arm in the entire system. It is a typed
446 transactional message that is processed at most once. If the `+poke` causes
446 transactional message that is processed at most once. If the `+poke` causes
447− Arvo to send an message over [Ames](@/docs/tutorials/arvo/ames.md) Ames
447+ Arvo to send an message over [Ames](@/docs/arvo/ames/ames.md) Ames
448 guarantees that the message will be delivered exactly once. This is sometimes said
448 guarantees that the message will be delivered exactly once. This is sometimes said
449 to be impossible, and it is for standard operating systems, but that is not the case for single-level stores engaged in
449 to be impossible, and it is for standard operating systems, but that is not the case for single-level stores engaged in
450 a permanent session, as is the case among Arvo ships.
450 a permanent session, as is the case among Arvo ships.
@@ -561,7 +561,7 @@ data that directly causes the desired outcome of a `move`. This event data is co
562As of this writing, we have nine vanes, which each provide the following services:
562As of this writing, we have nine vanes, which each provide the following services:
564−- [Ames](@/docs/tutorials/arvo/ames.md): the name of both our network and the vane that communicates over it.
564+- [Ames](@/docs/arvo/ames/ames.md): the name of both our network and the vane that communicates over it.
565- [Behn](@/docs/tutorials/arvo/behn.md): a simple timer.
565- [Behn](@/docs/tutorials/arvo/behn.md): a simple timer.
566- [Clay](@/docs/tutorials/arvo/clay.md): our version-controlled, referentially- transparent, and global filesystem.
566- [Clay](@/docs/tutorials/arvo/clay.md): our version-controlled, referentially- transparent, and global filesystem.
567- [Dill](@/docs/tutorials/arvo/dill.md): a terminal driver. Unix sends keyboard events to `%dill` from the console, and `%dill` produces terminal output.
567- [Dill](@/docs/tutorials/arvo/dill.md): a terminal driver. Unix sends keyboard events to `%dill` from the console, and `%dill` produces terminal output.