From b92650370783a5b9e67c463531963ac2a8cd97e0 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Sat, 12 Dec 2020 00:05:24 -0500 Subject: add blank lines between "term" and describing paras (three instances) --- taler-auditor-manual.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 0efb2dbd..583a7496 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -118,8 +118,8 @@ third parties to verify one's own work. The Taler software stack for an auditor consists of the following components: -- DBMS - Postgres +- DBMS: Postgres + The auditor requires a DBMS to stores a local copy of the transaction history for the Taler exchange, as well as for its own internal bookkeeping and checkpointing. The DBMS is assumed to be assure the auditor of the database invariants (foreign @@ -132,6 +132,7 @@ components: support another DBMS. - The auditor Web service + The auditor is expected to provide a public Web service. At this REST API, merchants can (probabilistically) provide deposit confirmations, allowing the auditor to detect if an exchange is underreporting deposits. @@ -145,6 +146,7 @@ components: The main binary of this component is the ``taler-auditor-httpd``. - The (main) auditor + The main auditor logic checks the various signatures, totals up the amounts and checks for arithmetic inconsistencies. It also computes the expected bank balance, revenue and risk exposure of the -- cgit v1.2.3