[taler-docs] branch master updated: english

[gnunet]

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

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new ac6f28e  english
ac6f28e is described below

commit ac6f28ecbfc116894ef82f02decfc61da52cad13
Author: MS <ms@taler.net>
AuthorDate: Mon Aug 31 13:39:53 2020 +0200

    english
---
 libeufin/bank-transport-ebics.rst | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/libeufin/bank-transport-ebics.rst 
b/libeufin/bank-transport-ebics.rst
index 0d06f83..d335c6e 100644
--- a/libeufin/bank-transport-ebics.rst
+++ b/libeufin/bank-transport-ebics.rst
@@ -27,8 +27,8 @@ The following steps are required to set up an EBICS bank 
transport:
 5. The nexus sends the public keys electronically to the bank's EBICS server, 
together with the information
    identifying the subscriber (PartnerID, UserID, SystemID).
 
-6. The user print a document that contains the public key and hashes for all 
three key pairs.
-   The user then signs this document sends it to the bank (physically/scanned).
+6. The user prints a document that contains the public key and hashes for all 
three key pairs.
+   The user then signs this document and sends it to the bank 
(physically/scanned).
 
 7. The bank receives the letter and verifies that the keys from the letter 
correspond
    to the electronically sent keys.  If they match, the bank sets the state of 
the
@@ -51,5 +51,3 @@ Alternative ways of setting up the EBICS bank transport are:
 * Importing from a backup.  The backup contains metadata (EBICS URL, HostID,
   UserId, ...) and the three passphrase-protected subscriber keys.
 * Certificate-based setup (currently not supported by LibEuFin, only used in 
France)
-
-

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