commit f032f46c73f37efb02a230ebcd6e741d0a2960d0
parent 8ce1befc020379ffb8feee1a5686a697c77935a5
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 18 Oct 2022 17:22:36 +0900
typos
Diffstat:
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/users/gns.rst b/users/gns.rst
@@ -22,7 +22,7 @@ records and petnames. A petname is a name that can be freely chosen by
the user. This results in non-unique name-value mappings as www.bob to
one user might be www.friend for someone else.
-For a complete specification of the protocl, we refer to `LSD0001 <https://lsd.gnunet.org/lsd0001>`__.
+For a complete specification of the protocol, we refer to `LSD0001 <https://lsd.gnunet.org/lsd0001>`__.
Start Zones
~~~~~~~~~~~
@@ -44,7 +44,7 @@ External
""""""""
Your GNUnet installation ships with a default configuration of *Start Zones*.
-The first is ``.gnunet.org``, which points to the authoritate zone of the
+The first is ``.gnunet.org``, which points to the authoritative zone of the
GNUnet project.
This *Start Zone* allows you to resolve names ending with ``.gnunet.org``.
It can be used to resolve, for example, ``www.gnunet.org``.
@@ -58,7 +58,7 @@ You can try it out for yourself (if you are connected to the peer-to-peer networ
Another *Start Zone* configured by default is ``.pin``.
It points to a special zone also managed by the GNUnet project.
-Users may register submodomains on a first-come first-served-basis at https://fcfs.gnunet.org.
+Users may register subdomains on a first-come first-served-basis at https://fcfs.gnunet.org.
Use ``gnunet-config -s gns`` to view the GNS configuration, including all
configured external zones that are operated by other users.
@@ -131,7 +131,7 @@ zTLD, you can do so as follows:
$ gnunet-gns --lookup=www.000G0047M3HN599H57MPXZK4VB59SWK4M9NRD68E1JQFY3RWAHDMKAPN30
The use of zTLDs is mostly useful in the absence of a *Start Zone* configuration
-for that zone or when querying names programatically.
+for that zone or when querying names programmatically.
Local zone maintenance
~~~~~~~~~~~~~~~~~~~~~~
@@ -288,7 +288,7 @@ deliberately expensive, to deter people from doing this just for fun (as
the actual revocation operation is expensive for the network, not for
the peer performing the revocation).
-To avoid TL;DR ones from accidentally revocating their zones, we are not
+To avoid TL;DR ones from accidentally revoking their zones, we are not
giving away the command, but it is uncomplicated: the actual revocation
is performed by using the ``-p`` option of ``gnunet-revocation``.
@@ -346,7 +346,7 @@ We can distinguish between two types of applications:
1. **GNS-aware applications**: Such applications know what GNS is and how it
can be used to resolve names. Examples are some of GNUnet's services such
as `re:claimID <reclaimID-Identity-Provider>`_ or `Messenger <Using-the-GNUnet-Messenger>`_.
- 2. **GNS-unaware applications**: Applications that implicity assume the names
+ 2. **GNS-unaware applications**: Applications that implicitly assume the names
are resolved through DNS. Such applications use OS-specific APIs or query
configured DNS servers directly.
@@ -361,7 +361,7 @@ in order to translate DNS name queries by applications to GNS name
queries where applicable and else fall back to DNS.
Optionally, you may want to configure your dns2gns service to run on a
-non-priviledged port like 5353. But, in case you are going to edit
+non-privileged port like 5353. But, in case you are going to edit
``/etc/resolv.conf`` directly, the dns2gns service MUST run on port 53
as you cannot specify the port number. A ``$FALLBACK_DNS`` variable
should be a DNS server you trust such as your local router:
@@ -523,7 +523,7 @@ The .pin zone
First, you may want to visit https://fcfs.gnunet.org and register your zone(s)
with the ``.pin`` top-level domain shipped by default with GNUnet.
This will allow other GNUnet users to resolve your zone under the name you
-managed to aquire for yourself.
+managed to acquire for yourself.
The registration policy of PIN is "first-come, first-served".
@@ -656,7 +656,7 @@ In addition, GNS supports DNS record types, such as `A`, `AAAA` or `TXT`.
For a complete description of the records, please refer to the
specification at `LSD0001 <https://lsd.gnunet.org/lsd0001>`__.
-In the following, we discuss GNS records with specific behaviour or
+In the following, we discuss GNS records with specific behavior or
special handling in GNUnet.
