commit 9847f5cc047d9817dedb48e9a591ac04d11ecafd
parent 5342026d448d6bb36ecc4e33fb5ea260456c76a3
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date: Sun, 22 Nov 2020 06:08:29 -0500
mark up file names (four instances)
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -1348,10 +1348,10 @@ Configuration format
In Taler realm, any component obeys to the same pattern to get
configuration values. According to this pattern, once the component has
been installed, the installation deploys default values in
-${prefix}/share/taler/config.d/, in .conf files. In order to override
+``${prefix}/share/taler/config.d/``, in ``.conf`` files. In order to override
these defaults, the user can write a custom .conf file and either pass
-it to the component at execution time, or name it taler.conf and place
-it under $HOME/.config/.
+it to the component at execution time, or name it ``taler.conf`` and place
+it under ``$HOME/.config/``.
A config file is a text file containing sections, and each section
contains its values. The right format follows:
