Regenerate config

[privoxy.git] / README

diff --git a/README b/README
index 559801f..3916991 100644 (file)
--- a/README
+++ b/README
@@ -32,8 +32,9 @@
  *
  *********************************************************************/
 
  *
  *********************************************************************/
 

-This README is included with Privoxy 3.0.22. See http://www.privoxy.org/ for
-more information. The current code maturity level is "stable".
+This README is included with the development version of Privoxy 3.0.25. See
+http://www.privoxy.org/ for more information. The current code maturity level
+is "UNRELEASED", but seems stable to us :).

 
 -------------------------------------------------------------------------------
 
 
 -------------------------------------------------------------------------------
 


@@ -104,16 +105,22 @@ try it 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.
 
 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
 
 -------------------------------------------------------------------------------
 
 5. DOCUMENTATION
 

-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.
+There should be documentation in the 'doc' subdirectory, but it may not be
+completed at this point. In particular, see the User Manual there, the FAQ, and
+those interested in Privoxy development, should look at developer-manual.

 
 

-The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter'.
+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 top-level source directory.

 
 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,
 
 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,


@@ -135,7 +142,7 @@ A lot of support requests don't contain enough information and can't be solved
 without a lot of back and forth which causes unnecessary delays. Reading this
 section should help to prevent that.
 
 without a lot of back and forth which causes unnecessary delays. Reading this
 section should help to prevent that.
 

-Before contacting us to report a problem, please try to verify that it is a
+Before contacting us to report a problem, please try to verify that it is a 

 Privoxy problem, and not a browser or site problem or documented behaviour that
 just happens to be different than what you expected. If unsure, try toggling
 off Privoxy, and see if the problem persists.
 Privoxy problem, and not a browser or site problem or documented behaviour that
 just happens to be different than what you expected. If unsure, try toggling
 off Privoxy, and see if the problem persists.


@@ -156,7 +163,7 @@ requesting support:
 
   * The operating system and versions you run Privoxy on, e.g. Windows XP SP2.
 
 
   * The operating system and versions you run Privoxy on, e.g. Windows XP SP2.
 

-  * The name, platform, and version of the browser you were using (e.g.
+  * The name, platform, and version of the browser you were using (e.g. 

     Internet Explorer v5.5 for Mac).
 
   * The URL where the problem occurred, or some way for us to duplicate the
     Internet Explorer v5.5 for Mac).
 
   * The URL where the problem occurred, or some way for us to duplicate the