use ‘.. code-block:: ini’ (14 instances)

1 files changed, 8 insertions, 8 deletions

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index bf69c499..aecc56a5 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -527,7 +527,7 @@ Service address
 The following option sets the transport layer address used by the
 merchant backend:
 
-   ::
+.. code-block:: ini
 
       [MERCHANT]/SERVE = TCP | UNIX
 
@@ -560,7 +560,7 @@ Currency
 Which currency the Web shop deals in, i.e. “EUR” or “USD”, is
 specified using the option
 
-   ::
+.. code-block:: ini
 
       [TALER]/CURRENCY
 
@@ -579,7 +579,7 @@ Database
 In principle is possible for the backend to support different DBMSs.
 The option
 
-   ::
+.. code-block:: ini
 
       [MERCHANT]/DB
 
@@ -591,7 +591,7 @@ DBMS-specific options to access the database.
 
 For postgres, you need to provide:
 
-   ::
+.. code-block:: ini
 
       [MERCHANTDB-postgres]/CONFIG
 
@@ -734,7 +734,7 @@ Sample backend configuration
 
 The following is an example for a complete backend configuration:
 
-  ::
+.. code-block:: ini
 
    [TALER]
    CURRENCY = KUDOS
@@ -1347,7 +1347,7 @@ it under ``$HOME/.config/``.
 A config file is a text file containing sections, and each section
 contains its values. The right format follows:
 
-::
+.. code-block:: ini
 
    [section1]
    value1 = string
@@ -1366,11 +1366,11 @@ variables that are unset, by using the following syntax:
 
 by defining them under a ``[paths]`` section, see example below,
 
-::
+.. code-block:: ini
 
    [paths]
    TALER_DEPLOYMENT_SHARED = ${HOME}/shared-data
-   ..
+   ...
    [section-x]
    path-x = ${TALER_DEPLOYMENT_SHARED}/x