[tor-commits] [flashproxy/master] Typo.

[dcf at torproject.org]

commit 0e9f651b2c004c27452d8f7f3426f23172ce9e75
Author: David Fifield <david at bamsoftware.com>
Date:   Sat Jun 8 20:17:59 2013 -0700

    Typo.
---
 doc/flashproxy-client.1     |    8 ++++----
 doc/flashproxy-client.1.txt |    2 +-
 flashproxy-client           |    2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/flashproxy-client.1 b/doc/flashproxy-client.1
index 6cb4a0d..e9fea5c 100644
--- a/doc/flashproxy-client.1
+++ b/doc/flashproxy-client.1
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: flashproxy-client
 .\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
-.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
-.\"      Date: 04/30/2013
+.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\"      Date: 06/08/2013
 .\"    Manual: \ \&
 .\"    Source: \ \&
 .\"  Language: English
 .\"
-.TH "FLASHPROXY\-CLIENT" "1" "04/30/2013" "\ \&" "\ \&"
+.TH "FLASHPROXY\-CLIENT" "1" "06/08/2013" "\ \&" "\ \&"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -38,7 +38,7 @@ Wait for connections on a local and a remote port\&. When any pair of connection
 .sp
 The local connection acts as a SOCKS4a proxy, but the host and port in the SOCKS request are ignored and the local connection is always linked to a remote connection\&.
 .sp
-By default, runs as a managed proxy: informs a parent Tor project of support for the "websocket" pluggable transport\&. In managed mode, the \fILOCAL\fR port is chosen arbitrarily instead of defaulting to 9001; however this can be overridden by including a \fILOCAL\fR port in the command\&. This is the way the program should be invoked in a torrc ClientTransportPlugin "exec" line\&. Use the \fB\-\-external\fR option to run as an external proxy that does not interact with Tor\&.
+By default, runs as a managed proxy: informs a parent Tor process of support for the "websocket" pluggable transport\&. In managed mode, the \fILOCAL\fR port is chosen arbitrarily instead of defaulting to 9001; however this can be overridden by including a \fILOCAL\fR port in the command\&. This is the way the program should be invoked in a torrc ClientTransportPlugin "exec" line\&. Use the \fB\-\-external\fR option to run as an external proxy that does not interact with Tor\&.
 .sp
 If any of the \fB\-\-register\fR, \fB\-\-register\-addr\fR, or \fB\-\-register\-methods\fR options are used, then your IP address will be sent to the facilitator so that proxies can connect to you\&. You need to register in some way in order to get any service\&. The \fB\-\-facilitator\fR option allows controlling which facilitator is used; if omitted, it uses a public default\&.
 .SH "OPTIONS"
diff --git a/doc/flashproxy-client.1.txt b/doc/flashproxy-client.1.txt
index 0a7bf36..66eaa50 100644
--- a/doc/flashproxy-client.1.txt
+++ b/doc/flashproxy-client.1.txt
@@ -24,7 +24,7 @@ The local connection acts as a SOCKS4a proxy, but the host and port in the SOCKS
 request are ignored and the local connection is always linked to a remote
 connection.
 
-By default, runs as a managed proxy: informs a parent Tor project of support for
+By default, runs as a managed proxy: informs a parent Tor process of support for
 the "websocket" pluggable transport. In managed mode, the __LOCAL__ port is chosen
 arbitrarily instead of defaulting to 9001; however this can be
 overridden by including a __LOCAL__ port in the command. This is the way the
diff --git a/flashproxy-client b/flashproxy-client
index 70b2464..34f2cf8 100755
--- a/flashproxy-client
+++ b/flashproxy-client
@@ -78,7 +78,7 @@ The local connection acts as a SOCKS4a proxy, but the host and port in the SOCKS
 request are ignored and the local connection is always linked to a remote
 connection.
 
-By default, runs as a managed proxy: informs a parent Tor project of support for
+By default, runs as a managed proxy: informs a parent Tor process of support for
 the "websocket" pluggable transport. In managed mode, the LOCAL port is chosen
 arbitrarily instead of defaulting to %(local_port)d; however this can be
 overridden by including a LOCAL port in the command. This is the way the