Minor updates to clarify how to put the documentation in place.

pep-0101.txt

@@ -290,15 +290,15 @@ How to Make A Release
 
       This should be rare and indicates a breakdown in the process.
 
-  ___ Use the release script to create the gzip and bz2 tarballs, md5
-      checksums, and gpg signature files.
+  ___ Use the release script to create the source gzip and bz2 tarballs, md5
+      checksums, documentation tar and zip files, and gpg signature files.
 
       .../sandbox/release/release.py --export X.YaZ
 
       This will leave all the relevant files in a subdirectory called 'dist',
       and the built docs in 'dist/docs'.
 
-  ___ scp the files to your home directory on dinsdale.python.org.
+  ___ scp or rsync all the files to your home directory on dinsdale.python.org.
 
       While you're waiting for the files to finish uploading, you can continue
       on with the remaining tasks.  You can also ask folks on #python-dev
@@ -379,10 +379,13 @@ How to Make A Release
       ___ md5sum the files and make sure they got uploaded intact.
 
       ___ If this is a final release: Move the doc zips and tarballs to
-          /data/ftp.python.org/pub/python/doc/X.Y[.Z], and adapt the
-          "current" symlink in that directory.
+          /data/ftp.python.org/pub/python/doc/X.Y[.Z] creating the directory
+          if necessary, and adapt the "current" symlink in .../doc to point to
+          that directory.  Note though that if you're releasing a maintenance
+          release for an older version, don't change the current link.
 
-      ___ If this is a final release, also unpack the HTML docs to
+      ___ If this is a final release (even a maintenance release), also unpack
+          the HTML docs to
           /data/ftp.python.org/pub/docs.python.org/release/X.Y[.Z].
 
       ___ Let the DE check if the docs are built and work all right.