[taler-docs] branch master updated: nexus man: omit implementation detail

[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 76459a60 nexus man: omit implementation detail
76459a60 is described below

commit 76459a6058236db94a7378991d7a48d3249ab9d5
Author: MS <ms@taler.net>
AuthorDate: Mon Nov 20 15:36:31 2023 +0100

    nexus man: omit implementation detail
---
 manpages/libeufin-nexus.1.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manpages/libeufin-nexus.1.rst b/manpages/libeufin-nexus.1.rst
index 9aa88ce8..31eb7aa1 100644
--- a/manpages/libeufin-nexus.1.rst
+++ b/manpages/libeufin-nexus.1.rst
@@ -98,7 +98,7 @@ Its options are as follows:
 ebics-fetch
 -----------
 
-This subcommands download banking records via EBICS.  By default it downloads 
notifications, in the form of ``camt.054``.  It looks for the most recent 
incoming transaction and asks the bank any notification starting from such 
timestamp.  Along the download, ebics-fetch would bounce incoming payments that 
do not have a valid Taler subject, or as well those with an already existing 
valid subject.  Valid incoming payments are then stored in the database so that 
they can trigger Taler withd [...]
+This subcommand downloads banking records via EBICS and stores them into the 
database.  By default, it downloads ``camt.054`` notifications.  Along the 
download, ebics-fetch would bounce incoming payments that do not have a valid 
Taler subject, or as well those with an already existing valid subject.  Valid 
incoming payments are then stored in the database so that they can trigger 
Taler withdrawals.  Along this process, ebics-submit would as well reconcile 
initiated outgoing payments wit [...]
 
 **-h** \| **--help**
    Print short help on options.

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