X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=README;h=eb50b2220e9665062ff2aefb6b573993d2831a43;hp=890964c9fb345b76792afd0c0ee7b98cab4e8daa;hb=e73669aae7d505c90e5ea9507d07543b06ab4245;hpb=4985684a0376e6a84c5f542c7324617259092575

diff --git a/README b/README
index 890964c9..eb50b222 100644
--- a/README
+++ b/README
@@ -1,10 +1,10 @@
 /*********************************************************************
  *
- * File        :  doc/source/readme.sgml
+ * File        :  README
  *
- * Purpose     :  README file to give a short intro.
+ * Purpose     :  Give a short intro about Privoxy.
  *
- * Copyright   :  Written by and Copyright (C) 2001-2020 the
+ * Copyright   :  Written by and Copyright (C) 2001-2021 the
  *                Privoxy team. https://www.privoxy.org/
  *
  *                Based on the Internet Junkbuster originally written
@@ -32,7 +32,7 @@
  *
  *********************************************************************/
 
-This README is included with the development version of Privoxy 3.0.30. See
+This README is included with the development version of Privoxy 3.0.34. See
 https://www.privoxy.org/ for more information. The current code maturity level
 is "UNRELEASED", but seems stable to us :).
 
@@ -169,8 +169,8 @@ requesting support:
   * The URL where the problem occurred, or some way for us to duplicate the
     problem (e.g. http://somesite.example.com/?somethingelse=123).
 
-  * Whether your version of Privoxy is one supplied by the Privoxy developers
-    via SourceForge, or if you got your copy somewhere else.
+  * Whether your version of Privoxy is one supplied by the Privoxy developers,
+    or if you got your copy somewhere else.
 
   * Whether you are using Privoxy together with another proxy such as Tor. If
     so, please temporary disable the other proxy to see if the symptoms change.
@@ -184,10 +184,10 @@ requesting support:
     directive is being used and the following debug options are enabled (all of
     them):
 
-    debug     1 # Log the destination for each request Privoxy let through.
+    debug     1 # Log the destination for each request. See also debug 1024.
                 #   See also debug 1024.
     debug     2 # show each connection status
-    debug     4 # show I/O status
+    debug     4 # show tagging-related messages
     debug     8 # show header parsing
     debug   128 # debug redirects
     debug   256 # debug GIF de-animation
@@ -203,7 +203,7 @@ requesting support:
     debug    64 # debug regular expression filters
 
     If you suspect that Privoxy interprets the request or the response
-    incorrectly, please enable
+    incorrectly, please enable additionally
 
     debug 32768 # log all data read from the network
 
@@ -216,6 +216,8 @@ requesting support:
     don't submit any logfiles you didn't read first. You can mask sensitive
     information as long as it's clear that you removed something.
 
+    Please clear the browser cache before reproducing the problem.
+
 You don't have to tell us your actual name when filing a problem report, but if
 you don't, please use a nickname so we can differentiate between your messages
 and the ones entered by other "anonymous" users that may respond to your
@@ -230,9 +232,6 @@ automatically get a mail when someone responds to your request. Please don't
 bother to add an email address when using the tracker. If you prefer to
 communicate through email, just use one of the mailing lists directly.
 
-If you are new to reporting problems, you might be interested in How to Report
-Bugs Effectively.
-
 The appendix of the Privoxy User Manual also has helpful information on
 understanding actions, and action debugging.