[tor-commits] [torspec/master] Try to clean up sr/{current, previous} a little

[nickm@xxxxxxxxxxxxxx]

commit 6602c67e7dd91a08c3e710060ab20410a0cc5a2f
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Wed Jan 11 14:37:48 2017 -0500

    Try to clean up sr/{current,previous} a little
---
 control-spec.txt | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/control-spec.txt b/control-spec.txt
index 025e28d..24b2e92 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -998,11 +998,9 @@
 
     "sr/current"
     "sr/previous"
-      Get either the current or previous shared random value from the
-      consensus. The values are as seen in the consensus that is base64
-      encoded. An empty value means that it couldn't be found and thus is
-      non-existent in the current consensus the tor daemon has or tor doesn't
-      have a usable consensus.
+      The current or previous shared random value, as received in the
+      consensus, base-64 encoded.  An empty value means that the consensus
+      either has no shared random value, or that Tor has no consensus.
 
   Examples:
      C: GETINFO version desc/name/moria1

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits