diff options
| author | Linus Nordberg <linus@nordberg.se> | 2021-09-07 16:50:07 +0200 |
|---|---|---|
| committer | Rasmus Dahlberg <rasmus.dahlberg@kau.se> | 2021-10-02 00:54:13 +0200 |
| commit | 93e1adb39c2c99f56ea34a151f7accecfca122e0 (patch) | |
| tree | 6e99201ccaba3399b6a90b9990c29844bf0996b2 | |
| parent | 921753c82e2f2492325dca768fceb0b516be3457 (diff) | |
minor wording changes
- more than two perspectives
- avoid "deployment" to refer to "log operations"
- don't say "idiot"
| -rw-r--r-- | doc/design.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/design.md b/doc/design.md index e34b1fe..d2a6a62 100644 --- a/doc/design.md +++ b/doc/design.md @@ -43,9 +43,9 @@ think of this as some sort of bottom-line for what it takes to apply a transparent logging pattern. Past use-cases that wanted to piggy-back on an existing reliable log ecosystem fit well into our scope [\[BinTrans\]](https://wiki.mozilla.org/Security/Binary_Transparency). -We also want the design to be easy from the perspective of log operations and -deployment in constrained environments. This includes considerations such as -idiot-proof parsing, protection against log spam and poisoning, and a +We also want the design to be easy from many different perspectives, for example log operations and +verification in constrained environments. This includes considerations such as +simple parsing, protection against log spam and poisoning, and a well-defined gossip protocol without any complex auditing logic. ### 1.2 - Abstract setting |