aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/control-spec.txt18
-rw-r--r--doc/spec/dir-spec.txt8
-rw-r--r--doc/spec/proposals/103-multilevel-keys.txt2
3 files changed, 15 insertions, 13 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index 64596bac9..4886a4ba8 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -362,18 +362,20 @@ $Id$
not necessarily those for a descriptor that Tor currently has.
[First implemented in 0.1.2.3-alpha.]
- "ns/all" -- Network status info for all ORs we have an opinion about,
- joined by newlines. [First implemented in 0.1.2.3-alpha.]
+ "ns/all" -- Network status info (v2 directory style) for all ORs we
+ have an opinion about, joined by newlines. [First implemented
+ in 0.1.2.3-alpha.]
"desc/all-recent" -- the latest server descriptor for every router that
Tor knows about.
- "network-status" -- a space-separated list of all known OR identities.
- This is in the same format as the router-status line in directories;
- see dir-spec-v1.txt section 3 for details. (If VERBOSE_NAMES is
- enabled, the output will not conform to dir-spec-v1.txt; instead, the
- result will be a space-separated list of LongName, each preceded by a
- "!" if it is believed to be not running.)
+ "network-status" -- a space-separated list (v1 directory style)
+ of all known OR identities. This is in the same format as the
+ router-status line in v1 directories; see dir-spec-v1.txt section
+ 3 for details. (If VERBOSE_NAMES is enabled, the output will
+ not conform to dir-spec-v1.txt; instead, the result will be a
+ space-separated list of LongName, each preceded by a "!" if it is
+ believed to be not running.)
"addr-mappings/all"
"addr-mappings/config"
diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt
index 690064641..918176bf7 100644
--- a/doc/spec/dir-spec.txt
+++ b/doc/spec/dir-spec.txt
@@ -109,9 +109,9 @@ $Id$
* The most sensitive data in the entire network (the identity keys
of the directory authorities) needed to be stored unencrypted so
- that the authorities . Now, the authorities' identity keys are
- stored offline, and used to certify medium-term signing keys that
- can be rotated.
+ that the authorities can sign network-status documents on the fly.
+ Now, the authorities' identity keys are stored offline, and used
+ to certify medium-term signing keys that can be rotated.
0.3. Some Remaining questions
@@ -258,7 +258,7 @@ $Id$
"Exactly once": These items MUST occur exactly one time in every
instance of the document type.
- "At start, exactly once": These items MUST occur in every instance of
+ "At end, exactly once": These items MUST occur in every instance of
the document type, and MUST appear exactly once, and MUST be the
last item in their documents.
diff --git a/doc/spec/proposals/103-multilevel-keys.txt b/doc/spec/proposals/103-multilevel-keys.txt
index ce4da1fee..859e45661 100644
--- a/doc/spec/proposals/103-multilevel-keys.txt
+++ b/doc/spec/proposals/103-multilevel-keys.txt
@@ -175,7 +175,7 @@ Extensions to Proposal 101.
for that voter.
A key certificate is invalid if any of the following hold:
- * The version is unrecognized
+ * The version is unrecognized.
* The fingerprint does not match the identity key.
* The identity key or the signing key is ill-formed.
* The published date is very far in the past or future.