[taler-docs] branch master updated (d0858fc -> 5c6f937)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from d0858fc  add link to ‘Revocations’ in Exchange manual
     new b8210fa  mark up ‘[auditor]’
     new 5c6f937  mark up ‘[auditor]’ (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-auditor-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 7d9e993..4ff022b 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -223,7 +223,7 @@ offline key, it is only used for a few cryptographic 
signatures and
 thus the respective code can be run on modest hardware, like a
 Raspberry Pi.
 
-The following values are to be configured in the section [auditor]:
+The following values are to be configured in the section ``[auditor]``:
 
 -  ``AUDITOR_PRIV_FILE``: Path to the auditor’s private key file.
 
@@ -238,7 +238,7 @@ Serving
 
 The auditor can serve HTTP over both TCP and UNIX domain socket.
 
-The following values are to be configured in the section [auditor]:
+The following values are to be configured in the section ``[auditor]``:
 
 -  ``serve``: must be set to ``tcp`` to serve HTTP over TCP, or ``unix`` to 
serve
    HTTP over a UNIX domain socket
@@ -266,7 +266,7 @@ documentation for details.
 Database
 --------
 
-The option ``DB`` under section [auditor] gets the DB backend’s name the
+The option ``DB`` under section ``[auditor]`` gets the DB backend’s name the
 exchange is going to use. So far, only ``DB = postgres`` is supported. After
 choosing the backend, it is mandatory to supply the connection string
 (namely, the database name). This is possible in two ways:

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