[taler-docs] branch master updated (113d37b -> b8d9f57)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from 113d37b  mark up ‘CONFIG’, ‘[auditordb-BACKEND]’
     new f253df6  fix typo: s/respectivy/respective/
     new 7fece3a  fix typo: s/exchange's/exchanges/
     new fc55bb3  add comment: one question
     new d567f5d  add colon between term and its description (four instances)
     new b8d9f57  mark up ‘INSERT’, ‘CREATE’, ‘DELETE’, ‘DROP’, ‘UPDATE’

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

diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 4a87500..ffd40a5 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -364,7 +364,7 @@ Deployment
 
 Before GNU Taler wallets will happily interact with an exchange,
 the respective auditor's public key (to be obtained via ``gnunet-ecc``)
-must be added under the respectivy currency to the wallet.  This
+must be added under the respective currency to the wallet.  This
 is usually expected to be hard-coded into the Taler wallet.
 
 Users can also manually add auditors for a particular currency via a
@@ -379,7 +379,7 @@ Exchange
 --------
 
 The next step is to add the exchange's master public key and the base
-URL of the exchange to the list of exchange's audited by the auditor.
+URL of the exchange to the list of exchanges audited by the auditor.
 This is done using the ``taler-auditor-exchange`` tool.  The tool
 basically creates the respective record in the auditor's database.
 
@@ -409,20 +409,22 @@ receive the blob to sign (Website, manual delivery, ...). 
 Note that the
 blob does not contain confidential data, but signing the wrong keys would
 be fatal.  Given the blob, the auditor would sign it using:
 
+.. What does "fatal" mean precisely -- audit fail, system fail?  --ttn
+
 .. code-block:: console
 
    $ taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o 
OUTPUT_FILE
 
 Those arguments are all mandatory.
 
--  ``EXCHANGE_MASTER_PUB`` the base32 Crockford-encoded exchange’s
+-  ``EXCHANGE_MASTER_PUB``: the base32 Crockford-encoded exchange’s
    master public key.
 
--  ``BLOB`` the blob generated by the ``taler-exchange-keyup`` tool.
+-  ``BLOB``: the blob generated by the ``taler-exchange-keyup`` tool.
 
--  ``AUDITOR_URL`` the URL that identifies the auditor.
+-  ``AUDITOR_URL``: the URL that identifies the auditor.
 
--  ``OUTPUT_FILE`` where on the disk the signed blob is to be saved.
+-  ``OUTPUT_FILE``: where on the disk the signed blob is to be saved.
 
 ``OUTPUT_FILE`` must then be provided to the exchange and there copied into
 the directory specified by the option ``AUDITOR_BASE_DIR`` under the section
@@ -445,7 +447,8 @@ used to setup the schema.  For replication of the actual 
SQL data, we refer to
 the Postgres manual.  We note that asynchronous replication should suffice.
 
 Note that during replication, the only statements that may be performed
-are INSERTS.  CREATE/DELETE/DROP/UPDATE are generally not allowed.  A
+are ``INSERT``\ s.  ``CREATE`` / ``DELETE`` / ``DROP`` / ``UPDATE``
+are generally not allowed.  A
 special exception applies when an exchange runs garbage collection on
 old data that is no longer relevant from a regulatory point of view.
 

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