lsd0004

commit 72e140fc2b25c07fe3249df18b2877f9333ed6fb
parent 484c36781226ea9a7162a596825844e491ac0e29
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon,  1 Aug 2022 11:06:25 +0200

fi

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

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -1140,8 +1140,8 @@ BEGIN
           The signature of a Path Element is created by the current hop
           after it made its routing decision identifiying the successor peer.
           The wire format of an example path from Peers A over B and C as it
-          would be received by D in a is illustrated in <xref target="figure_path_ex"/>.
-          <tt>PutMessage</tt> or <tt>ResultMessage</tt>.
+           would be received by D in a <tt>PutMessage</tt> or <tt>ResultMessage</tt>
+          is illustrated in <xref target="figure_path_ex"/>.
           A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field
           a length of 3.
           A <tt>PutMessage</tt> would indicate a length of 3 as the sum of
@@ -1215,8 +1215,8 @@ BEGIN
           The wire format of a truncated example path from Peers B over C to D
             is illustrated in <xref target="figure_path_ex_trunc"/>.
           The wire format of an example path from Peers B over C as it
-          would be received by D in a is illustrated in <xref target="figure_path_ex_trunc"/>.
-          <tt>PutMessage</tt> or <tt>ResultMessage</tt>.
+          would be received by D in a <tt>PutMessage</tt> or <tt>ResultMessage</tt>
+          is illustrated in <xref target="figure_path_ex_trunc"/>.
           A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field
           a length of 1.
           A <tt>PutMessage</tt> would indicate a length of 1 as the sum of