From fad8da04c147123cb19829a667683235ebd57531 Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Wed, 19 Jun 2013 13:00:09 +0100 Subject: [PATCH] Fix typo. Copied from Perforce Change: 182805 ServerID: perforce.ravenbrook.com --- mps/manual/source/topic/message.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/mps/manual/source/topic/message.rst b/mps/manual/source/topic/message.rst index 68aacc7be46..95a3ee0e362 100644 --- a/mps/manual/source/topic/message.rst +++ b/mps/manual/source/topic/message.rst @@ -20,12 +20,12 @@ results. implemented in the form of a :term:`message queue` attached to each :term:`arena`. -The client program must enable each message type that they are -prepared to handle, by calling :c:func:`mps_message_type_enable`. Then -it must poll the message queue at regular intervals when it is -convenient to do so, calling :c:func:`mps_message_get` to retrieve -each message from the queue, and then calling -:c:func:`mps_message_discard` when it is done with it. +The client program must enable each message type that it is prepared +to handle, by calling :c:func:`mps_message_type_enable`. Then it must +poll the message queue at regular intervals when it is convenient to +do so, calling :c:func:`mps_message_get` to retrieve each message from +the queue, and finally calling :c:func:`mps_message_discard` when done +with the message. Messages are thus :term:`manually managed `: if the client program enables one or more message types, and then