[taler-docs] branch master updated (dea5cef -> fe85289)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from dea5cef  mark up ‘$’ (two instances)
     new 8821c4a  mark up ‘taler-merchant-benchmark’
     new 6c4d1cc  fix typo: add closing paren
     new fe85289  fix typo: "work" -> "word"

The 3 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 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 4ccde0c..7182945 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -1501,14 +1501,14 @@ start.
 Benchmark setup
 ---------------
 
-The taler-merchant-benchmark tool will automatically launch and configure the
+The ``taler-merchant-benchmark`` tool will automatically launch and configure 
the
 exchange, (Python) bank and other tools required for the benchmark. However,
 the configuration file must be provided and have consistent options set.  The
 options that require special care include the exchange's public key (which
 must match the private key in the file specified by the configuration), the
 currency (which must be consistent across the file), the denomination
 structure (which must enable payments in the range of 100ths of the unit
-currency (often called cents). Furthermore, the benchmark will set the
+currency (often called cents)). Furthermore, the benchmark will set the
 Exchange bank account password to be "x", so the configuration must also
 specify "x" for the passphrase.  Finally, the bank must be configured to allow
 for substantial debt least the transactions by the benchmark run out of
@@ -1585,7 +1585,7 @@ options:
    ``/track/transaction`` and ``/track/transfer``. This command should
    only be used to see if the operation ends without problems, as no
    actual measurement of performance is provided (despite of the
-   ’benchmark’ work used in the tool’s name).
+   ’benchmark’ word used in the tool’s name).
 
 
 

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