+ Update example output.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommend the use of the https-inspection action in the documentation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Upgrade a couple of URLs to https://.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add ElectroBSD to the list of operating systems.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bumped generated Firefox version to 78 (ESR).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bumped version to 1.2.2.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ User documentation:
+ <itemizedlist>
+ <listitem>
+ <para>
+ 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 ...
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Describe how to check if Privoxy has been built with
+ FEATURE_HTTPS_INSPECTION.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a link to the trusted-cas-file documentation
+ that explains how the user can create the file herself.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update the +hide-user-agent example with uagen output.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Slightly improve the wording of the ca-key-file documentation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explicitly mention Windows 10 as supported so search engines and
+ users looking for it can find it.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Import a bunch of contributors from the ChangeLog.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remove obsolete doc/gpl.html.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Upgrade a couple of links to https://.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Don't prefer the SourceForge patch tracker over the
+ privoxy-devel mailing list. While at it, link to the
+ SourceForge patch tracker.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Mention http-inspection in the 'my browser warns me about
+ unauthenticated content' FAQ entry.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Simplify the 'Is there is a license or fee?' FAQ entry.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add another +redirect{} example.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explicitly mention that interested sponsors should include
+ the link target in their first mail.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clarify that only Privoxy team members can object to new sponsors
+ and link to the list of current team members.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Note that sponsor URLs may not contain keyword spam.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Garbage collect doc/webserver/images which isn't referenced anymore.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update the method to reach the proxy settings in Firefox.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update proxy_setup.jpg description to refer to Firefox.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Regenerate proxy_setup.jpg with a more recent Firefox (78.0).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Regenerate files-in-use.jpg without obsolete standard.action
+ with modern colors and a slightly better quality.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update URL to the actionsfile tracker.