@@ -73,8 +73,9 @@ and it will pretty-print its state, like:
73The generator also has a few useful optional arguments:
73The generator also has a few useful optional arguments:
75- `%bowl`: Print the agent's bowl.
75- `%bowl`: Print the agent's bowl.
76−- `[%state %some-face]`: Print the part of your agent's state that has a face of
76+- `[%state 'some code']`: Evaluate some code with the agent's state as its
77− `some-face`.
77+ subject and print the result. The most common case is `[%state %some-face]`,
78+ which will print the contents of the wing with the given face.
78- `[%incoming ...]`: Print details of the matching incoming subscription, one
79- `[%incoming ...]`: Print details of the matching incoming subscription, one
80 - `[%incoming %ship ~some-ship]`
81 - `[%incoming %ship ~some-ship]`
@@ -88,8 +89,8 @@ The generator also has a few useful optional arguments:
88 - `[outgoing %term %agent-name]`
89 - `[outgoing %term %agent-name]`
90By default it will retrieve your agent's state by using its `on-save` arm, but
91By default it will retrieve your agent's state by using its `on-save` arm, but
91−if your app implements a scry endpoint with a path of `/x/dbug/state`, it will use that
92+if your app implements a scry endpoint with a path of `/x/dbug/state`, it will
92−instead.
93+use that instead.
94We haven't yet covered some of the concepts described here, so don't worry if
95We haven't yet covered some of the concepts described here, so don't worry if
95you don't fully understand `dbug`'s functionality - you can refer back here
96you don't fully understand `dbug`'s functionality - you can refer back here