[taler-docs] 02/02: use ‘.. code-block:: nginx’ (three 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 97b8feb3e1ffd8839fc3b01015b7684a199bb17b
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Dec 4 04:43:31 2020 -0500

    use ‘.. code-block:: nginx’ (three instances)
---
 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 0ba5e88..8e9ff04 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -939,7 +939,7 @@ Nginx
 
 For Nginx, a possible basic reverse proxy configuration would be:
 
-   ::
+.. code-block:: nginx
 
       proxy_pass http://unix:/some/path/here.sock;
       proxy_redirect off;
@@ -1005,7 +1005,7 @@ Nginx
 For Nginx, you can implement token-based merchant backend authentication as
 follows:
 
-    ::
+.. code-block:: nginx
 
       location ~ /private/ {
           if ($http_authorization !~ "(?i)ApiKey SECURITYTOKEN") {
@@ -1024,7 +1024,7 @@ If you are running different instances on the same 
backend, you
 likely will want to specify different access control tokens for
 each instance:
 
-    ::
+.. code-block:: nginx
 
       location ~ ^/instances/foo/private/ {
           if ($http_authorization !~ "(?i)ApiKey FOOTOKEN") {

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