taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 7d385ee4f12a10a86db9eb18cd6c086b833b349f
parent 8049c53715a7979b22a345786ac15218cac0d27a
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Sat, 12 Dec 2020 01:10:11 -0500

diction: s/evolves around/concerns/

Diffstat:
Mtaler-auditor-manual.rst | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 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