[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: diction: s/to be assure/to be able t
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: diction: s/to be assure/to be able to assure/ |
Date: |
Sat, 12 Dec 2020 06:12:31 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 6b654cf diction: s/to be assure/to be able to assure/
6b654cf is described below
commit 6b654cf7dfe2342de85ecd3fe2755f4dac961336
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Dec 12 00:10:58 2020 -0500
diction: s/to be assure/to be able to assure/
---
taler-auditor-manual.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 2d1ea93..6c98bf1 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -122,7 +122,7 @@ components:
The auditor requires a DBMS to store 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
+ The DBMS is assumed to be able to assure the auditor of the database
invariants (foreign
key, uniqueness, length restrictions). Should the exported data from the
exchange
fail to be imported due to constraint violations, this is an immediate
serious
concern that must be addressed manually. The software only verifies the
content
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: diction: s/to be assure/to be able to assure/,
gnunet <=