[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: diction: s/evolves around/concerns/
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: diction: s/evolves around/concerns/ |
Date: |
Sat, 12 Dec 2020 07:11:44 +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 7d385ee diction: s/evolves around/concerns/
7d385ee is described below
commit 7d385ee4f12a10a86db9eb18cd6c086b833b349f
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Dec 12 01:10:11 2020 -0500
diction: s/evolves around/concerns/
---
taler-auditor-manual.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 5786a82..581700c 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -589,8 +589,8 @@ Failures
Most audit failures are handled by the auditor's regular reporting
functionality,
creating a (hopefully descriptive) PDF report detailing the problems found.
-However, there is one category of errors where this is not possible, which
evolves
-around arithmetic overflows for amounts. Taler's specification limits amount
+However, there is one category of errors where this is not possible, which
+concerns arithmetic overflows for amounts. Taler's specification limits amount
values to at most 2^52. If, during the auditor's calculations, amounts are
encountered that exceed this threshold, the auditor will not generate a regular
report, but instead write a log statement explaining where the problem happened
--
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/evolves around/concerns/,
gnunet <=