packaging simplification, TODO cleanup.

[monkeysphere.git] / website / trust-models.mdwn

diff --git a/website/trust-models.mdwn b/website/trust-models.mdwn
index c8dd93615a34537167a007a995698c4a245622bb..8fee5cbe9f7a0d2eb153574c1384d329445f3e2f 100644 (file)
--- a/website/trust-models.mdwn
+++ b/website/trust-models.mdwn
@@ -62,9 +62,9 @@ validity*:
 
  *  Given that:
 
-        * the key itself is valid, in the first narrow sense used above, and
-        * given the UserID's set of cryptographically-correct certifications, and
-        * given your personal subjective declarations about who you trust to make certifications (and *how much* you trust them to do this), 
+    * the key itself is valid, in the first narrow sense used above, and
+    * given the UserID's set of cryptographically-correct certifications, and
+    * given your personal subjective declarations about who you trust to make certifications (and *how much* you trust them to do this), 
 
     is this User ID bound to its key with an acceptable trust path?
 
@@ -85,7 +85,7 @@ These colon-delimited records say (in order):
  * `1`: uses new "PGP" trust model (0 would be the "Classic trust model") -- see below
  * `1220401097`: seconds since the epoch that I created the trust db.
  * `1220465006`: seconds after the epoch that the trustdb will need to be rechecked (usually due to the closest pending expiration, etc)
- * `3`: Either 3 certifications from keys with marginal ownertrust are needed for full User ID+Key validity
+ * `3`: Either 3 certifications from keys with marginal ownertrust ...
  * `1`: Or 1 certification from a key with full ownertrust is needed for full User ID+Key validity
  * `5`: `max_cert_depth` (i'm not sure exactly how this is used, though the name is certainly suggestive)