summaryrefslogtreecommitdiff
path: root/taler-merchant-manual.rst
diff options
context:
space:
mode:
Diffstat (limited to 'taler-merchant-manual.rst')
-rw-r--r--taler-merchant-manual.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 6d148068..1e6e72a1 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -87,7 +87,7 @@ components:
to process financial transactions with Taler. This manual primarily
describes how to install and configure this backend.
- A DBMS which stores the transaction history for the Taler backend.
- For now, the GNU Taler reference implemenation only supports
+ For now, the GNU Taler reference implementation only supports
Postgres, but the code could be easily extended to support another
DBMS. Please review the Postgres documentation for details on
how to configure the database.
@@ -1100,7 +1100,7 @@ in a special “402 Payment Required” response inside the ``X-Taler-Tip``
header.
The frontend should handle errors returned by the backend, such as
-missconfigured instances or a lack of remaining funds for tipping.
+misconfigured instances or a lack of remaining funds for tipping.
.. _Picking-up-of-the-tip:
@@ -1336,7 +1336,7 @@ second gives the chance to leave some payments unaggregated, and also to
use merchant instances other than the default (which is, actually, the
one used by default by the tool).
-Note: the abilty of driving the aggregation policy is useful for testing
+Note: the ability of driving the aggregation policy is useful for testing
the backoffice facility.
Any subcommand is also equipped with the canonical ``--help`` option, so
@@ -1410,7 +1410,7 @@ layout:
[PAYMENTS-GENERATOR]
# The exchange used during the test: make sure the merchant backend
- # being tested accpets this exchange.
+ # being tested accepts this exchange.
# If the sysadmin wants, she can also install a local exchange
# and test against it.
EXCHANGE = https://exchange.demo.taler.net/