[taler-docs] 02/02: mark up ‘/private/’ (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 8da3a557fea47475b6670baec864e9c14f5345f0
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sun Nov 22 05:44:48 2020 -0500

    mark up ‘/private/’ (two instances)
---
 taler-merchant-manual.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 1ab0c91..d03c9aa 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -994,7 +994,7 @@ setup access control!
 Access control
 --------------
 
-All endpoints with /private/ in the URL must be restricted to authorized users
+All endpoints with ``/private/`` in the URL must be restricted to authorized 
users
 of the respective instance.  Specifically, the HTTP server must be configured
 to only allow access to ``$BASE_URL/private/`` to the authorized users of the
 default instance, and to ``$BASE_URL/instances/$ID/private/`` to the
@@ -1004,7 +1004,7 @@ How access control is done (TLS client authentication, 
HTTP basic or digest
 authentication, etc.) is completely up to the merchant and does not matter to
 the Taler merchant backend.
 
-Note that all of the other endpoints (without /private/) are expected to be
+Note that all of the other endpoints (without ``/private/``) are expected to be
 fully exposed to the Internet, and wallets may have to interact with those
 endpoints directly without client authentication.
 

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