[taler-docs] branch master updated: typos

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 90d7b51  typos
     new 6869fe8  Merge branch 'master' of git+ssh://git.taler.net/docs
90d7b51 is described below

commit 90d7b517a09eb765b1912bf27ef0a8f668ed84c7
Author: Christian Grothoff <address@hidden>
AuthorDate: Tue Mar 31 20:56:26 2020 +0200

    typos
---
 developers-manual.rst                 | 2 +-
 manpages/taler-auditor-exchange.1.rst | 2 +-
 manpages/taler.conf.5.rst             | 4 ++--
 taler-exchange-manual.rst             | 4 ++--
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst
index 7d1f6ab..4799dbd 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -892,7 +892,7 @@ from implementing new CMDs and traits within other 
codebases.
 
 ::
 
-   /* Withouth loss of generality, let's consider the
+   /* Without loss of generality, let's consider the
     * following logic to exist inside the run() method of CMD1 */
    ..
 
diff --git a/manpages/taler-auditor-exchange.1.rst 
b/manpages/taler-auditor-exchange.1.rst
index 219ad44..422d8b0 100644
--- a/manpages/taler-auditor-exchange.1.rst
+++ b/manpages/taler-auditor-exchange.1.rst
@@ -58,7 +58,7 @@ Bugs
 
 We should optionally verify the correctness of this exchange’s base URL
 and that it matches the master public key (note that the exchange may
-still be offline, so it should be possible to bypass such a verfication
+still be offline, so it should be possible to bypass such a verification
 step). Furthermore, if we do verification, as a (less secure)
 convenience option, we should make **-** m optional and obtain it from
 the base URL.
diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index acbfa03..0378845 100644
--- a/manpages/taler.conf.5.rst
+++ b/manpages/taler.conf.5.rst
@@ -330,7 +330,7 @@ named “[fees-METHOD]” state the (aggregate) wire transfer 
fee and the
 reserve closing fees charged by the exchange. Note that fees are
 specified using the name of the wire method, not by the plugin name. You
 need to replace “YEAR” in the option name by the calendar year for which
-the fee should apply. Usually, fees should be given for serveral years
+the fee should apply. Usually, fees should be given for several years
 in advance.
 
 WIRE-FEE-YEAR
@@ -360,7 +360,7 @@ DURATION_SPEND
    How long do clients have to spend these coins?
 
 FEE_WITHDRAW
-   What fee is charged for withdrawl?
+   What fee is charged for withdrawal?
 
 FEE_DEPOSIT
    What fee is charged for depositing?
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 89f6ad7..d7a6c21 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -148,7 +148,7 @@ components:
    Postgres
    The exchange requires a DBMS to stores the transaction history for
    the Taler exchange and aggregator, and a (typically separate) DBMS
-   for the Taler auditor. For now, the GNU Taler reference implemenation
+   for the Taler auditor. For now, the GNU Taler reference implementation
    only supports Postgres, but the code could be easily extended to
    support another DBMS.
 
@@ -698,7 +698,7 @@ the following command
 Those arguments are all mandatory.
 
 -  ``EXCHANGE_MASTER_PUB`` the base32 Crockford-encoded exchange’s
-   master public key. Tipically, this value lies in the configuration
+   master public key. Typically, this value lies in the configuration
    option ``[exchange]/master_public_key``.
 
 -  ``BLOB`` the blob generated in the previous step.

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