[lsd0003] branch master updated: Fixed some formating full operation mode desc

[gnunet]

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

elias-summermatter pushed a commit to branch master
in repository lsd0003.

The following commit(s) were added to refs/heads/master by this push:
     new 6f3122e  Fixed some formating full operation mode desc
6f3122e is described below

commit 6f3122ec4f94988da5b44a5538aab6d9fa7de430
Author: Elias Summermatter <elias.summermatter@seccom.ch>
AuthorDate: Mon Dec 21 13:39:12 2020 +0100

    Fixed some formating full operation mode desc
---
 draft-summermatter-set-union.xml | 45 +++++++++++++++++++++-------------------
 1 file changed, 24 insertions(+), 21 deletions(-)

diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index f17dc38..c42e198 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -409,29 +409,32 @@
                 <name>Full Synchronisation Mode</name>
 
                 <t>
-                    In full synchronisation mode, if the set of the initiating 
peer is bigger than the set of the receiving peer, the initiating    ### 
Nachrichten und states ander darstellen
-                    peer sends a "Request Full" message and change from 
"Expecting SE" in "Full Receiving" State.                                   ### 
Refferenz auf nachrichten und all elements = message type anstat beschreibung
-                    In all other cases the initiating peer sends all set 
elements to the other peer
-                    followed by the "Full Done" message and changes into "Full 
Sending" State.
-                </t>
-                <t>
-                    <strong>Expecting IBF: </strong>                           
                                                                      ## 
Descripion list
-                    If a peer in the in state "Expecting IBF" receives a 
"Request Full" message from the other peer, the
-                    peer starts sending all the elements of the set followed 
by a "Full Done" message and change to the
-                    "Full Sending" State. If the peer receives an "Full 
Element" the peer changes to the state "Full Receiving".
-                </t>
-                <t>
-                    <strong>Full Sending: </strong>
-                    While a peer is in "Full Sending" state the peer expects 
to continuously receiving elements from the other
-                    peer. As soon as a the "Full Done" message is received the 
peer changes into "Finished" state
-                </t>
-                <t>
-                    <strong>Full Receiving (In code: Expecting IBF): </strong>
-                    While a peer is in "Full Receiving" state the peer expects 
to continuously receiving elements from the other
-                    peer. As soon as a the "Full Done" message is received the 
peer sends the remaining elements set to the other
-                    peer followed by a "Full Done". After sending the last 
message the peer changes into "Finished" state.
+                    In full synchronisation mode, if the set of the initiating 
peer is bigger than the set of the receiving peer, the initiating
+                    peer sends a <em>Request Full</em> message and change from 
<strong>Expecting SE</strong> to the <strong>Full Receiving</strong> State.
+                    In all other cases the initiating peer sends all set 
elements to the other peer followed by the <em>Full Done</em> message and
+                    changes into <strong>Full Sending</strong> state.
                 </t>
 
+                <t><strong>STATES:</strong></t>
+                <dl>
+                    <dt><strong>Expecting IBF:</strong></dt>
+                    <dd>
+                        If a peer in the in state <strong>Expecting 
IBF</strong> receives a <em>Request Full</em> message from the other peer, the
+                        peer starts sending all the elements of the set 
followed by a <em>Full Done</em> message and change to the
+                        <strong>Full Sending</strong> State. If the peer 
receives an <em>Full Element</em> the peer changes to the state <strong>Full 
Receiving</strong>.
+                    </dd>
+                    <dt><strong>Full Sending:</strong></dt>
+                    <dd>
+                        While a peer is in <strong>Full Sending</strong> state 
the peer expects to continuously receiving elements from the other
+                        peer. As soon as a the <em>Full Done</em> message is 
received the peer changes into <strong>Finished</strong> state.
+                    </dd>
+                    <dt><strong>Full Receiving (In code: Expecting IBF): 
</strong></dt>
+                    <dd>
+                        While a peer is in <strong>Full Receiving</strong> 
state the peer expects to continuously receiving elements from the other
+                        peer. As soon as a the <em>Full Done</em> message is 
received the peer sends the remaining elements set to the other
+                        peer followed by a <em>Full Done</em>. After sending 
the last message the peer changes into <strong>Finished</strong> state.
+                    </dd>
+                </dl>
             </section>
             <section anchor="modeofoperation_individual-elements" 
numbered="true" toc="default">
                 <name>Individual Element Synchronisation Mode</name>

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