lsd0004

commit bc291e7e85d2e8cfd3a9c1bd5d36a25df7a9e7b6
parent c409e987a7cbe04423c86e5844b1d723e2d5759f
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Thu, 10 Mar 2022 12:54:18 +0100

simplify english

Diffstat:
M
draft-schanzen-r5n.xml
 | 
15
++++++++++-----

1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -558,10 +558,11 @@ Connectivity | |Underlay|  |Underlay|
         </dd>
       </dl>
       <t>
-        In addition to the above procedures, which are meant to be actively
-        executed by the implementation as part of the peer-to-peer protocol,
-        the following signals (usually implemented as callbacks) drive
-	updates of the routing table, local storage and message transmission:
+        The above procedures are meant to be actively
+        executed by the implementation as part of the peer-to-peer protocol.
+	In addition, the underlay is expected to emit
+        the following signals (usually implemented as callbacks)
+	based on network events observed by the underlay implementation:
       </t>
       <dl>
         <dt>
@@ -604,13 +605,17 @@ Connectivity | |Underlay|  |Underlay|
           this address to other peers.
         </dd>
         <dt>
-          <tt>RECEIVE() -> (P, M)</tt>
+          <tt>RECEIVE -> (P, M)</tt>
         </dt>
         <dd>
           This signal informs the local peer that a protocol
           message <tt>M</tt> was received from a peer <tt>P</tt>.
         </dd>
       </dl>
+      <t>
+	These signals then drive updates of the routing table, local storage
+	and message transmission.
+      </t>	
     </section>
     <section>
       <name>Bootstrapping</name>