[lsd0001] branch master updated: trying to improve English / clarity

[gnunet]

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

grothoff pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 3f7b611  trying to improve English / clarity
3f7b611 is described below

commit 3f7b6118a499ac2d33211065fc90872e6bde02f9
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 17:05:29 2023 +0200

    trying to improve English / clarity
---
 draft-schanzen-gns.xml | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 87f5204..5ff50c5 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -115,8 +115,8 @@
      <t>
        This specification describes the GNU Name System (GNS), a
        censorship-resistant, privacy-preserving and decentralized
-       domain name resolution protocol.  GNS can bind names to any
-       kind of cryptographically secured token, enabling it to double
+       domain name resolution protocol.  GNS cryptographically secures
+       the binding of names to arbitrary tokens, enabling it to double
        in some respects as an alternative to some of today’s public
        key infrastructures.
      </t>
@@ -129,7 +129,10 @@
        root zone.  In the GNS reference implementation, users can
        autonomously and freely delegate control of names to zones
        through their local configurations.
-       In this model, users are expected to manage their local configurations, 
so as to avoid any confusion as to how names are resolved.
+       GNS expects each user to be in control of their setup.
+       By following <xref target="namespace_ambiguity" /> guidelines,
+       users should manage to avoid any confusion as to how names are
+       resolved.
      </t>
      <t>
        Name resolution and zone dissemination is based on the
@@ -3799,14 +3802,14 @@ Base32GNS-Decode:
        </section>
        <section>
          <name>Record sets</name>
-       
+
          <t>
            The test vectors include record sets with a variety
            of record types and flags for both PKEY and EDKEY zones.
            This includes labels with UTF-8 characters to demonstrate
            internationalized labels.
          </t>
-         <t><strong>(1) PKEY zone with ASCII label and one delegation 
record</strong></t> 
+         <t><strong>(1) PKEY zone with ASCII label and one delegation 
record</strong></t>
          <artwork name="" type="" align="left" alt="">
            <![CDATA[
 Zone private key (d, big-endian):
@@ -3911,7 +3914,7 @@ ae a4 39 91 48 d5 0c ff
 
            ]]>
          </artwork>
-         <t><strong>(2) PKEY zone with UTF-8 label and three 
records</strong></t> 
+         <t><strong>(2) PKEY zone with UTF-8 label and three 
records</strong></t>
          <artwork name="" type="" align="left" alt="">
            <![CDATA[
 Zone private key (d, big-endian):

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