aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorLinus Nordberg <linus@nordberg.se>2021-09-23 14:25:23 +0200
committerLinus Nordberg <linus@nordberg.se>2021-09-23 14:25:23 +0200
commit9c032019554136c6808e595f64e6fceb77927c03 (patch)
tree1c1c7f3670b06be6ff01ba170f2b3f8dd5c907e5 /README.md
parent44b530a8ccb3ff6f05c1b4b4ca450f8c60d329c8 (diff)
un-bullet the list of claims
Diffstat (limited to 'README.md')
-rw-r--r--README.md9
1 files changed, 4 insertions, 5 deletions
diff --git a/README.md b/README.md
index 9dc2482..0dd4ad0 100644
--- a/README.md
+++ b/README.md
@@ -9,11 +9,10 @@ _certificates_ keeps the overall design simple and generally useful.
A minimal statement encodes the following claim: the right data has a
certain cryptographic hash. You can add additional meaning to each
-statement. For example, you may use a sigsum log to claim that
-
-- everyone gets the same news articles,
-- software package X builds reproducibly, or
-- a list of key-value pairs is maintained with policy Y.
+statement. For example, you may use a sigsum log to claim things like
+i) everyone get the same news articles, ii) software package X builds
+reproducibly, or iii) a list of key-value pairs are maintained with
+policy Y.
Sigsum logging makes it reasonable to believe your claims by adding enough
discoverability to verify them.