commit 7b5d0c813a3942386e3d479eebf49be6a062616a
parent 9ee5d90ab358dbac83faefca0ef4ee7cf6e3ba01
Author: Christian Grothoff <christian@grothoff.org>
Date: Wed, 17 Feb 2021 12:57:23 +0100
Merge branch 'master' of git+ssh://git.taler.net/docs
Diffstat:
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/design-documents/008-fees.rst b/design-documents/008-fees.rst
@@ -42,7 +42,7 @@ Requirements
The metrics for the exchange should be advisory, i.e. an informed user should
be able to accept the withdrawal anyway.
-
+
The exchange's business interests may be in conflict with (1) a transparency of
cost for the user and and (2) restrictions on denomination/fee structures.
Thus the metrics should still allow some degree of variability between
@@ -60,7 +60,7 @@ is *reasonable*:
* For a denomination of value ``v``, either
- (a) ``v`` must be the the smallest offered denomination, or
+ (a) ``v`` must be the smallest offered denomination, or
(b) there must be another denomination with a value of at least ``v / 10``.
Is there a relationship between the smallest denomination and the size of fees?
diff --git a/design-documents/010-exchange-helpers.rst b/design-documents/010-exchange-helpers.rst
@@ -157,7 +157,7 @@ Alternatives
* The helpers could have been started by the exchange. This would have
required the helpers use SUID. Allowing the system administrator to start
them as they see fit is more flexible with respect to the privilege
- configuration. Also, this avoid forcing the the exchange to manage
+ configuration. Also, this avoid forcing the exchange to manage
restarting on crashes and/or crash reporting.
diff --git a/manpages/taler-exchange-offline.1.rst b/manpages/taler-exchange-offline.1.rst
@@ -391,7 +391,7 @@ an older "enable" (or "disable") message after a more recent "disable" (or
to keep the actual files exchanged with the offline tool secret.
The **taler-exchange-offline** tool tries to make sure that the online signing
-keys of the the exchange are always created by the same two security modules.
+keys of the exchange are always created by the same two security modules.
The goal here is to prevent an attacker who compromised **taler-exchange-httpd**
but *not* the security modules from providing attacker-controlled keys to the
offline signing process.
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
@@ -235,7 +235,7 @@ Functionality
^^^^^^^^^^^^^
The UNIX domain sockets have mode 0620 (u+rw, g+w). The exchange process
-MUST be in the same group as the the crypto helper processes.
+MUST be in the same group as the crypto helper processes.
The two helper processes will create the required private keys, and allow
anyone with access to the UNIX domain socket to sign arbitrary messages with
