on master help sign in
ames:tasks: add missing + on arm name

Co-authored-by: poprox <51337059+drbeefsupreme@users.noreply.github.com>

commitce3d837426ffc48b7b9069e1cad34919b2b26c29 authortinnus-napbus <77721746+tinnus-napbus@users.noreply.github.com> dateThu 26 Aug 2021, 12:16 (5 years ago) parent7428b15
1 file changed+1−1
content/docs/arvo/ames/tasks.md+1−1
content/docs/arvo/ames/tasks.md+1−1
@@ -26,7 +26,7 @@ system/lifecycle tasks.
2626
2727This `task` only ever originates from Unix. It does the initial processing of a packet, namely by passing the raw packet information to `+decode-packet` which deserializes the packet and giving that data and the origin of the packet to `+on-hear-packet`, which begins the transformation of the packet into a new event in the form of a `+event-core`.
2828
29−There are multiple `+on-hear` arms in `ames.hoon`. Here we refer to `on-hear:event-core`, as that is the one called by a `%hear` `task`. The other ones are used primarily for ack and nack processing, or receiving message fragments.
29+There are multiple `+on-hear` arms in `ames.hoon`. Here we refer to `+on-hear:event-core`, as that is the one called by a `%hear` `task`. The other ones are used primarily for ack and nack processing, or receiving message fragments.
3030
3131`%hear` takes in a [$blob](/docs/arvo/ames/data-types#blob), which is essentially a large atom (around 1kB or less) that is the raw data of the message, and a [$lane](/docs/arvo/ames/data-types#lane), which is the origin of the message (typically an IP address).
3232