gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: fix 2nd link (#7945)


From: gnunet
Subject: [taler-docs] branch master updated: fix 2nd link (#7945)
Date: Mon, 16 Oct 2023 22:03:42 +0200

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 e32431b9 fix 2nd link (#7945)
e32431b9 is described below

commit e32431b9b3c699d2009ea371d7f8ea394147716b
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Mon Oct 16 22:03:39 2023 +0200

    fix 2nd link (#7945)
---
 taler-merchant-manual.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 6d8c7622..0ad9bb30 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -267,13 +267,13 @@ Transfers
 .. index:: wire transfer
 
 The Taler backend can be used to verify that the exchange correctly wired all
-of the funds to the merchant. However, if no `Taler Bank Merchant HTTP API
-<taler-bank-merchant-http-api>`_ was provided for the respective bank account,
+of the funds to the merchant. However, if no :ref:`Taler Bank Revenue HTTP API
+<taler-bank-merchant-http-api>` was provided for the respective bank account,
 the backend does not have access to the incoming wire transfers of the
-merchant's bank account. In this case, merchants must manually provide the
+merchant's bank account. In this case, merchants should manually provide the
 backend with wire *transfer* data that specifies the *wire transfer subject*
 and the amount that was received. Given this information, the backend can
-detect and report any irregularities that might arise.
+detect and report any irregularities that might arise.  
 
 Rewards
 -------

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]