gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: clarifications; title change


From: gnunet
Subject: [lsd0001] branch master updated: clarifications; title change
Date: Fri, 20 May 2022 18:21:47 +0200

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 f34be76  clarifications; title change
f34be76 is described below

commit f34be766564619034f3f8048b74cfbb81fe0e6c8
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Fri May 20 18:21:44 2022 +0200

    clarifications; title change
---
 draft-schanzen-gns.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 5456628..8d29003 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -3330,10 +3330,10 @@ Value       Symbol            Symbol
          </ol>
        </section>
        <section anchor="day_in_zoneowner">
-         <name>A Day in the Life of a Zone Owner</name>
+         <name>Use-case: Zone Owner</name>
          <t>
            In order to become a zone owner, it is sufficient to generate
-           a zone key and a corresponding secret key.
+           a zone key and a corresponding secret key using a GNS 
implementation.
            At this point, the zone owner can manage GNS resource records in a
            local zone database.
            The resource records can then be published by a GNS implementation
@@ -3381,7 +3381,7 @@ Value       Symbol            Symbol
          </t>
        </section>
        <section>
-         <name>User-centric zone management</name>
+         <name>Use-case: End-user</name>
          <t>
            A user is expected to install a GNS implementation if it is not 
already
            provided through other means such as the operating system

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]