[gnunet-scheme] 01/03: doc: Fix ‘mq-prio-prefs’ cross-reference.

[gnunet]

This is an automated email from the git hooks/post-receive script.

maxime-devos pushed a commit to branch master
in repository gnunet-scheme.

commit 8dd5ca970397a1a27d9f84770e589a9d115feac7
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Mon Feb 7 14:54:21 2022 +0000

    doc: Fix ‘mq-prio-prefs’ cross-reference.
    
    * doc/service-communication (Sending messages): Add ‘mq-prio-prefs’ label.
---
 doc/service-communication.tm | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/service-communication.tm b/doc/service-communication.tm
index c3c36a1..89c187d 100644
--- a/doc/service-communication.tm
+++ b/doc/service-communication.tm
@@ -169,11 +169,12 @@
   slice. This is an asynchronuous operation, so this procedure can return
   before the service has processed the message.
 
-  Depending on the transport, it might be possible for messages to be lost or
-  received out-of-order. Some transports allow to explicitely allow messages
-  to be lost or received out-of-order and would by default retransmit lost
-  messages and reorder out-of-order messages; this behaviour can to a degree
-  be controlled by setting the <dfn|priority-preference> flags.
+  <label|mq-prio-prefs>Depending on the transport, it might be possible for
+  messages to be lost or received out-of-order. Some transports allow to
+  explicitely allow messages to be lost or received out-of-order and would by
+  default retransmit lost messages and reorder out-of-order messages; this
+  behaviour can to a degree be controlled by setting the
+  <dfn|priority-preference> flags.
 
   These flags are not absolute, e.g. even if reliable transmission is
   requested, it is possible that the transport fail to transmit the message.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.