[taler-docs] branch master updated (44e89d9 -> 9afab33)

[gnunet]

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

ms pushed a change to branch master
in repository docs.

    from 44e89d9  cosmetic
     new bdf0f32  elaborate more
     new a6b1d52  cosmetic
     new 9afab33  typos and rephrasing

The 3 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:
 libeufin/nexus-tutorial.rst | 33 +++++++++++++++------------------
 1 file changed, 15 insertions(+), 18 deletions(-)

diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst
index 498db70..49bcc23 100644
--- a/libeufin/nexus-tutorial.rst
+++ b/libeufin/nexus-tutorial.rst
@@ -132,8 +132,8 @@ the sandbox.  The EBICS parameters identify the subscriber 
that should have
 access to the bank account via EBICS.
 
 To populate the account with some test transactions, run the following command
-(note that we use the bankaccount subcommand, as this command is not
-EBICS-specific!):
+(note that we use the *bankaccount* subcommand, because there is no need to 
rely
+on EBICS):
 
 .. code-block:: console
 
@@ -194,12 +194,11 @@ and ``LIBEUFIN_NEXUS_PASSWORD``.  In this example, 
``LIBEUFIN_NEXUS_USERNAME`` s
 set to ``foo``, and ``LIBEUFIN_NEXUS_PASSWORD`` to the value given for its 
password
 in step (2).
 
-Next, we will create an 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.
 
 .. note::
 
-   For the sandbox set up in this guide, the EBICS base URL
+   For the sandbox setup in this guide, the EBICS base URL
    is ``http://localhost:5000/ebicsweb``.
 
 .. code-block:: console
@@ -227,12 +226,13 @@ a backup copy* of such keys.
           --output-file $BACKUP_FILE \
           $CONNECTION_NAME
 
-At this point, Nexus must communicate all the details to the bank.  Therefore,
-it will synchronize the connection.  In this EBICS example, Nexus will send
-the *INI* and *HIA* messages to the bank.
+At this point, Nexus needs to both communicate its keys to the bank, and
+download the bank's.  This syncronization happens through the INI, HIA, and
+finally HPB message types.
 
-Now that the bank has received the public keys of the subscriber 
electronically,
-it also needs to verify them offline.  For this, the nexus can generate a key 
letter:
+After the electronic synchronization, the subscriber must confirm their keys
+by sending a physical mail to the bank.  The following command helps generating
+such letter:
 
 .. code-block:: console
 
@@ -240,9 +240,6 @@ it also needs to verify them offline.  For this, the nexus 
can generate a key le
 
 .. note::
 
-   The resulting PDF should be sent to the bank, which will verify
-   that the keys printed in it match the keys sent electronically.
-
    When using the LibEuFin sandbox, subscribers are automatically
    activated after keys are received electronically.
 
@@ -273,7 +270,7 @@ It is now possible to list the accounts offered by the 
connection.
         list-offered-bank-accounts \
           $CONNECTION_NAME
 
-Nexus now needs an explicit import of the accounts it should to manage.  This
+Nexus now needs an explicit import of the accounts it should manage.  This
 step is needed to let the user pick a custom name for such accounts.
 
 .. code-block:: console
@@ -281,7 +278,7 @@ step is needed to let the user pick a custom name for such 
accounts.
   $ libeufin-cli
       connections \
         import-bank-account \
-          --offered-account-id $ACCOUNT_NATIVE_NAME \
+          --offered-account-id testacct01 \
           --nexus-bank-account-id $CUSTOM_RENAMING_FOR_ACCOUNT \
           $CONNECTION_NAME
 
@@ -313,8 +310,8 @@ This command asks Nexus to *download the latest bank 
statements*:
 .. note::
 
    By default, the latest available transactions are fetched.  It is also
-   possible to specify a custom data range (or even all available transactions)
-   and the type of transactions to fetch ( inter-day statements or intra-day
+   possible to specify a custom date range (or even all available transactions)
+   and the type of transactions to fetch (inter-day statements or intra-day
    reports).
 
 Once Nexus stored all the information in the database, the
@@ -353,7 +350,7 @@ Note: the ``$AMOUNT`` value needs the format 
``X.Y:CURRENCY``; for example
 ``10:EUR``, or ``1.01:EUR``.
 
 The previous command should return a value (``$UUID``) that uniquely
-identifies the prepared payment in the Nexus system.  It'll be needed
+identifies the prepared payment in the Nexus system.  That is needed
 in the next step, to **send the payment instructions to the bank**:
 
 .. code-block:: console

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