[taler-docs] branch master updated: -fix #6966

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 85a3127  -fix #6966
85a3127 is described below

commit 85a3127d828260222f3232e99046523c266625d1
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Aug 1 12:24:25 2021 +0200

    -fix #6966
---
 manpages/taler-exchange-offline.1.rst | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/manpages/taler-exchange-offline.1.rst 
b/manpages/taler-exchange-offline.1.rst
index f3036be..b1beaf2 100644
--- a/manpages/taler-exchange-offline.1.rst
+++ b/manpages/taler-exchange-offline.1.rst
@@ -30,12 +30,15 @@ the exchange’s long-term offline signing key and should be 
run in a secure
 subcommands as arguments which are then processed sequentially.
 
 The tool includes two subcommands to interact *online* with the exchange's
-REST APIs.  The ``download`` subcommand downloads the future public keys from 
the
-running exchange.  The resulting data serves as input to the ``sign`` and 
``show``
-subcommands.  The ``upload`` subcommand uploads the signatures created with the
-private master key to the exchange.  It handles the output of all subcommands
-(except ``download``).  The ``download`` and ``upload`` subcommands must 
naturally be
-run "online" and do not require access to the offline key.
+REST APIs.  To determine how to talk to the exchange, these two subcommands
+rely on the ``BASE_URL`` configuration option from the ``[exchange]`` section
+of the configuration file.  The ``download`` subcommand downloads the future
+public keys from the running exchange.  The resulting data serves as input to
+the ``sign`` and ``show`` subcommands.  The ``upload`` subcommand uploads the
+signatures created with the private master key to the exchange.  It handles
+the output of all subcommands (except ``download``).  The ``download`` and
+``upload`` subcommands must naturally be run "online" and do not require
+access to the offline key.
 
 All other subcommands are intended to be run "offline". However, especially
 when testing, it is of course possible to run the subcommands online as well.

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