@@ -34,7 +34,8 @@ of data produced by the endpoint. There are a handful of exceptions to this:
3434
3535#### `%d`
3636
37−A scry to Gall with a `%d` `care` and no `path` will produce the `desk` in which the specified agent resides. For example:
37+A scry to Gall with a `%d` `care` and no `path` will produce the `desk` in which
38+the specified agent resides. For example:
3839
3940```
4041> .^(desk %gd /=hark-store=)
@@ -61,7 +62,8 @@ agents on that desk and their status. For example:
6162
6263#### `%u`
6364
64−A scry to Gall with a `%u` `care` and no `path` will check whether or not the specified agent is installed and running:
65+A scry to Gall with a `%u` `care` and no `path` will check whether or not the
66+specified agent is installed and running:
6567
6668```
6769> .^(? %gu /=btc-wallet=)
@@ -119,7 +121,9 @@ The `on-peek` arm, therefore, begins like so:
119121 ....
120122```
121123
122−Typically, you'd handle the `path` similarly to `on-watch`, as we discussed in the lesson on subscriptions. You'd use something like a wutlus expression to test the type of the `path`, defining your scry endpoints like so:
124+Typically, you'd handle the `path` similarly to `on-watch`, as we discussed in
125+the lesson on subscriptions. You'd use something like a wutlus expression to
126+test the type of the `path`, defining your scry endpoints like so:
123127
124128```hoon
125129?+ path (on-peek:def path)