X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=INSTALL;h=22166940c9fbe6a14833697209631ebc20ca1d59;hp=09ab9046c6378f4635b48675d2b5930dc3c95704;hb=58b518549b4cad7b89e2e87def5169d83ceb2d45;hpb=24819687ad6f130c6966ac8995935751c6b607e0

diff --git a/INSTALL b/INSTALL
index 09ab9046..22166940 100644
--- a/INSTALL
+++ b/INSTALL
@@ -40,8 +40,8 @@ compiler like gcc are required.
 
 When building from a source tarball, first unpack the source:
 
- tar xzvf privoxy-3.0.9-beta-src* [.tgz or .tar.gz]
- cd privoxy-3.0.9-beta
+ tar xzvf privoxy-3.0.11-beta-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.11-beta
 
 
 For retrieving the current CVS sources, you'll need a CVS client installed.
@@ -155,14 +155,13 @@ correct paths and values, if anything other than a default install is done.
 
 If install finds previous versions of local configuration files, most of these
 will not be overwritten, and the new ones will be installed with a "new"
-extension. default.action, default.filter, and standard.action will be
-overwritten. You will then need to manually update the other installed
-configuration files as needed. The default template files will be overwritten.
-If you have customized, local templates, these should be stored safely in a
-separate directory and defined in config by the "templdir" directive. It is of
-course wise to always back-up any important configuration files "just in case".
-If a previous version of Privoxy is already running, you will have to restart
-it manually.
+extension. default.action and default.filter will be overwritten. You will then
+need to manually update the other installed configuration files as needed. The
+default template files will be overwritten. If you have customized, local
+templates, these should be stored safely in a separate directory and defined in
+config by the "templdir" directive. It is of course wise to always back-up any
+important configuration files "just in case". If a previous version of Privoxy
+is already running, you will have to restart it manually.
 
 For more detailed instructions on how to build Redhat RPMs, Windows
 self-extracting installers, building on platforms with special requirements