[taler-docs] branch master updated (f34f4a4 -> 8da3a55)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from f34f4a4  fix typo: add blank line after ‘::’
     new 784e31d  mark up ‘example.com’
     new 8da3a55  mark up ‘/private/’ (two instances)

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 taler-merchant-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 10bd133..d03c9aa 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -983,7 +983,7 @@ endpoint):
        RequestHeader add "X-Forwarded-Proto" "https"
        </Location>
 
-Note that the above again assumes your domain name is /example.com/ and that
+Note that the above again assumes your domain name is ``example.com`` and that
 you have TLS configured.  Note that you must add the "https" header unless
 your site is not available via TLS.
 
@@ -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.