[lsd0004] 02/03: More language

[gnunet]

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0004.

commit 564e5fa775b0c0fdf947e857727412dfca4f5ac8
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Fri Dec 23 19:24:20 2022 +0900

    More language
---
 draft-schanzen-r5n.xml | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 1a252cc..98c46f9 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -276,8 +276,6 @@
       <t>
         The specific semantics of the above operations as provided by 
R<sup>5</sup>N
         for applications are defined in <xref target="overlay"/>.
-        The handling of blocks and their validation and storage is defined in
-        <xref target="blockstorage"/>.
       </t>
       <t>
         In a trivial scenario where there is only one peer (the local host),
@@ -317,9 +315,9 @@
       </t>
       <t>
         Across this document, the functional components of an R<sup>5</sup>N
-        implementation are divided into block processing (<xref 
target="blockstorage"/>),
-        message processing (<xref target="p2p_messages"/>) and routing
-        (<xref target="routing"/>).
+        implementation are divided into routing (<xref target="routing"/>),
+        message processing (<xref target="p2p_messages"/>) and
+        block processing (<xref target="blockstorage"/>).
         <xref target="figure_r5n_arch"/> illustrates the architectural 
overview of
         R<sup>5</sup>N.
       </t>
@@ -351,12 +349,13 @@ Connectivity | |Underlay|  |Underlay|
       </figure>
     </section>
     <section anchor="overlay" numbered="true" toc="default">
-      <name>Application API</name>
+      <name>Overlay operations</name>
       <t>
-        An implementation of this specification commonly exposes the two API
-        procedures "GET" and "PUT".
-        The following are non-normative examples of such APIs and their
-        behaviour are detailed in order to give implementers a fuller picture 
of the protocol.
+        An implementation of this specification commonly exposes the two 
overlay
+        operations "GET" and "PUT".
+        The following are non-normative examples of APIs for those operations.
+        Their behaviour is described prosaically in order to give implementers 
a fuller
+        picture of the protocol.
       </t>
       <section>
         <name>The GET procedure</name>

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