[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 03/05: mark up file names (four instances)
From: |
gnunet |
Subject: |
[taler-docs] 03/05: mark up file names (four instances) |
Date: |
Sun, 22 Nov 2020 12:12:48 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
commit 9847f5cc047d9817dedb48e9a591ac04d11ecafd
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sun Nov 22 06:08:29 2020 -0500
mark up file names (four instances)
---
taler-merchant-manual.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 7172c1c..7ed1a7c 100644
--- 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:
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.