[or-cvs] minor cleanups on howto

[arma at seul.org]

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

Modified Files:
	howto.txt 
Log Message:
minor cleanups on howto


Index: howto.txt
===================================================================
RCS file: /home2/or/cvsroot/control/doc/howto.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- howto.txt	11 Jul 2005 19:10:28 -0000	1.1
+++ howto.txt	11 Jul 2005 19:46:23 -0000	1.2
@@ -6,13 +6,13 @@
 0. About this document
 
    This document has instructions for writing programs to interface with
-   Tor.  You should read it if you want to write a Tor controller, of if you
+   Tor.  You should read it if you want to write a Tor controller, or if you
    want to make your programs work with Tor correctly.
 
 0.1. Further reading
 
-   You should probably have a good idea of what Tor does and how it works;
-   see the main Tor documentation for more detail.
+   You should probably have a good idea first of what Tor does and how it
+   works; see the main Tor documentation for more detail.
 
    If you want full specifications for the data formats and protocols Tor
    uses, see tor-spec.txt, control-spec.txt, and socks-extensions.txt, all of
@@ -22,7 +22,6 @@
 
    Suppose you have a simple network application, and you want that
    application to send its traffic over Tor.  This is pretty simple to do:
-   here's how.
 
      - Make sure your protocol is stream based.  If you're using TCP, you're
        fine; if you're using UDP or another non-TCP protocol, Tor can't cope
@@ -76,11 +75,14 @@
    similar API), then it will effectively broadcast the names of the hosts it
    is about to connect to.
 
-1.2. Notes on authentication
+   See http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS for
+   more details.
+
+1.2. Notes on authentication by IP address
 
    If your service uses IP addresses to prevent abuse, you should consider
    switching to a different model.  Once your software works with Tor,
-   annoying people may being using Tor to conceal their IP addresses.  If the
+   annoying people may begin using Tor to conceal their IP addresses.  If the
    best abuse-prevention scheme you have is IP based, you'll be forced to
    choose between blocking all users who want privacy, and allowing abuse.
    If you've implemented a better authorization scheme, you won't have this
@@ -108,12 +110,12 @@
 
 2. Writing a controller
 
-   If you want your application to use Tor in a more fine-grained manner (and
-   not just to anonymize your application's connections) you need to write a
-   "controller".  A controller is a program that connects to Tor and sends it
-   commands.  With a controller, you can examine and change Tor's
-   configuration on the fly, change how circuits are built, and other
-   operations.
+   If you want your application to use Tor in a more fine-grained manner
+   (i.e., not just to anonymize your application's connections) you need
+   to write a "controller".  A controller is a program that connects
+   to the Tor client and sends it commands.  With a controller, you can
+   examine and change Tor's configuration on the fly, change how circuits
+   are built, and perform other operations.
 
    As of the most recent version (0.1.0.11), Tor does not have its controller
    interface enabled by default.  You need to configure it to listen on some
@@ -131,7 +133,7 @@
 
    This document covers the Python and Java interfaces to Tor, and the
    underlying "v1" control protocol introduced in Tor version
-   0.1.1.0. Earlier versions used an older and tricker control protocol which
+   0.1.1.0. Earlier versions used an older and trickier control protocol which
    is not covered here; see "control-spec-v0.txt" for details.
 
 2.1. Getting started
@@ -451,3 +453,4 @@
  [1] http://archive.socks.permeo.com/protocol/socks4.protocol
  [2] http://archive.socks.permeo.com/protocol/socks4a.protocol
  [3] SOCKS5: RFC1928
+