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

4 files changed, 15 insertions, 15 deletions

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 8faadb6a..432e2d1e 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -320,7 +320,7 @@ choosing the backend, it is mandatory to supply the connection string
 -  via configuration option CONFIG, under section [auditordb-BACKEND].
    For example, the demo exchange is configured as follows:
 
-::
+.. code-block:: ini
 
    [auditor]
    ...
diff --git a/taler-backoffice-manual.rst b/taler-backoffice-manual.rst
index d9c57f2c..3042845d 100644
--- a/taler-backoffice-manual.rst
+++ b/taler-backoffice-manual.rst
@@ -63,7 +63,7 @@ read:
 https://docs.taler.net/exchange/html/taler-exchange.html#Configuration-format),
 a working configuration example is the following one:
 
-::
+.. code-block:: ini
 
    [taler]
    # will be EUR, USD, or whatever currency the merchant
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 7e132d79..4d19709e 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -311,7 +311,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
@@ -330,7 +330,7 @@ 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
@@ -496,7 +496,7 @@ starting with “exchange-account-” for the section name. You can ENABLE for
 each account whether it should be used, and for what (incoming or outgoing
 wire transfers):
 
-::
+.. code-block:: ini
 
    [exchange-account-1]
    # With x-taler-bank (say for PyBank)
@@ -554,7 +554,7 @@ apply whenever the exchange closes a reserve (sending back funds to the
 customer). The fees must be constant for a full year, which is specified
 as part of the name of the option.
 
-::
+.. code-block:: ini
 
    [fees-iban]
    WIRE-FEE-2018 = EUR:0.01
@@ -583,7 +583,7 @@ choosing the backend, it is mandatory to supply the connection string
 -  via configuration option CONFIG, under section [exchangedb-BACKEND].
    For example, the demo exchange is configured as follows:
 
-::
+.. code-block:: ini
 
    [exchange]
    ...
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