diff --git a/pep-0101.txt b/pep-0101.txt
index cd0922b9b..de27220a8 100644
--- a/pep-0101.txt
+++ b/pep-0101.txt
@@ -35,8 +35,8 @@ Things You'll Need
       which hopefully will be on the "web of trust" with at least one of
       the other release managers.
 
-    * Access to ``dinsdale.python.org``, the Python web host.  You'll
-      be uploading files directly here.
+    * Access to ``dl-files.psf.io``, the server that hosts download files.
+      You'll be uploading files directly here.
 
     * Shell access to ``hg.python.org``, the Python Mercurial host.  You'll
       have to adapt repository configuration there.
@@ -335,11 +335,11 @@ How to Make A Release
       - Now he runs msi.py with ActivePython or Python with pywin32.
 
       The WE checksums the files (*.msi, *.chm, *-pdb.zip), uploads them to
-      dinsdale together with gpg signature files, and emails you the location
-      and md5sums.
+      dl-files.psf.io together with gpg signature files, and emails you the
+      location and md5sums.
 
-  ___ The ME builds Mac installer packages and uploads them to dinsdale together
-      with gpg signature files.
+  ___ The ME builds Mac installer packages and uploads them to dl-files.psf.io
+      together with gpg signature files.
 
   ___ Time to build the source tarball.  Be sure to update your clone to the
       correct branch.  E.g.
@@ -364,7 +364,7 @@ How to Make A Release
       tarballs and signatures in a subdirectory called 'X.Y.ZaN/src', and the
       built docs in 'X.Y.ZaN/docs' (for final releases).
 
-  ___ scp or rsync all the files to your home directory on dinsdale.python.org.
+  ___ scp or rsync all the files to your home directory on dl-files.psf.io.
 
       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
@@ -401,32 +401,32 @@ How to Make A Release
       freshly unpacked directory looks weird, you better stop now and
       figure out what the problem is.
 
-  ___ Now you need to go to dinsdale.python.org and move all the files in
+  ___ Now you need to go to dl-files.psf.io and move all the files in
       place over there.  Our policy is that every Python version gets its own
       directory, but each directory contains all releases of that version.
 
-      ___ On dinsdale, cd /data/ftp.python.org/pub/python/X.Y.Z
-          creating it if necessary.  Make sure it is owned by group 'webmaster'
-          and group-writable.
+      ___ On dl-files.psf.io, cd /srv/www.python.org/ftp/python/X.Y.Z creating
+          it if necessary.  Make sure it is owned by group 'downloads' and
+          group-writable.
 
       ___ Move the release .tgz, and .tar.xz files into place, as well as the
           .asc GPG signature files.  The Win/Mac binaries are usually put there
           by the experts themselves.
 
           Make sure they are world readable.  They should also be group
-          writable, and group-owned by webmaster.
+          writable, and group-owned by downloads.
 
       ___ Use `gpg --verify` to 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 creating the directory
+          /srv/www.python.org/ftp/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 (even a maintenance release), also unpack
           the HTML docs to
-          /data/ftp.python.org/pub/docs.python.org/release/X.Y.Z.
+          /data/ftp.python.org/pub/docs.python.org/release/X.Y.Z on dinsdale.
           If it is a release of a security-fix-only version, tell the DE to
           build a version with the "version switcher" and put it there.
 
@@ -492,7 +492,7 @@ How to Make A Release
           production release" paragraph as appropriate
 
       Note, you don't have to copy any release files into this directory;
-      they only live on dinsdale in the ftp directory.
+      they only live on dl-files.psf.io in the ftp directory.
 
   ___ Edit `download/releases/content.ht` to update the version numbers for
       this release.  There are a bunch of places you need to touch: