1 files changed, 67 insertions, 62 deletions

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index d47ae9c..e0b38de 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -187,23 +187,55 @@
    <section>
      <name>Terminology</name>
      <dl>
+       <dt>Apex Label</dt>
+       <dd>
+         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"/>.
+         The apex label is represented using the character U+0040 ("@" without
+         the quotes).
+       </dd>
        <dt>Application</dt>
        <dd>
          A component which uses a GNS implementation
          to resolve names into records and processes its contents.
        </dd>
-       <dt>Resolver</dt>
+       <dt>Blinded Zone Key</dt>
        <dd>
-         The component of a GNS implementation which provides
-         the recursive name resolution logic defined in
-         <xref target="resolution"/>.
+         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 Master</dt>
+
+       <dt>Extension Label</dt>
        <dd>
-         The component of a GNS implementation which provides
-         local zone management and publication as defined in
-         <xref target="publish"/>.
+         The primary use for the extension label is in redirections where the redirection
+         target is defined relative to the authoritative zone of the redirection
+         record (<xref target="gnsrecords_redirect"/>).
+         The extension label is represented using the character U+002B ("+"
+         without the quotes).
        </dd>
+       <dt>Label Separator</dt>
+       <dd>
+         Labels in a name are separated using the label separator U+002E
+         ("." without the quotes).
+         In GNS, with the exceptions of zone Top-Level Domains
+         (see below) and boxed records (see <xref target="gnsrecords_box"/>),
+         every separator label in a name delegates to another zone.
+       </dd>
+       <dt>Label</dt>
+       <dd>
+         A GNS label is a label as defined in <xref target="RFC8499"/>.
+         Labels are UTF-8 strings in Unicode
+         Normalization Form C (NFC) <xref target="Unicode-UAX15"/>.
+         The apex label, label separator and the extension label have
+         special purposes in the resolution protocol which are defined
+         in the rest of the document.
+         Zone administrators <bcp14>MAY</bcp14> disallow certain labels that
+         might be easily confused with other labels through registration policies
+         (see also <xref target="security_abuse"/>).
+       </dd>
+
        <dt>Name</dt>
        <dd>
          A name in GNS is a domain name as defined in  <xref target="RFC8499"/>
@@ -219,43 +251,28 @@
          specific user expectations, for example according to
          <xref target="Unicode-UTS46"/>.
        </dd>
-       <dt>Label</dt>
-       <dd>
-         A GNS label is a label as defined in <xref target="RFC8499"/>.
-         Labels are UTF-8 strings in Unicode
-         Normalization Form C (NFC) <xref target="Unicode-UAX15"/>.
-         The apex label, label separator and the extension label have
-         special purposes in the resolution protocol which are defined
-         in the rest of the document.
-         Zone administrators <bcp14>MAY</bcp14> disallow certain labels that
-         might be easily confused with other labels through registration policies
-         (see also <xref target="security_abuse"/>).
-       </dd>
-       <dt>Apex Label</dt>
+       <dt>Resolver</dt>
        <dd>
-         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"/>.
-         The apex label is represented using the character U+0040 ("@" without
-         the quotes).
+         The component of a GNS implementation which provides
+         the recursive name resolution logic defined in
+         <xref target="resolution"/>.
        </dd>
-       <dt>Extension Label</dt>
+       <dt>Resource Record</dt>
        <dd>
-         The primary use for the extension label is in redirections where the redirection
-         target is defined relative to the authoritative zone of the redirection
-         record (<xref target="gnsrecords_redirect"/>).
-         The extension label is represented using the character U+002B ("+"
-         without the quotes).
+         A GNS resource record is the information associated with a label in a
+         GNS zone.
+         A GNS resource record contains information as defined by its
+         resource record type.
        </dd>
-       <dt>Label Separator</dt>
+       <dt>Start Zone</dt>
        <dd>
-         Labels in a name are separated using the label separator U+002E
-         ("." without the quotes).
-         In GNS, with the exceptions of zone Top-Level Domains
-         (see below) and boxed records (see <xref target="gnsrecords_box"/>),
-         every separator label in a name delegates to another zone.
+         In order to resolve any given GNS name an initial start zone must be
+         determined for this name.
+         The start zone can be explicitly defined through a zTLD.
+         Otherwise, it is determined through a local suffix-to-zone mapping
+         (see <xref target="governance"/>).
        </dd>
+
        <dt>Top-Level Domain</dt>
        <dd>
                The rightmost part of a GNS name is a GNS Top-Level Domain (TLD).
@@ -272,25 +289,22 @@
          A zone is uniquely identified by its zone key.  Unlike DNS zones,
          a GNS zone does not need to have a SOA record under the apex label.
        </dd>
-       <dt>Zone Type</dt>
-       <dd>
-         The type of a GNS zone determines the cipher system and binary encoding
-         format of the zone key, blinded zone keys, and signatures.
-       </dd>
        <dt>Zone Key</dt>
        <dd>
          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>
-         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>
        <dd>
          The zone key derivation function (ZKDF) blinds a zone key using a label.
        </dd>
+
+       <dt>Zone Master</dt>
+       <dd>
+         The component of a GNS implementation which provides
+         local zone management and publication as defined in
+         <xref target="publish"/>.
+       </dd>
        <dt>Zone Owner</dt>
        <dd>
          The holder of the secret (typically a private key)
@@ -306,20 +320,11 @@
          A zTLD label sequence can only be distinguished from ordinary TLD label sequences
          by attempting to decode the labels into a zone type and zone key.
        </dd>
-       <dt>Start Zone</dt>
-       <dd>
-         In order to resolve any given GNS name an initial start zone must be
-         determined for this name.
-         The start zone can be explicitly defined through a zTLD.
-         Otherwise, it is determined through a local suffix-to-zone mapping
-         (see <xref target="governance"/>).
-       </dd>
-       <dt>Resource Record</dt>
+
+       <dt>Zone Type</dt>
        <dd>
-         A GNS resource record is the information associated with a label in a
-         GNS zone.
-         A GNS resource record contains information as defined by its
-         resource record type.
+         The type of a GNS zone determines the cipher system and binary encoding
+         format of the zone key, blinded zone keys, and signatures.
        </dd>
      </dl>
    </section>