@@ -35,10 +35,10 @@ Let's take a look at two apps, `:source` and `:sink`. First,
3535|_ [bow=bowl:gall $~]
3636::
3737++ poke-noun
38− |= non=*
38+ |= non=*
3939 ^- [(list move) _+>.$]
4040 :_ +>.$
41− %+ turn (prey /example-path bow)
41+ %+ turn (prey:pubsub:userlib /example-path bow)
4242 |=([o=bone *] [o %diff %noun non])
4343::
4444++ peer-example-path
@@ -140,7 +140,7 @@ And secondly, `:sink`:
140140--
141141```
142142
143−Save this as `sink.hoon` in the `/app` directory of your urbit's pier.
143+Save this as `sink.hoon` in the `/app` directory of your urbit's pier (make sure both `source` and `sink` are on the same ship).
144144
145145Two notes:
146146
@@ -231,12 +231,12 @@ languages call "map" -- it runs a function on every item in a list and collects
231231the results in a list. The list is `(prey /example-path bow)` and the function
232232is the `|=` line right after it.
233233
234−`++prey` is a standard library function defined in `zuse.hoon`. It takes a path
234+`prey:pubsub:userlib` is a standard library function defined in `zuse.hoon`. It takes a path
235235and a bowl and gives you a list of the subscribers who are subscribed on a path
236236that begins with the given path. "Prey" is short for "prefix".
237237
238238Now we have the list of relevant subscribers. This a list of triples,
239−`{bone @p path}`, where the only thing we really need is the bone, because we
239+`[bone @p path]`, where the only thing we really need is the bone, because we
240240don't need to know their urbit or what exact path they subscribed on. Thus, our
241241transformer function takes `[o=bone *]` and produces `[o %diff %noun non]`,
242242which is a move that provides bone `o` with this subscription update: