aboutsummaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-07 15:34:07 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-07 15:34:07 +0200
commitec29746e786554f7abb3a86c5d76d14ee1aec78c (patch)
treef7ff7bb04ed8b64aa9bd71fd358e2265f6ee350c /issues
parent9288886de0e4477bb6e3dface9266fe0644b3e97 (diff)
fixed s/transparent log/transparency log/g
Diffstat (limited to 'issues')
-rw-r--r--issues/risk-averse-attacker.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/issues/risk-averse-attacker.md b/issues/risk-averse-attacker.md
index 519001b..6829aa3 100644
--- a/issues/risk-averse-attacker.md
+++ b/issues/risk-averse-attacker.md
@@ -2,7 +2,7 @@
reported by: rgdd
We used to have a paragraph in our threat model that emphasized that the
-attacker we, and transparent logs in general, consider is risk-averse.
+attacker we, and transparency logs in general, consider is risk-averse.
This paragraph was pulled because it simply stated properties about our attacker
without explaining why that is interesting. The threat model text is fine