From 9afab33de06e98d791bc356d4c910bb215ca4512 Mon Sep 17 00:00:00 2001 From: MS Date: Sat, 16 Jan 2021 00:37:09 +0100 Subject: typos and rephrasing --- libeufin/nexus-tutorial.rst | 29 +++++++++++++---------------- 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst index 6e65228d..49bcc238 100644 --- a/libeufin/nexus-tutorial.rst +++ b/libeufin/nexus-tutorial.rst @@ -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 -- cgit v1.2.3