-fix notes

1 files changed, 6 insertions, 7 deletions

diff --git a/frags/configuration-format.rst b/frags/configuration-format.rst
index 489e98cb..5a74c775 100644
--- a/frags/configuration-format.rst
+++ b/frags/configuration-format.rst
@@ -11,7 +11,7 @@ In order to override these defaults, the user can write a custom configuration
 file and either pass it to the component at execution time using the *-c*
 option, or name it taler.conf and place it under $HOME/.config/ which is where
 components will look by default. Note that the systemd service files pass ``-c
-/etc/taler/taler.conf``, thus making ``/etc/taler/taler.conf`` 
+/etc/taler/taler.conf``, thus making ``/etc/taler/taler.conf``
 the primary location for the configuration.
 
 A config file is a text file containing sections, and each section
@@ -35,9 +35,9 @@ variables that are unset, by using the following syntax:
 ``${VAR:-default}``. There are two ways a user can set the value
 of ``$``-prefixable variables:
 
-  (1) by defining them under a ``[paths]`` section:
+(1) by defining them under a ``[paths]`` section:
 
-     .. code-block:: ini
+    .. code-block:: ini
 
        [paths]
        TALER_DEPLOYMENT_SHARED = ${HOME}/shared-data
@@ -45,11 +45,11 @@ of ``$``-prefixable variables:
        [section-x]
        path-x = ${TALER_DEPLOYMENT_SHARED}/x
 
-  (2) or by setting them in the environment:
+(2) or by setting them in the environment:
 
-     .. code-block:: console
+    .. code-block:: console
 
-        $ export VAR=/x
+       $ export VAR=/x
 
 The configuration loader will give precedence to variables set under
 ``[path]`` over environment variables.
@@ -62,4 +62,3 @@ pathnames, when they use several levels of ``$``-expanded variables. See
 
 The repository ``git://git.taler.net/deployment`` contains example code
 for generating configuration files under ``deployment/netzbon/``.
-