[Top][All Lists]

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

[taler-docs] branch master updated: fix more typos

From: gnunet
Subject: [taler-docs] branch master updated: fix more typos
Date: Wed, 28 Apr 2021 00:17:59 +0200

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 02182e9  fix more typos
02182e9 is described below

commit 02182e9324ab8dce6d5ab41310be0c0bf11343aa
Author: Christian Grothoff <>
AuthorDate: Wed Apr 28 00:17:18 2021 +0200

    fix more typos
 taler-exchange-manual.rst | 2 +-
 taler-merchant-manual.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index aa9dcdd..a143d49 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -955,7 +955,7 @@ Internal audits
 While an exchange should use an external auditor to attest to regulators that
 it is operating correctly, an exchange operator can also use the auditor's
-logic to perform internal checks.  For this, an exchange opeator can generally
+logic to perform internal checks.  For this, an exchange operator can generally
 follow the auditor guide.  However, instead of using ``taler-auditor-sync``,
 an internal audit can and likely should be performed either directly against
 the production exchange database or against a synchronous copy created using
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 3fcdc55..6782c7e 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -1096,7 +1096,7 @@ authentication, including TLS client certificates, HTTP 
basic and digest
 authentication and others, which can all be used (possibly in combination) to
 restrict access to the internal API to authorized clients.
-System admininistrators are strongly advised to test their access control
+System administrators are strongly advised to test their access control
 setup before going into production!

To stop receiving notification emails like this one, please contact

reply via email to

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