git.iko.soy/urbit.org
on master help sign in
gall-guide: tweaks/typos for lesson 9
091d2c1Tinnus Napbus
content/docs/userspace/gall-guide/9-vanes.md+5−4
compare with master
unifiedsplit
@@ -45,7 +45,8 @@ briefly recap it here. The type of the card is as follows:
45[%pass path %arvo note-arvo]
45[%pass path %arvo note-arvo]
46```
46```
47
47
48−The `path` will just be the `wire` you want the response to arrive on. The `note-arvo` is the following union:
48+The `path` will just be the `wire` you want the response to arrive on. The
49+`note-arvo` is the following union:
49
50
50```hoon
51```hoon
51+$ note-arvo
52+$ note-arvo
@@ -77,7 +78,7 @@ desk.
77## Receiving a vane gift
78## Receiving a vane gift
78
79
79Once a `task` has been sent to a vane, any `gift`s the vane sends back in
80Once a `task` has been sent to a vane, any `gift`s the vane sends back in
80−response will arrive in the `on-arvo` arm of your agent core. The `on-arvo` arm
81+response will arrive in the `on-arvo` arm of your agent. The `on-arvo` arm
81exclusively handles such vane `gift`s. The `gift`s will arrive in a `sign-arvo`,
82exclusively handles such vane `gift`s. The `gift`s will arrive in a `sign-arvo`,
82along with the `wire` specified in the original request. The `on-arvo` arm
83along with the `wire` specified in the original request. The `on-arvo` arm
83produces a `(quip card _this)` like usual, so it would look like:
84produces a `(quip card _this)` like usual, so it would look like:
@@ -89,7 +90,7 @@ produces a `(quip card _this)` like usual, so it would look like:
89 .....
90 .....
90```
91```
91
92
92−A `sign-arvo` is the following structure:
93+A `sign-arvo` is the following structure, defined in `lull.hoon`:
93
94
94```hoon
95```hoon
95+$ sign-arvo
96+$ sign-arvo
@@ -265,7 +266,7 @@ After approximately five seconds, we see the timer fired successfully:
265
266
266- Each vane has an API composed of `task`s it takes and `gift`s it produces.
267- Each vane has an API composed of `task`s it takes and `gift`s it produces.
267- Each vane's `task`s and `gift`s are defined in `lull.hoon`
268- Each vane's `task`s and `gift`s are defined in `lull.hoon`
268−- Each vane's section of the [Arvo documentation](/docs/arvo/overview) include
269+- Each vane's section of the [Arvo documentation](/docs/arvo/overview) includes
269 an API reference that explains its `task`s and `gift`s, as well as an Examples
270 an API reference that explains its `task`s and `gift`s, as well as an Examples
270 section demonstrating their usage.
271 section demonstrating their usage.
271- Vane `task`s can be sent to vanes by `%pass`ing them an `%arvo` `card`.
272- Vane `task`s can be sent to vanes by `%pass`ing them an `%arvo` `card`.