Update the docs steps.

pep-0101.txt

@@ -38,6 +38,7 @@ How to Make A Release
     * RM = Release Manager: Barry Warsaw <barry@python.org> (US/Eastern)
     * WE = Windows: Martin von Loewis <martin@v.loewis.de> (Central Europe)
     * ME = Mac: Ronald Oussoren <ronaldoussoren@mac.com> (Central Europe)
+    * DE = Docs: Georg Brandl <georg@python.org> (Central Europe)
     * IE = Idle Expert: ??
 
     NOTE: It is highly recommended that the RM contact the Experts the day
@@ -300,7 +301,7 @@ How to Make A Release
       steps to take:
 
       % cd /tmp
-      % tar zxvf ~/Python-2.6c2.tgz  # tar xjvf ~/Python-2.6c2.tar.bz2
+      % tar xzvf ~/Python-2.6c2.tgz  # tar xjvf ~/Python-2.6c2.tar.bz2
       % cd Python-2.6c2
       % ls
       (Do things look reasonable?)
@@ -308,7 +309,7 @@ How to Make A Release
       (Are there stray .pyc files?)
       % ls Doc/tools
       (Make sure it doesn't contain "docutils", "sphinx", "jinja" or
-      "pygments" directories.)
+      "pygments" directories.  Also look for stray .pyc files.)
       % ./configure
       (Loads of configure output)
       % make test
@@ -371,6 +372,11 @@ How to Make A Release
           /data/ftp.python.org/pub/python/doc/X.Y[.Z], and adapt the
           "current" symlink in that directory.
 
+      ___ If this is a final release, also unpack the HTML docs to
+          /data/ftp.python.org/pub/www.python.org/doc/X.Y[.Z].
+
+      ___ Let the DE check if the docs are built and work all right.
+
   Now it's time to twiddle the web site.
 
   To do these steps, you must have the permission to edit the website.  If you