commit e39bfac4e21e148d27690eaae57cf243da8130f7
parent 5fb7da06ae51f21afe087d569c7d2a0c16d2ab88
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sun, 14 Jul 2024 09:06:48 +0200
fine tune terminology
Diffstat:
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -225,7 +225,7 @@
<dt>Address</dt>
<dd>
<t>
- An <em>Address</em> is a UTF-8 <xref target="RFC3629"/> string which can be
+ An <em>address</em> is a UTF-8 <xref target="RFC3629"/> string which can be
used to address a <em>peer</em> through the Underlay (<xref target="underlay"/>).
The format of an address is not enforced by this specification,
but it is expected that in most cases the address is a URI <xref target="RFC3986"/>.
@@ -281,9 +281,8 @@
</dd>
<dt>HELLO block</dt>
<dd>
- A <tt>HELLO block</tt> is a <em>block</em> with a <em>block-type</em> <tt>DHT_HELLO</tt> (13).
- A <tt>HELLO block</tt> is used to store and retrieve <em>addresses</em> of a <em>peer</em>.
- <tt>HELLO</tt> blocks are used by the peer discovery mechanism in <xref target="find_peer"/>.
+ A <tt>HELLO block</tt> is a type of <em>block</em> that is used to store and retrieve <em>addresses</em> of a <em>peer</em>.
+ It are used by the peer discovery mechanism in <xref target="find_peer"/>.
</dd>
<dt>HELLO URL</dt>
<dd>
@@ -294,10 +293,10 @@
</dd>
<dt>Key</dt>
<dd>
- 512-bit identifier of a location in the DHT. Multiple <tt>Blocks</tt> can be
+ 512-bit identifier of a location in the DHT. Multiple <tt>blocks</tt> can be
stored under the same <em>key</em>. A <em>peer identity</em> is also a <tt>key</tt>.
In the context of "key-value stores" this
- refers to "key" under which values (<em>blocks</em>) are stored.
+ refers to "key" under which <em>blocks</em> are stored.
</dd>
<dt>Message Processing</dt>
<dd>