summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <grothoff@gnunet.org>2021-11-29 17:55:09 +0100
committerChristian Grothoff <grothoff@gnunet.org>2021-11-29 17:55:09 +0100
commit67c8b098e7388e88acfdcffca00741794cfe65e7 (patch)
tree1b1f687ace41b9ab12b27569f27e3e110bc46e2d
parent5cbf2d123deac43033028b2c1c91a88b88eec6ba (diff)
downloaddocs-67c8b098e7388e88acfdcffca00741794cfe65e7.tar.gz
docs-67c8b098e7388e88acfdcffca00741794cfe65e7.tar.bz2
docs-67c8b098e7388e88acfdcffca00741794cfe65e7.zip
fix typos
-rw-r--r--manpages/TDM.el2
-rw-r--r--manpages/taler-exchange-aggregator.1.rst2
-rw-r--r--manpages/taler-exchange-offline.1.rst2
-rw-r--r--taler-auditor-manual.rst6
-rw-r--r--taler-exchange-setup-guide.rst4
5 files changed, 8 insertions, 8 deletions
diff --git a/manpages/TDM.el b/manpages/TDM.el
index 98a9a46..b4fabc7 100644
--- a/manpages/TDM.el
+++ b/manpages/TDM.el
@@ -25,7 +25,7 @@
;; This library currently provides one command: ‘TDM-convert-options’.
;; The intended workflow is simple:
;; - Create a new file from template.
-;; - Do the <FOO> subtitutions / deletions as necessary.
+;; - Do the <FOO> substitutions / deletions as necessary.
;; - Split the window, one half for Synopsis, one for Description.
;; - Do ‘COMMAND --help’ and copy the portion of its output that
;; describes the options into the buffer in the Synopsis section.
diff --git a/manpages/taler-exchange-aggregator.1.rst b/manpages/taler-exchange-aggregator.1.rst
index c74b376..87a5cd7 100644
--- a/manpages/taler-exchange-aggregator.1.rst
+++ b/manpages/taler-exchange-aggregator.1.rst
@@ -59,7 +59,7 @@ The aggregator uses a special table to lock shards it is working on. If an aggre
Print version information.
**-y** \| **--kyc-off**
- Run without KYC checks. Talk with your regualtor before using this option.
+ Run without KYC checks. Talk with your regulator before using this option.
See Also
diff --git a/manpages/taler-exchange-offline.1.rst b/manpages/taler-exchange-offline.1.rst
index 4641b41..18d5399 100644
--- a/manpages/taler-exchange-offline.1.rst
+++ b/manpages/taler-exchange-offline.1.rst
@@ -218,7 +218,7 @@ enable-account
--------------
This subcommand
-informs an exchange that it should advertize a bank account as belonging to
+informs an exchange that it should advertise a bank account as belonging to
the exchange on its ``/wire`` endpoint. Note that this does *not* ensure that
the exchange will use this bank account for incoming or outgoing wire
transfers! For this, the **taler-exchange-transfer** and
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 5aaae57..cf3952f 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -633,14 +633,14 @@ to perform database replication. This is done using:
$ echo "CREATE PUBLICATION $NAME FOR ALL TABLES;" | psql taler-exchange
The exchange must share the password of the publication with the auditor. A
-good ``$NAME`` relates to the auditor's buisness unit name. A secure tunnel
+good ``$NAME`` relates to the auditor's business unit name. A secure tunnel
must be setup between the exchange and the auditor, for example using SSH or
Wireguard.
It is also necessary to edit ``main.cf`` of the exchange and on the auditor
side to enable logical replication. If an exchange has multiple auditors, it
should setup multiple ``egress`` accounts. The exchange must ensure that
-the following lines are in the ``main.cf`` Postgres configuaration (the port
+the following lines are in the ``main.cf`` Postgres configuration (the port
may differ) to enable replication over the network:
.. code-block::
@@ -650,7 +650,7 @@ may differ) to enable replication over the network:
wal_level= logical
Equally, the auditor must configure logical replication in the ``main.cf``
-Postgres configuaration:
+Postgres configuration:
.. code-block::
diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index be105d2..049c5ff 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -366,7 +366,7 @@ a backup copy* of such keys.
$CONNECTION_NAME
At this point, Nexus needs to both communicate its keys to the bank, and
-download the bank's keys. This syncronization happens through the INI, HIA, and
+download the bank's keys. This synchronization happens through the INI, HIA, and
finally, HPB message types.
After the electronic synchronization, the subscriber must confirm their keys
@@ -386,7 +386,7 @@ such letter:
..
FIXME: Maybe is not 100% clear that 'connecting' means exchanging keys
- wiht the bank?
+ with the bank?
Once the connection is synchronized, Nexus needs to import locally the data
corresponding to the bank accounts offered by the bank connection just made.