commit 708869b9de9e1f1512a0cf28974cf6a415039dd8
parent 0a3305a9165d840dfbcca4d12a9e818f9eb6cebb
Author: Christian Grothoff <christian@grothoff.org>
Date: Sat, 13 Jul 2024 09:40:31 +0200
English and style fixes
Diffstat:
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -1740,25 +1740,25 @@ BEGIN
an EdDSA signature <xref target="ed25519"/> by the sender of this message
(using the same format as the signatures in PUTPATH)
affirming that the sender forwarded the message from
- the predecessor (all zeros if PATH_LEN is 0,
- otherwise the last peer in PUTPATH) to
+ the predecessor (all zeros if <tt>PATH_LEN</tt> is 0,
+ otherwise the last peer in <tt>PUTPATH</tt>) to
the target peer.
Modified by processing peers (if flag is set).
</dd>
<dt>BLOCK</dt>
<dd>
- the variable-length block payload. The contents are determined
- by the BTYPE field. The length is determined by MSIZE minus
- the size of all of the other fields.
- Set by the initiator. Read-only.
+ the variable-length block payload. The contents are
+ determined by the <tt>BTYPE</tt> field. The length is
+ determined by <tt>MSIZE</tt> minus the size of all of
+ the other fields. Set by the initiator. Read-only.
</dd>
</dl>
</section>
<section anchor="p2p_put_processing">
<name>Processing</name>
<t>
- Upon receiving a <tt>PutMessage</tt> from a peer <tt>P</tt>
- , or created through initiation by an overlay API,
+ Upon receiving a <tt>PutMessage</tt> from a peer <tt>P</tt>,
+ or created through initiation by an overlay API,
an implementation <bcp14>MUST</bcp14> process it step by step as follows:
</t>
<ol>
