[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] [tor/master 03/10] Note that we only can't handle automatic demotion. Users can always change their state manually.
Author: Steven Murdoch <Steven.Murdoch@xxxxxxxxxxxx>
Date: Mon, 15 Mar 2010 00:23:12 +0000
Subject: Note that we only can't handle automatic demotion. Users can always change their state manually.
Commit: 60d416a564deafaef0efcd60c7923a6308718550
---
.../ideas/xxx-automatic-node-promotion.txt | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
index d96861d..692bc7e 100644
--- a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
+++ b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
@@ -60,11 +60,11 @@ Target:
Auto-bridge -> relay: Tor has detected that it is sufficiently
reliable to be a *relay*
- Note that this model does not support demotion. If this is
- desirable, there should be some memory as to whether the previous
- state was relay, bridge, or auto-bridge. Otherwise the user may be
- prompted to become a relay, although he has opted to only be a
- bridge.
+ Note that this model does not support automatic demotion. If this
+ is desirable, there should be some memory as to whether the
+ previous state was relay, bridge, or auto-bridge. Otherwise the
+ user may be prompted to become a relay, although he has opted to
+ only be a bridge.
3.x User interaction policy
--
1.7.1