[or-cvs] r10350: cleanups on man page from edmanm (tor/trunk/doc)

[arma@xxxxxxxx]

Author: arma
Date: 2007-05-26 03:42:06 -0400 (Sat, 26 May 2007)
New Revision: 10350

Modified:
   tor/trunk/doc/tor.1.in
Log:
cleanups on man page from edmanm


Modified: tor/trunk/doc/tor.1.in
===================================================================
--- tor/trunk/doc/tor.1.in	2007-05-26 00:39:10 UTC (rev 10349)
+++ tor/trunk/doc/tor.1.in	2007-05-26 07:42:06 UTC (rev 10350)
@@ -776,7 +776,7 @@
 Overrides the default DNS configuration with the configuration in
 \fIfilename\fP.  The file format is the same as the standard Unix
 "\fBresolv.conf\fP" file (7).  This option, like all other
-ServerDNS options, only affects name lookup that your server does on
+ServerDNS options, only affects name lookups that your server does on
 behalf of clients.  Also, it only takes effect if Tor was built with
 eventdns support.  (Defaults to use the system DNS configuration.)
 .LP
@@ -786,8 +786,8 @@
 domain.  For example, if this system is configured to believe it is in
 "example.com", and a client tries to connect to "www", the client will be
 connected to "www.example.com".
-This option only affects name lookup that your server does on
-behalf of clients, and only takes effect if Tor was build with
+This option only affects name lookups that your server does on
+behalf of clients, and only takes effect if Tor was built with
 eventdns support.
 (Defaults to "0".)
 .LP
@@ -797,8 +797,8 @@
 our local nameservers have been configured to hijack failing DNS requests
 (usually to an advertising site).  If they are, we will attempt to correct
 this.
-This option only affects name lookup that your server does on
-behalf of clients, and only takes effect if Tor was build with
+This option only affects name lookups that your server does on
+behalf of clients, and only takes effect if Tor was built with
 eventdns support.
 (Defaults to "1".)
 .LP
@@ -807,8 +807,8 @@
 When we're detecting DNS hijacking, make sure that these \fIvalid\fP
 addresses aren't getting redirected.  If they are, then our DNS is
 completely useless, and we'll reset our exit policy to "reject *:*".
-This option only affects name lookup that your server does on
-behalf of clients, and only takes effect if Tor was build with
+This option only affects name lookups that your server does on
+behalf of clients, and only takes effect if Tor was built with
 eventdns support.
 (Defaults to "www.google.com, www.mit.edu, www.yahoo.com,
 www.slashdot.org".)
@@ -819,8 +819,8 @@
 containing illegal characters (like @ and :) rather than sending them to an
 exit node to be resolved.  This helps trap accidental attempts to resolve
 URLs and so on.
-This option only affects name lookup that your server does on
-behalf of clients, and only takes effect if Tor was build with
+This option only affects name lookups that your server does on
+behalf of clients, and only takes effect if Tor was built with
 eventdns support.
 (Default: 0)