[taler-docs] 71/119: mark up ‘/refresh/link’ (two instances)

[gnunet]

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

ttn pushed a commit to branch master
in repository docs.

commit 540e123ea3e8c81594d7caff7a5a9d9a0d013f6b
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Mar 19 02:33:26 2021 -0400

    mark up ‘/refresh/link’ (two instances)
---
 core/api-exchange.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index 676a098..9d71145 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -1358,7 +1358,7 @@ transactions with the freshly exchangeed coins unlinkabe 
to previous transaction
 by anyone except the wallet itself.
 
 However, the new coins are linkable from the private keys of all old coins
-using the /refresh/link request.  While /refresh/link must be implemented by
+using the ``/refresh/link`` request.  While ``/refresh/link`` must be 
implemented by
 the exchange to achieve taxability, wallets do not really ever need that part 
of
 the API during normal operation.
 

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