summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-12-12 01:10:11 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-12-12 01:10:11 -0500
commit7d385ee4f12a10a86db9eb18cd6c086b833b349f (patch)
tree592bbe8ee0bf2614323913599687ba8e572e96d4
parent8049c53715a7979b22a345786ac15218cac0d27a (diff)
downloaddocs-7d385ee4f12a10a86db9eb18cd6c086b833b349f.tar.gz
docs-7d385ee4f12a10a86db9eb18cd6c086b833b349f.tar.bz2
docs-7d385ee4f12a10a86db9eb18cd6c086b833b349f.zip
diction: s/evolves around/concerns/
-rw-r--r--taler-auditor-manual.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 5786a829..581700cb 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