[taler-docs] branch master updated (9647548 -> 5b85c92)

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a change to branch master
in repository docs.

    from 9647548  add period at end of sentence
     new 7ecf07e  write "Nexus" w/ initial upcase latter
     new 76768de  write "LibEuFin" in camel case
     new 92cd9f1  add period at end of sentence
     new 5b85c92  write "PostgreSQL" like so

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 taler-exchange-setup-guide.rst | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index c17ac6f..c880b40 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -49,9 +49,9 @@ To deploy this with a real bank, you need:
 
 Information to write down during the installation:
 
-* libeufin nexus superuser password
+* LibEuFin Nexus superuser password
 * Taler facade base URL
-* exchange nexus username and password
+* exchange Nexus username and password
 
 
 
@@ -61,7 +61,7 @@ Installation
 We assume that the system is a minimal installation of Ubuntu 20.04 LTS.
 Ideally, you should have two hosts, ``exchange-online`` and
 ``exchange-offline``.  It is also possible to run the HTTPS nginx server or
-the Postgres database on yet another host, but in these instructions we will
+the PostgreSQL database on yet another host, but in these instructions we will
 assume that only two hosts are used. Alas, the instructions will also work if
 you run everything on one system, but then you have the security drawback of
 not keeping the high-security private keys disconnected from the Internet.
@@ -160,7 +160,7 @@ to compartmentalize different parts of the system:
 * taler-exchange-secmod-eddsa: manages the EdDSA private online signing keys.
 * taler-exchange-closer: closes idle reserves by triggering wire transfers 
that refund the originator.
 * taler-exchange-aggregator: aggregates deposits into larger wire transfer 
requests.
-* taler-exchange-wire: performs wire transfers with the bank (via 
libeufin/nexus).
+* taler-exchange-wire: performs wire transfers with the bank (via 
LibEuFin/Nexus).
 * postgres: runs the Postgres database (from *postgres* package).
 * www-data: runs the frontend HTTPS service with the TLS keys (from *nginx* 
package).
 
@@ -282,7 +282,7 @@ service that provides a JSON abstraction layer to access 
bank accounts.
 
 The Nexus currently uses an sqlite3 database as storage by default.
 We currently recommend to stick with this default.  In future
-versions, there will be a migration path to a postgresql database.
+versions, there will be a migration path to a PostgreSQL database.
 
 The HTTP port and database connection string can be edited in the 
configuration:
 
@@ -326,7 +326,7 @@ to create less privileged users is offered.
 Connecting Nexus with an EBICS account
 --------------------------------------
 
-The command line interface of the LibEuFin nexus needs the following three
+The command line interface of the LibEuFin Nexus needs the following three
 values to be defined in the environment: ``LIBEUFIN_NEXUS_URL``,
 ``LIBEUFIN_NEXUS_USERNAME``, and ``LIBEUFIN_NEXUS_PASSWORD``.  In this example,
 ``LIBEUFIN_NEXUS_USERNAME`` should be set to ``admin``, and
@@ -334,7 +334,7 @@ values to be defined in the environment: 
``LIBEUFIN_NEXUS_URL``,
 previous step (the ``libeufin-nexus superuser`` command).  The
 ``LIBEUFIN_NEXUS_URL`` could be given as ``http://localhost:5017/``.
 
-Next, we create a EBICS *bank connection* that nexus can use to communicate 
with the bank.
+Next, we create a EBICS *bank connection* that Nexus can use to communicate 
with the bank.
 
 .. code-block:: console
 
@@ -430,7 +430,7 @@ list of transactions, and making a payment.
 Testing: Requesting the transaction history
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The LibEuFin nexus keeps a local copy of the bank account's transaction
+The LibEuFin Nexus keeps a local copy of the bank account's transaction
 history.  Before querying transactions locally, it is necessary
 to request transactions for the bank account via the bank connection.
 
@@ -495,7 +495,7 @@ in the next step, to **send the payment instructions to the 
bank**:
 Automatic scheduling
 ~~~~~~~~~~~~~~~~~~~~
 
-With an EBICS bank connection, the LibEuFin nexus needs to regularly query for
+With an EBICS bank connection, the LibEuFin Nexus needs to regularly query for
 new transactions and (re-)submit prepared payments.
 
 It is possible to schedule these tasks via an external task scheduler such as
@@ -656,14 +656,14 @@ exchange processes should not have access to this 
information.
 
   [exchange-accountcredentials-1]
 
-  # LibEuFin expects basic auth
+  # LibEuFin expects basic auth.
   wire_gateway_auth_method = basic
 
-  # username and password set in LibEuFin
+  # username and password set in LibEuFin.
   username = ...
   password = ...
 
-  # base URL of the wire gateway set up with LibEuFin
+  # base URL of the wire gateway set up with LibEuFin.
   wire_gateway_url = ...
 
 
@@ -682,7 +682,7 @@ Exchange Database Setup
 =======================
 
 The access credentials for the exchange's database are configured in
-``/etc/taler/secrets/exchange-db.secret.conf``.  Currently, only postgres is
+``/etc/taler/secrets/exchange-db.secret.conf``.  Currently, only PostgreSQL is
 supported as a database backend.
 
 The following users must have access to the exchange database:
@@ -724,7 +724,7 @@ in the configuration file would simply be:
 
 
 If the database is run on a different host, please follow the instructions
-from the Postgres manual for configuring remote access.
+from the PostgreSQL manual for configuring remote access.
 
 After configuring the database credentials, the exchange database needs
 to be initialized with the following command:

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.