@@ -34,7 +34,8 @@ of data produced by the endpoint. There are a handful of exceptions to this:
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:
40> .^(desk %gd /=hark-store=)
41> .^(desk %gd /=hark-store=)
@@ -61,7 +62,8 @@ agents on that desk and their status. For example:
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:
67> .^(? %gu /=btc-wallet=)
69> .^(? %gu /=btc-wallet=)
@@ -119,7 +121,9 @@ The `on-peek` arm, therefore, begins like so:
124+Typically, you'd handle the `path` similarly to `on-watch`, as we discussed in
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:
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:
125?+ path (on-peek:def path)
129?+ path (on-peek:def path)