@@ -56,12 +56,10 @@ but just to give you an idea of a typical pattern: An agent for a chat app might
56take new messages as pokes, add them to the list of messages in its state, and
56take new messages as pokes, add them to the list of messages in its state, and
57send out the new messages to subscribed chat participants as `gift`s.
57send out the new messages to subscribed chat participants as `gift`s.
59−As discussed [in the previous
59+As discussed in the previous lesson, Gall will automatically send a `%poke-ack`
60−lesson](/docs/userspace/gall-guide/5-cards#acknowledgements), Gall will
61−automatically send a `%poke-ack` `gift` back to wherever the poke came from. The
60+`gift` back to wherever the poke came from. The `%poke-ack` will be a nack if
62−`%poke-ack` will be a nack if your agent crashed while processing the poke, and
61+your agent crashed while processing the poke, and an ack otherwise. If it's a
63−an ack otherwise. If it's a nack, the `tang` in the `%poke-ack` will contain a
62+nack, the `tang` in the `%poke-ack` will contain a stack trace of the crash.
64−stack trace of the crash.
66As a result, you do not need to explicitly send a `%poke-ack`. Instead, you
64As a result, you do not need to explicitly send a `%poke-ack`. Instead, you
67would design your agent to handle only what you expect and crash in all other
65would design your agent to handle only what you expect and crash in all other