[taler-docs] branch master updated (6938dc5 -> ef0523e)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from 6938dc5  -improve merchant manual
     new 45b913b  mark up some /etc filenames
     new ef0523e  change markup from " to ``

The 2 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 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index c49a418..86585c7 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -508,10 +508,10 @@ To run the Taler backend on TCP port 8888, use:
 .. note::
 
    When using the Debian/Ubuntu packages, these options are already
-   configured in the /etc/taler/conf.d/merchant.conf configuration file.
+   configured in the ``/etc/taler/conf.d/merchant.conf`` configuration file.
 
-   If you need to change them, you should edit /etc/taler/override.conf,
-   for example by passing "-c /etc/taler/override.conf" to the
+   If you need to change them, you should edit ``/etc/taler/override.conf``,
+   for example by passing ``-c /etc/taler/override.conf`` to the
    ``taler-config`` commands above.
 
 
@@ -537,7 +537,7 @@ https://exchange.demo.taler.net/:
 
    When using the Debian/Ubuntu packages, these options should be
    configured in the ``/etc/taler/taler.conf`` configuration file
-   (alternatively, you can also edit /etc/taler/overrides.conf).
+   (alternatively, you can also edit ``/etc/taler/overrides.conf``).
    However, you must edit the ``taler.conf`` file manually and must
    not use ``taler-config`` to do this, as that would inline the include
    directives and destroy the carefully setup path structure.

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