Regenerate docs for 3.0.21 stable

[privoxy.git] / doc / webserver / developer-manual / newrelease.html

diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html
index 60995a2..fb10326 100644 (file)
--- a/doc/webserver/developer-manual/newrelease.html
+++ b/doc/webserver/developer-manual/newrelease.html
@@ -185,11 +185,11 @@
           Finished docs should be then be committed to CVS (for those without
           the ability to build these). Some docs may require rather obscure
           processing tools. <tt class="FILENAME">config</tt>, the man page
-          (and the html version of the man page), and the PDF docs fall in
-          this category. REAMDE, the man page, AUTHORS, and config should all
-          also be committed to CVS for other packagers. The formal docs
-          should be uploaded to the webserver. See the Section "Updating the
-          webserver" in this manual for details.</p>
+          (and the html version of the man page) fall in this category.
+          REAMDE, the man page, AUTHORS, and config should all also be
+          committed to CVS for other packagers. The formal docs should be
+          uploaded to the webserver. See the Section "Updating the webserver"
+          in this manual for details.</p>
         </li>
 
         <li>
@@ -738,7 +738,7 @@
           <tr>
             <td>
               <pre class="PROGRAMLISTING">
-  debchange -v 3.0.21-UNRELEASED-1 "New upstream version"
+  debchange -v 3.0.21-stable-1 "New upstream version"
 </pre>
             </td>
           </tr>
@@ -757,7 +757,7 @@
         </table>
 
         <p>This will create <tt class=
-        "FILENAME">../privoxy_3.0.21-UNRELEASED-1_i386.deb</tt> which can be
+        "FILENAME">../privoxy_3.0.21-stable-1_i386.deb</tt> which can be
         uploaded. To upload the package to Sourceforge, simply issue</p>
 
         <table border="0" bgcolor="#E0E0E0" width="100%">