[or-cvs] typos and tabs

Roger Dingledine arma at seul.org
Fri Sep 10 18:56:55 UTC 2004


Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/doc

Modified Files:
	TODO tor.1.in 
Log Message:
typos and tabs


Index: TODO
===================================================================
RCS file: /home/or/cvsroot/doc/TODO,v
retrieving revision 1.158
retrieving revision 1.159
diff -u -d -r1.158 -r1.159
--- TODO	8 Sep 2004 06:52:33 -0000	1.158
+++ TODO	10 Sep 2004 18:56:51 -0000	1.159
@@ -13,7 +13,7 @@
 
       0.0.9:
         o Fix OutboundBindAddress
-        o Config defaults should be consistant with config file and no
+        o Config defaults should be consistent with config file and no
           config file.
         o write instructions for port-forwarding directives or programs
           to let people run on ports 80 and 443 without needing to bind
@@ -21,24 +21,24 @@
         o clean up all the comma-separated stuff (eg exit policies) into
           smartlists.
         o investigate sctp for alternate transport.
- 	o Document all undocumented options, or mark them as undocumented
-	  in the source.
+        o Document all undocumented options, or mark them as undocumented
+          in the source.
         o bandwidth buckets for write as well as read.
         . Cached-directory changes:
-            o make clients store the cached-directory to disk,
-            o and use it when they startup, so they don't need to bootstrap
-              from the authdirservers every time they start.
-            - also, once we've reduced authdirserver entries to config
-              lines, we can have lines that list cacheddirservers too.
+          o make clients store the cached-directory to disk,
+          o and use it when they startup, so they don't need to bootstrap
+            from the authdirservers every time they start.
+          - also, once we've reduced authdirserver entries to config
+            lines, we can have lines that list cacheddirservers too.
         . compress the directory.
-	    o Implement gzip/zlib wrappers
-	    o Compress directories as they're cached/generated
-	    o When requested, give a compressed directory.
-	    o Decompress incoming HTTP based on Content-Encoding
-	    - Once dirservers are running new code, make clients
-	      request compressed directories.  (Alternative: Switch
-	      to HTTP/1.1 and use Allowed-Encoding.  Is that really
-	      what we want?)
+          o Implement gzip/zlib wrappers
+          o Compress directories as they're cached/generated
+            o When requested, give a compressed directory.
+            o Decompress incoming HTTP based on Content-Encoding
+            - Once dirservers are running new code, make clients
+              request compressed directories.  (Alternative: Switch
+              to HTTP/1.1 and use Allowed-Encoding.  Is that really
+              what we want?)
 N       - switch dirservers entries to config lines.
 N       - let tor clients use http proxies for dir fetching
 N       - per-month byte allowances.

Index: tor.1.in
===================================================================
RCS file: /home/or/cvsroot/doc/tor.1.in,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- tor.1.in	10 Sep 2004 18:54:21 -0000	1.21
+++ tor.1.in	10 Sep 2004 18:56:52 -0000	1.22
@@ -108,7 +108,7 @@
 If 1, Tor will only create outgoing connections to ORs running on ports that
 your firewall allows (defaults to 80 and 443; see firewallports).  This will
 allow you to run Tor as a client behind a firewall with restrictive policies,
-but will not allow you server behind such a firewall.
+but will not allow you to run as a server behind such a firewall.
 .TP
 \fBfirewallports \fR\fIPORTS\fP
 A list of ports that your firewall allows you to connect to.  Only used when



More information about the tor-commits mailing list