[taler-docs] branch master updated (fd7b0ff -> 50c869c)

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a change to branch master
in repository docs.

    from fd7b0ff  mark up ‘taler-merchant-httpd’
     new 1c98800  mark up ‘taler-merchant-dbinit’
     new 5342026  mark up ‘taler-merchant-dbinit’
     new 9847f5c  mark up file names (four instances)
     new 1e3b924  mark up file name
     new 50c869c  fix typo: pluralize ‘component’

The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 taler-merchant-manual.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 0dd1e16..530171f 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -1327,11 +1327,11 @@ Advanced topics
 Database Scheme
 ---------------
 
-The merchant database must be initialized using /taler-merchant-dbinit/.
+The merchant database must be initialized using ``taler-merchant-dbinit``.
 This tool creates the tables required by the Taler merchant to operate.
 The tool also allows you to reset the Taler merchant database, which is
 useful for test cases but should never be used in production. Finally,
-taler-merchant-dbinit has a function to garbage collect a database,
+``taler-merchant-dbinit`` has a function to garbage collect a database,
 allowing administrators to purge records that are no longer required.
 
 The database scheme used by the merchant looks as follows:
@@ -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:
@@ -1394,13 +1394,13 @@ The configuration loader will give precedence to 
variables set under
 
 The utility ``taler-config``, which gets installed along with the
 exchange, serves to get and set configuration values without directly
-editing the .conf. The option ``-f`` is particularly useful to resolve
+editing the ``.conf``. The option ``-f`` is particularly useful to resolve
 pathnames, when they use several levels of ``$``-expanded variables. See
 ``taler-config --help``.
 
 Note that, in this stage of development, the file
 ``$HOME/.config/taler.conf`` can contain sections for *all* the
-component. For example, both an exchange and a bank can read values from
+components. For example, both an exchange and a bank can read values from
 it.
 
 The `deployment repository <https://git.taler.net/deployment>`_ contains 
examples of

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.