[gnunet] branch master updated: -fix typos

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new f630c5a67 -fix typos
f630c5a67 is described below

commit f630c5a675ca37467b5fba9a3dd41044381ac6ce
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Apr 23 23:58:12 2021 +0200

    -fix typos
---
 ChangeLog                  | 10 +++++-----
 README                     | 18 +++++++++---------
 bootstrap                  |  2 +-
 doc/index.html             |  2 +-
 doc/release_policy.rfc.txt | 10 +++++-----
 5 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 631c35f46..b8f45a824 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,7 +2,7 @@ Sat, 3 Apr 2021 09:40:46 +0200 (08fe7735b)
 handbook: Add section on commit messages and developer branches - Martin 
Schanzenbach
 
 Thu, 1 Apr 2021 00:41:38 +0200 (9f340d5cc)
-SETU: added some more perf messurement point for var message size - Elias 
Summermatter
+SETU: added some more perf measurement point for var message size - Elias 
Summermatter
 
 Thu, 1 Apr 2021 00:15:43 +0200 (12bb61317)
 SETU: fixed some bug in rand element gen and added variable payload for 
perfmance - Elias Summermatter
@@ -11,7 +11,7 @@ Wed, 31 Mar 2021 11:49:10 +0200 (902331756)
 SETU: Added new operation parameters for performance tests - Elias Summermatter
 
 Wed, 31 Mar 2021 11:16:38 +0200 (b5660e0a3)
-SETU: imporved tests - Elias Summermatter
+SETU: improved tests - Elias Summermatter
 
 Tue, 30 Mar 2021 19:26:40 +0200 (ca4c9eae2)
 UTIL/SCALARPRODUCT: Do not build ECC dlog or scalarproduct with incompatible 
libgcrypt versions (>=1.9.0) - Martin Schanzenbach
@@ -32,7 +32,7 @@ Thu, 18 Mar 2021 11:48:42 +0100 (f9ae0c23c)
 Added working test with randum set - Elias Summermatter
 
 Thu, 18 Mar 2021 08:45:31 +0100 (0d6237ae0)
-Added some randum elemet generation test for setu - Elias Summermatter
+Added some randum element generation test for setu - Elias Summermatter
 
 Sun, 14 Mar 2021 14:04:00 +0100 (b47586e76)
 add packaging notice; fix #5633 - Martin Schanzenbach
@@ -722,7 +722,7 @@ Thu, 30 Jan 2020 10:48:04 +0100 (015cd279b)
 added testing scripts for dns2gns - rexxnor
 
 Fri, 24 Jan 2020 16:51:29 +0100 (f4a172abf)
-export GNUNET_PQ_run_sql() functonality - Christian Grothoff
+export GNUNET_PQ_run_sql() functionality - Christian Grothoff
 
 Fri, 24 Jan 2020 16:30:45 +0100 (2fd320bc7)
 modify GNUNET_PQ_connect_with_cfg to enable flexible loading of .sql files - 
Christian Grothoff
@@ -902,7 +902,7 @@ Fri Jun 28 14:10:53 2019 +0200
 
 Thu Jun 27 10:34:46 2019 +0200
   The REST server now returns the Origin header value in the
-  CORS header reponse. -schanzen
+  CORS header response. -schanzen
 
 Thu Jun 27 09:08:06 2019 +0200
   GNS NSS plugin will not timeout and not hang forever and block
diff --git a/README b/README
index 0665a8339..665cb3818 100644
--- a/README
+++ b/README
@@ -182,7 +182,7 @@ Recommended software for developer tools:
      you, open a bug so that we can get a more portable
      fix in.
 
-[*4] We are commited  to portable tools and solutions
+[*4] We are committed  to portable tools and solutions
      where possible. New scripts should be Posix sh
      compatible, current and older scripts are
      in the process of being rewritten to comply
@@ -213,7 +213,7 @@ For a correct functionality depending on the host OS, you 
need
 to run the equivalent of these steps after installation.
 Replace $(DESTDIR)$(libexecdir) with the appropriate paths,
 for example /usr/local/lib/gnunet/libexec/. Note that this
-obviously must be run as priviledged user.
+obviously must be run as privileged user.
 
 chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn
 chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn
@@ -289,8 +289,8 @@ Building GNUnet from source
 
 IMPORTANT: You can read further notes about compilation from source in
 the handbook under doc/handbook/, which includes notes about specific
-requirements for operating systems aswell. If you are a package
-mantainer for an Operating System we invite you to add your notes if
+requirements for operating systems as well. If you are a package
+maintainer for an Operating System we invite you to add your notes if
 you feel it is necessary and can not be covered in your Operating
 System's documentation.
 
@@ -338,7 +338,7 @@ in 'contrib/services' or by running:
 
 
 Note that you must read paragraph "Notes on setuid", which documents steps you
-have to follow after the installation, as a priviledged user. We require some
+have to follow after the installation, as a privileged user. We require some
 binaries to be setuid. The most portable approach across all supported
 platforms and targets is to let this be handled manually.
 The installation will work if you do not run these steps as root, but some
@@ -376,7 +376,7 @@ $GNUNET_PREFIX you might have specified, as those libraries 
must be in
 your packaging script to miss those plugins, so you might need to do some
 additional manual work to include those libraries in your binary package(s).
 Similarly, if you want to use the GNUnet Name System and did NOT run
-GNUnet's 'make install' process with priviledged rights, the libraries will be
+GNUnet's 'make install' process with privileged rights, the libraries will be
 installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/"
 manually.
 
@@ -443,7 +443,7 @@ GNUnet by periodically executing
 $ cat $SERVICEHOME/data/hosts/* > the_file
 
 and offering 'the_file' via your web server.  Alternatively, you can
-run the build-in web server by adding '-p' to the OPTIONS value
+run the built-in web server by adding '-p' to the OPTIONS value
 in the "hostlist" section of gnunet.conf and opening the respective
 HTTPPORT to the public.
 
@@ -495,7 +495,7 @@ https://bugs.gnunet.org/ or our bugs mailinglist.
 Please make sure to run the script "contrib/scripts/gnunet-bugreport"
 and include the output with your bug reports.  More about how to
 report bugs can be found in the GNUnet FAQ on the webpage.  Submit
-patches via E-Mail to gnunet-developers@gnu.org, formated with
+patches via E-Mail to gnunet-developers@gnu.org, formatted with
 `git format-patch`.
 
 In order to run the unit tests by hand (instead of using "make check"),
@@ -540,7 +540,7 @@ Then set in the HTTP section of gnunet.conf the 
"ADVERTISED_PORT" to
 "ADVERTISED_PORT" to "443" and "PORT" to 4433.
 
 You can do the same trick for the TCP and UDP transports if you want
-to map them to a priviledged port (from the point of view of the
+to map them to a privileged port (from the point of view of the
 network).  However, we are not aware of this providing any advantages
 at this point.
 
diff --git a/bootstrap b/bootstrap
index 8fc4c4426..984c56cb3 100755
--- a/bootstrap
+++ b/bootstrap
@@ -1,7 +1,7 @@
 #!/bin/sh
 #
 # We should use /usr/bin/env sh, but some systems are notoriously picky.
-# In fact we could ommit this line if some automations wouldn't rely on
+# In fact we could omit this line if some automations wouldn't rely on
 # running this file via ./bootstrap.
 #
 # This file is in the public domain.
diff --git a/doc/index.html b/doc/index.html
index 93c0e7d9e..bf8683780 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -2,7 +2,7 @@
   <head>
     <title>GNUnet - GNUnet Manuals and Handbooks</title>
     <meta charset="utf-8">
-    <meta name="keywords" 
content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,inofficial,GNU">
+    <meta name="keywords" 
content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,unofficial,GNU">
     <meta name="description" content="The GNUnet Manuals">
     <link href="style.css" rel="stylesheet">
     <meta name="viewport" content="width=device-width, initial-scale=1">
diff --git a/doc/release_policy.rfc.txt b/doc/release_policy.rfc.txt
index 8fd89f73c..41c98ec93 100644
--- a/doc/release_policy.rfc.txt
+++ b/doc/release_policy.rfc.txt
@@ -42,7 +42,7 @@ document the current release model:
     mostly we rather explicitly declare certain bugs as "not critical")
   - Whenever API changes happen the person making that changes should update
     dependencies or at least work with people who hack on the dependencies to
-    cooridnate the adjustments
+    coordinate the adjustments
   o buildbots are happy (if running)
   o static analysis is happy (if available, false-positives => ignore)
   o documentation is reasonably up-to-date
@@ -57,7 +57,7 @@ For further information see: 
https://trunkbaseddevelopment.com/
 
 II. Evaluation Criteria 
 =======================
-(what are criterias to interprete the results as success if we review
+(what are criteria to interpret the results as success if we review
 the problem and solution after a year or so)
 
 III. Concerns (of team members)
@@ -74,7 +74,7 @@ code. I don't have a magic bullet to motivate you to write 
more tests,
 or to improve existing tests. -CG
 
   Your argument is good. Two or three of us thought that the problem is about
-  missing releases which we feld demotivating. We thought, we were stucked
+  missing releases which we feld demotivating. We thought, we were stuck
   somewhere. But as you state, it is us not doing the necessary work. What I
   still find useful is to document the release process. In consequence I
   changed the problem statement. -xrs
@@ -125,7 +125,7 @@ leaves of the dependency graph, that is great.  However, 
occasionally
 there are architectural changes. Not of the type where the graph
 changes, but where key API assumptions change. We recently had one for
 the GNU Name System with the dropping of ".gnu".  Before, CADET
-changed the semantics and paramter for 'port'.  In the future, CORE
+changed the semantics and parameter for 'port'.  In the future, CORE
 will introduce protocol versioning.  Whenever such a change happens,
 it usually falls upon the person making that change to update
 dependencies as well (or at least to work with people who hack on the
@@ -175,7 +175,7 @@ Note that none of this really adds up to a "release policy".
 V. Previous Versions
 ====================
 (if we found some flaws in the solution, and we want to change the
-release policy, we document the old ones here als previous versions.
+release policy, we document the old ones here as previous versions.
 the goal is establish a learn process.)
 
 IV. References

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