[taler-docs] branch master updated (6002a59 -> 2d0cbb2)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from 6002a59  mark up ‘test-auditor.sh’
     new 8d7d957  mark up ‘taler-wallet-cli’
     new 2d0cbb2  mark up ‘test-auditor.sh’ (two instances)

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-auditor-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index ebae20f..34c2143 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -878,19 +878,19 @@ Testing the auditor
 The main objective of the auditor is to detect inconsistencies. Thus, the
 ``test-auditor.sh`` script deliberately introduces various inconsistencies into
 a synthetic exchange database.  For this, an "normal" exchange database is
-first generated using the taler-wallet-cli.  Then, various fields or rows
+first generated using the ``taler-wallet-cli``.  Then, various fields or rows
 of that database are manipulated, and the auditor is let loose on the modified
 database.  Afterwards, the test verifies that the JSON contains values
 indicating that the auditor found the inconsistencies.  The script also
 verifies that template expansion and LaTeX run work for the JSON output,
 but it does not verify the correctness of the final PDF.
 
-The test-auditor.sh script is written to maximize code coverage: it should
+The ``test-auditor.sh`` script is written to maximize code coverage: it should
 cover as many code paths as possible in both the exchange and the auditor.  It
 should also ideally create all interesting possible variations of the exchange
 database fields (within the constraints of the database schema).
 
-In general, test-auditor.sh runs the tests against an "old" database where
+In general, ``test-auditor.sh`` runs the tests against an "old" database where
 some transactions are past the due-date (and hence the aggregator would trigger
 wire transfers), as well as a freshly generated exchange database where the
 auditor would not perform any transfers.  Auditor interactions can be made

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