gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [lsd0001] branch master updated: typo


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] branch master updated: typo
Date: Fri, 04 Oct 2019 20:43:10 +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 46f7a1a  typo
46f7a1a is described below

commit 46f7a1a2604fcd7a42dd5ce64150c17146c42f88
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Oct 4 20:40:59 2019 +0200

    typo
---
 draft-schanzen-gns.html | 4 ++--
 draft-schanzen-gns.txt  | 4 ++--
 draft-schanzen-gns.xml  | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index 3dca9ad..1afd0fb 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -1152,7 +1152,7 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
 <p id="section-1-2">
        DNS was not designed with security as a goal. This makes it very
        vulnerable, especially to attackers that have the technical capabilities
-       of an entire nationstate at their disposal.
+       of an entire nation state at their disposal.
        This specification describes a censorship-resistant, privacy-preserving
        and decentralized name system: The GNU Name System (GNS). It is designed
        to provide a secure alternative to DNS, especially when censorship or
@@ -1431,7 +1431,7 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
 <figcaption><a href="#figure-5" class="selfRef">Figure 
5</a></figcaption></figure>
 </div>
 <p id="section-3.3-3">
-         NOTE: If an application uses a LEHO value in an HTTP reques header
+         NOTE: If an application uses a LEHO value in an HTTP request header
          (e.g. "Host:" header) it must be converted to a punycode 
representation
          <span>[<a href="#RFC3492" class="xref">RFC3492</a>]</span>.<a 
href="#section-3.3-3" class="pilcrow">ΒΆ</a></p>
 </section>
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index 7304aac..54cd7fb 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -93,7 +93,7 @@ Table of Contents
 
    DNS was not designed with security as a goal.  This makes it very
    vulnerable, especially to attackers that have the technical
-   capabilities of an entire nationstate at their disposal.  This
+   capabilities of an entire nation state at their disposal.  This
    specification describes a censorship-resistant, privacy-preserving
    and decentralized name system: The GNU Name System (GNS).  It is
    designed to provide a secure alternative to DNS, especially when
@@ -326,7 +326,7 @@ Internet-Draft             The GNU Name System              
   July 2019
 
                                   Figure 5
 
-   NOTE: If an application uses a LEHO value in an HTTP reques header
+   NOTE: If an application uses a LEHO value in an HTTP request header
    (e.g.  "Host:" header) it must be converted to a punycode
    representation [RFC3492].
 
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index c26989e..5dbc2cb 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -78,7 +78,7 @@
      <t>
        DNS was not designed with security as a goal. This makes it very
        vulnerable, especially to attackers that have the technical capabilities
-       of an entire nationstate at their disposal.
+       of an entire nation state at their disposal.
        This specification describes a censorship-resistant, privacy-preserving
        and decentralized name system: The GNU Name System (GNS). It is designed
        to provide a secure alternative to DNS, especially when censorship or
@@ -333,7 +333,7 @@
          <!--        <postamble>which is a very simple example.</postamble>-->
        </figure>
        <t>
-         NOTE: If an application uses a LEHO value in an HTTP reques header
+         NOTE: If an application uses a LEHO value in an HTTP request header
          (e.g. "Host:" header) it must be converted to a punycode 
representation
          <xref target="RFC3492" />.
        </t>

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



reply via email to

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