[lsd0001] branch master updated: terminology wording

[gnunet]

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 0c3e00c  terminology wording
0c3e00c is described below

commit 0c3e00cd8c113e9ff32e5ea62de5e3a32fb0a02e
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sun May 1 14:04:15 2022 +0200

    terminology wording
---
 draft-schanzen-gns.xml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 5765b17..72988d0 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -189,18 +189,18 @@
      <dl>
        <dt>Application</dt>
        <dd>
-         An application refers to a component which uses a GNS implementation
+         A component which uses a GNS implementation
          to resolve names into records and processes its contents.
        </dd>
        <dt>Resolver</dt>
        <dd>
-         The resolver is the part of the GNS implementation which provides
+         The component of a GNS implementation which provides
          the recursive name resolution logic defined in
          <xref target="resolution"/>.
        </dd>
        <dt>Zone Master</dt>
        <dd>
-         The zone master is the part of the GNS implementation which provides
+         The component of a GNS implementation which provides
          local zone management and publication as defined in
          <xref target="publish"/>.
        </dd>
@@ -233,7 +233,7 @@
        </dd>
        <dt>Apex Label</dt>
        <dd>
-         The apex label is used to publish resource
+         This type of label is used to publish resource
          records in a zone that can be resolved without providing a specific
          label. It is the GNS method to provide what is the "zone apex" in DNS
          <xref target="RFC4033"/>.
@@ -258,7 +258,7 @@
        </dd>
        <dt>Top-Level Domain</dt>
        <dd>
-        The rightmost part of a GNS name is a GNS Top-Level Domain (TLD).
+              The rightmost part of a GNS name is a GNS Top-Level Domain (TLD).
          A GNS TLD can consist of one or more labels.
         Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>),
         GNS does not expect all users to use the same global root zone. 
Instead,
@@ -279,12 +279,12 @@
        </dd>
        <dt>Zone Key</dt>
        <dd>
-         The zone key uniquely identifies a zone.
-         The zone key is usually a public key of an asymmetric key pair.
+         A key which uniquely identifies a zone.
+         It is usually a public key of an asymmetric key pair.
        </dd>
        <dt>Blinded Zone Key</dt>
        <dd>
-         A blinded zone key is derived from the zone key and a label.
+         The key derived from a zone key and a label.
          The zone key and the blinded zone key are unlinkable without 
knowledge of the label.
        </dd>
        <dt>Zone Key Derivation Function</dt>
@@ -293,7 +293,7 @@
        </dd>
        <dt>Zone Owner</dt>
        <dd>
-         The owner of a GNS zone is the holder of the secret (typically a 
private key)
+         The holder of the secret (typically a private key)
         that (together with a label and a value to sign) allows the creation 
of zone
         signatures that can be validated against the respective blinded zone 
key.
        </dd>

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