[taler-docs] branch master updated: format ‘console’ code blocks (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.

The following commit(s) were added to refs/heads/master by this push:
     new dbb025d  format ‘console’ code blocks (two instances)
dbb025d is described below

commit dbb025d34ab099db1493a4abbb79a799863e28e5
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Dec 18 03:01:03 2020 -0500

    format ‘console’ code blocks (two instances)
---
 manpages/taler-auditor-offline.1.rst | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/manpages/taler-auditor-offline.1.rst 
b/manpages/taler-auditor-offline.1.rst
index 3c17ab1..dab2f53 100644
--- a/manpages/taler-auditor-offline.1.rst
+++ b/manpages/taler-auditor-offline.1.rst
@@ -78,16 +78,20 @@ The exchange and the **taler-auditor-httpd** must both be 
provided with
 the auditor's public key, such that they can validate messages signed
 by the auditor. To obtain the auditor's public key, use:
 
-$ AUDITOR_PRIV_FILE=`taler-config -f -c $CONF -s AUDITOR -o AUDITOR_PRIV_FILE`
-$ gnunet-ecc -p $AUDITOR_PRIV_FILE
+.. code-block:: console
+
+   $ AUDITOR_PRIV_FILE=`taler-config -f -c $CONF -s AUDITOR -o 
AUDITOR_PRIV_FILE`
+   $ gnunet-ecc -p $AUDITOR_PRIV_FILE
 
 Note that if the private key file does not yet exist, the above will fail.
 In this case, create the private key using:
 
-$ AUDITOR_PRIV_FILE=`taler-config -f -c $CONF -s AUDITOR -o AUDITOR_PRIV_FILE`
-$ AUDITOR_PRIV_DIR=`dirname $AUDITOR_PRIV_FILE`
-$ mkdir -p $AUDITOR_PRIV_DIR
-$ gnunet-ecc -g1 $AUDITOR_PRIV_FILE
+.. code-block:: console
+
+   $ AUDITOR_PRIV_FILE=`taler-config -f -c $CONF -s AUDITOR -o 
AUDITOR_PRIV_FILE`
+   $ AUDITOR_PRIV_DIR=`dirname $AUDITOR_PRIV_FILE`
+   $ mkdir -p $AUDITOR_PRIV_DIR
+   $ gnunet-ecc -g1 $AUDITOR_PRIV_FILE
 
 
 Relevant configuration options for **taler-auditor-offline** are:

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