summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--design-documents/011-auditor-db-sync.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/design-documents/011-auditor-db-sync.rst b/design-documents/011-auditor-db-sync.rst
index 505f7b49..f4befdfa 100644
--- a/design-documents/011-auditor-db-sync.rst
+++ b/design-documents/011-auditor-db-sync.rst
@@ -131,7 +131,7 @@ Drawbacks
is the answer, to be investigated what performs better.
* A malicious exchange could theoretically send expensive transactions
to the auditor via the replication mechanism (possibly ones that
- it did not even execute locally itself) to DoS the "ingres"
+ it did not even execute locally itself) to DoS the "ingress"
database. This would be noticed primarily by load
monitoring or even the auditor lagging unusually far behind the
exchange's transaction history. We believe this is acceptable,