[or-cvs] [tor/maint-0.2.2] Update the spec with the new bounds

[arma@xxxxxxxxxxxxxx]

commit a1860cc3f1d6224f3be40319a075471cb491e1aa
Author: Sebastian Hahn <sebastian@xxxxxxxxxxxxxx>
Date:   Sat Jan 15 19:49:39 2011 +0100

    Update the spec with the new bounds
---
 doc/spec/dir-spec.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt
index 4ba2ee3..eebceea 100644
--- a/doc/spec/dir-spec.txt
+++ b/doc/spec/dir-spec.txt
@@ -1161,14 +1161,14 @@
         research indicates that a lower value would mean fewer cells in
         transit in the network at any given time. Obeyed by Tor 0.2.1.20
         and later.
-        Min: 1, Max: 100000 XXX are these sane
+        Min: 100, Max: 1000
 
         "CircuitPriorityHalflifeMsec" -- the halflife parameter used when
         weighting which circuit will send the next cell. Obeyed by Tor
         0.2.2.10-alpha and later.  (Versions of Tor between 0.2.2.7-alpha
         and 0.2.2.10-alpha recognized a "CircPriorityHalflifeMsec" parameter,
         but mishandled it badly.)
-        Min: -1, Max: 2147483647 (INT32_MAX) XXX are these sane?
+        Min: -1, Max: 2147483647 (INT32_MAX)
 
         "perconnbwrate" and "perconnbwburst" -- if set, each relay sets
         up a separate token bucket for every client OR connection,