@@ -73,8 +73,9 @@ and it will pretty-print its state, like:
7373The generator also has a few useful optional arguments:
7474
7575- `%bowl`: Print the agent's bowl.
76−- `[%state %some-face]`: Print the part of your agent's state that has a face of
77− `some-face`.
76+- `[%state 'some code']`: Evaluate some code with the agent's state as its
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.
7879- `[%incoming ...]`: Print details of the matching incoming subscription, one
7980 of:
8081 - `[%incoming %ship ~some-ship]`
@@ -88,8 +89,8 @@ The generator also has a few useful optional arguments:
8889 - `[outgoing %term %agent-name]`
8990
9091By 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−instead.
92+if your app implements a scry endpoint with a path of `/x/dbug/state`, it will
93+use that instead.
9394
9495We haven't yet covered some of the concepts described here, so don't worry if
9596you don't fully understand `dbug`'s functionality - you can refer back here