From 90669a5fb3178025d38258616194f91812b02764 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Mon, 4 Sep 2023 18:59:33 +0200 Subject: various doc fixes --- taler-auditor-manual.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'taler-auditor-manual.rst') diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 6a7b9ea4..feaf7783 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -582,7 +582,7 @@ The next key step for the auditor is to configure replication of the *exchange*'s database in-house. This should be performed in two steps as illustrated in the following figure: -.. image:: replication.png +.. image:: images/replication.png First, the exchange should use standard PostgreSQL replication features to enable the auditor to obtain a full copy of the exchange's database. @@ -968,7 +968,7 @@ The auditor's database The database scheme used by the exchange looks as follows: -.. image:: auditor-db.png +.. image:: images/auditor-db.png Invariants checked by the auditor -- cgit v1.2.3