gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] 79/119: mark up ‘/refreshes/’, ‘/coins/’, ‘refresh_base_url


From: gnunet
Subject: [taler-docs] 79/119: mark up ‘/refreshes/’, ‘/coins/’, ‘refresh_base_url’
Date: Fri, 19 Mar 2021 08:12:49 +0100

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

ttn pushed a commit to branch master
in repository docs.

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

    mark up ‘/refreshes/’, ‘/coins/’, ‘refresh_base_url’
---
 core/api-exchange.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index ed39fda..8740c6b 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -1440,8 +1440,8 @@ the API during normal operation.
       // Base URL to use for operations on the refresh context
       // (so the reveal operation).  If not given,
       // the base URL is the same as the one used for this request.
-      // Can be used if the base URL for /refreshes/ differs from that
-      // for /coins/, i.e. for load balancing.  Clients SHOULD
+      // Can be used if the base URL for ``/refreshes/`` differs from that
+      // for ``/coins/``, i.e. for load balancing.  Clients SHOULD
       // respect the refresh_base_url if provided.  Any HTTP server
       // belonging to an exchange MUST generate a 307 or 308 redirection
       // to the correct base URL should a client uses the wrong base
@@ -1449,7 +1449,7 @@ the API during normal operation.
       //
       // When melting the same coin twice (technically allowed
       // as the response might have been lost on the network),
-      // the exchange may return different values for the refresh_base_url.
+      // the exchange may return different values for the ``refresh_base_url``.
       refresh_base_url?: string;
 
     }

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