Regenerated docs for 3.0.1 release.

diff --git a/README b/README
index 83bcd74..e091f4e 100644 (file)
--- a/README
+++ b/README
@@ -31,20 +31,11 @@
  *
  *********************************************************************/
 
+This README is included with Privoxy 3.0.1. See http://www.privoxy.org/ for
+more information. The current code level is stable.
 
 -------------------------------------------------------------------------------
 
-     **********************************************************
-     
- NOTE: This is a pre-release version of Privoxy from the "stable" CVS branch.
- It is being readied for the next stable release -- 3.0.1 which could happen
- "soon". While this tree is in a transition state, the version will be
- intentionally stamped as "0.0.0" so as to make it clear that this code is not
- yet ready for release. If you try this code, and find problems which seem to
- be bugs, please report it to the developers list.
-
-     **********************************************************
-
 Privoxy is a web proxy with advanced filtering capabilities for protecting
 privacy, filtering web page content, managing cookies, controlling access, and
 removing ads, banners, pop-ups and other obnoxious Internet junk. Privoxy has a
@@ -120,22 +111,16 @@ with FTP or other protocols for the simple reason it does not work.
 The actions list can be configured via the web interface accessed via http://
 p.p/, as well other options.
 
-All configuration files are subject to unannounced changes during the
-development process.
-
 -------------------------------------------------------------------------------
 
 5. DOCUMENTATION
 
-There should be documentation in the 'doc' subdirectory, but it is not
-completed at this point. In particular, see the User Manual there, the FAQ, and
-those interested in Privoxy development, should look at developer-manual.
+There should be documentation in the 'doc' subdirectory. In particular, see the
+User Manual there, the FAQ, and those interested in Privoxy development, should
+look at developer-manual.
 
-The most up to date source of information on the current development version,
-may still be either comments in the source code, or the included configuration
-files. The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter' in
-the toplevel source directory.
+The source and configuration files are all well commented. The main
+configuration files are: 'config', 'default.action', and 'default.filter'.
 
 Included documentation may vary according to platform and packager. All
 documentation is posted on http://www.privoxy.org, in case you don't have it,

diff --git a/privoxy.1 b/privoxy.1
index faa6c70..2e9ad0e 100644 (file)
--- a/privoxy.1
+++ b/privoxy.1
@@ -3,7 +3,7 @@
 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "PRIVOXY" "1" "17 March 2003" "Privoxy 3.0.1" ""
+.TH "PRIVOXY" "1" "18 March 2003" "Privoxy 3.0.1" ""
 .SH NAME
 privoxy \- Privacy Enhancing Proxy
 .SH SYNOPSIS
@@ -43,10 +43,12 @@ After (optionally) writing the PID file, assume the user ID of
 sufficient to do so.
 .TP
 \fB--chroot\fR
-Before changing to the user ID given in the --user option, chroot to that user's home
-directory, i.e. make the kernel pretend to the Privoxy process that the directory tree
-starts there. If set up carefully, this can limit the impact of possible vulnerabilities
-in Privoxy to the files contained in that hierarchy.
+Before changing to the user ID given in the --user option, chroot to
+that user's home directory, i.e. make the kernel pretend to the
+\fBPrivoxy\fR process that the directory tree starts
+there. If set up carefully, this can limit the impact of possible
+vulnerabilities in \fBPrivoxy\fR to the files contained in
+that hierarchy. 
 .PP
 If the \fIconfigfile\fR is not specified on  the  command  line,
 \fBPrivoxy\fR  will  look for a file named
@@ -99,8 +101,7 @@ these files are in the same directory as the \fBPrivoxy\fR
 executable.
 .PP
 The name and number of configuration files has changed from previous
-versions, and is subject to change as development
-progresses. In fact, the configuration itself is changed  and  much more
+versions. In fact, the configuration itself is changed  and  much more
 sophisticated. See the user-manual for a complete
 explanation of all configuration options and general usage, and notes for 
 upgrading from \fBJunkbuster\fR and earlier \fBPrivoxy\fR