gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] 85/119: change markup for ‘refresh_base_url’ from " to `` (


From: gnunet
Subject: [taler-docs] 85/119: change markup for ‘refresh_base_url’ from " to `` (two instances)
Date: Fri, 19 Mar 2021 08:12:55 +0100

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

ttn pushed a commit to branch master
in repository docs.

commit c2f0105b838bad56ba2d54c18537d793e56dd278
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Mar 19 02:44:40 2021 -0400

    change markup for ‘refresh_base_url’ from " to `` (two instances)
---
 core/api-exchange.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index 52f9dcb..4e69ba3 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -1493,10 +1493,10 @@ the API during normal operation.
   appeared *explicitly* in the protocol before).
 
   The base URL for ``/refreshes/``-requests may differ from the main base URL 
of
-  the exchange. Clients SHOULD respect the "refresh_base_url" returned for the
+  the exchange. Clients SHOULD respect the ``refresh_base_url`` returned for 
the
   coin during melt operations. The exchange MUST return a
   307 or 308 redirection to the correct base URL if the client failed to
-  respect the "refresh_base_url" or if the allocation has changed.
+  respect the ``refresh_base_url`` or if the allocation has changed.
 
   Errors such as failing to do proper arithmetic when it comes to calculating
   the total of the coin values and fees are simply reported as bad requests.

-- 
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]