From: Roger Dingledine Date: Thu, 3 Nov 2011 23:08:25 +0000 (-0400) Subject: fix grammar in man page entries from proposal 171 X-Git-Tag: tor-0.2.3.8-alpha~58 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=350fe952590fdfd1711aaaddcb478cdea20b6e6a;p=thirdparty%2Ftor.git fix grammar in man page entries from proposal 171 --- diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 89dd7dc638..c99c99984c 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -694,11 +694,11 @@ The following options are useful only for clients (that is, if received on this SOCKSPort are allowed to share circuits with one another. Recognized isolation flags are: **IsolateClientAddr**;; - Don't share a circuits with streams from a different + Don't share circuits with streams from a different client address. (On by default and strongly recommended; you can disable it with **NoIsolateClientAddr**.) **IsolateSOCKSAuth**;; - Don't share a circuits with streams for which different + Don't share circuits with streams for which different SOCKS authentication was provided. (On by default; you can disable it with **NoIsolateSOCKSAuth**.) **IsolateClientProtocol**;; @@ -706,10 +706,10 @@ The following options are useful only for clients (that is, if (SOCKS 4, SOCKS 5, TransPort connections, NATDPort connections, and DNSPort requests are all considered to be different protocols.) **IsolateDestPort**;; - Don't share a circuits with streams targetting a different + Don't share circuits with streams targetting a different destination port. **IsolateDestAddr**;; - Don't share a circuits with streams targetting a different + Don't share circuits with streams targetting a different destination address. **SessionGroup=**__INT__;; If no other isolation rules would prevent it, allow streams