[lsd0001] branch master updated: clarify where NICKs can be encountered, fix typo

[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 5974265  clarify where NICKs can be encountered, fix typo
5974265 is described below

commit 597426572f12db2b21a4fcc2c36e0cb14efe9a07
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Nov 10 21:09:00 2019 +0100

    clarify where NICKs can be encountered, fix typo
---
 draft-schanzen-gns.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 325d9e1..5f6e715 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -408,7 +408,8 @@
          This is a suggestion to other zones what label to use when creating a
          PKEY <xref target="gnsrecords_pkey" /> record containing this zone's
          public zone key.
-         This record SHOULD only be stored under the empty label "@".
+         This record SHOULD only be stored under the empty label "@" but
+         MAY be returned with record sets under any label.
          A NICK DATA entry has the following format:
        </t>
        <figure anchor="figure_nickrecord">
@@ -430,7 +431,7 @@
          <dt>NICKNAME</dt>
          <dd>
            A UTF-8 string (which is not 0-terminated) representing the 
preferred
-           label of the zone. This string MUST NOT inlcude a "." character.
+           label of the zone. This string MUST NOT include a "." character.
          </dd>
        </dl>
      </section>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.