+ <p>Remove reference to 'How to Report Bugs Effectively'. It was only rendered as text without URL in the
+ README anyway and there's no indication that users read it ...</p>
+ </li>
+ <li>
+ <p>Let the dok-readme target fix the location embedded into the README file. This used to be done by CVS
+ but since the git migration it has to be done through other means.</p>
+ </li>
+ <li>
+ <p>Remove 'experimental' warning for client-specific-tag-related directives. They seem to work reliably and
+ there is no obvious reason why we would change the syntax in the near future.</p>
+ </li>
+ <li>
+ <p>Describe how to check if Privoxy has been built with FEATURE_HTTPS_INSPECTION.</p>
+ </li>
+ <li>
+ <p>Add a link to the trusted-cas-file documentation that explains how the user can create the file
+ herself.</p>
+ </li>
+ <li>
+ <p>Don't explicitly mention the license for the code coming from 'Anonymous Coders' and Junkbusters. It's
+ obviously licensed under the GNU GPL like the rest of Privoxy or we wouldn't be allowed to distribute
+ it.</p>
+ </li>
+ <li>
+ <p>Update the +hide-user-agent example with uagen output.</p>
+ </li>
+ <li>
+ <p>Slightly improve the wording of the ca-key-file documentation.</p>
+ </li>
+ <li>
+ <p>Explicitly mention Windows 10 as supported so search engines and users looking for it can find it.</p>
+ </li>
+ <li>
+ <p>Import a bunch of contributors from the ChangeLog.</p>
+ </li>
+ <li>
+ <p>Remove obsolete doc/gpl.html.</p>