taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 3b47bac9e30cd44e49394b523ec53578e88db45f
parent 63885d038ccf5e94e267e4000411c8afeeaaead4
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 10 Feb 2024 23:02:34 +0100

fix more typos

Diffstat:
Mmanpages/taler.conf.5.rst | 2+-
Mtaler-exchange-manual.rst | 4++--
Mtaler-merchant-manual.rst | 2+-
3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst @@ -163,7 +163,7 @@ KYC_AML_TRIGGER Program to run on KYC attribute data to decide whether we should immediately flag an account for AML review. Program must return 0 if a manual AML review is not needed, and non-zero to trigger an AML review. The KYC attribute data of the new user will be passed on standard-input. STEFAN_ABS - Absolte amount to add as an offset in the STEFAN fee approximation + Absolute amount to add as an offset in the STEFAN fee approximation curve (see DD47). Defaults to CURRENCY:0 if not specified. STEFAN_LOG diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst @@ -1382,7 +1382,7 @@ started using a simple command: At this point, the exchange service is not yet fully operational. -To check whether the exchange is running correctly under the advertized +To check whether the exchange is running correctly under the advertised base URL, run: .. code-block:: shell-session @@ -1673,7 +1673,7 @@ makes the decision given the KYC attributes: The given program will be given the KYC attributes in JSON format on standard input, and must return 0 to continue without AML and non-zero to flag the -account for manual review. To disable this triger, simply leave the option to +account for manual review. To disable this trigger, simply leave the option to its default value of '[/usr/bin/]true'. To flag all new users for manual review, simply set the program to '[/usr/bin/]false'. diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst @@ -567,7 +567,7 @@ For the ``postgres`` backend, you need to specify: [merchantdb-postgres] CONFIG = "postgres:///taler-merchant" -This option specifies a PostgreSQL access path, typicallly using the format +This option specifies a PostgreSQL access path, typically using the format ``postgres:///$DBNAME``, where ``$DBNAME`` is the name of the PostgreSQL database you want to use (here, ``taler-merchant`` on the local machine). Suppose ``$USER`` is the name of the user who will run the backend process