HTTP -> HTTPS, and other linkrot fixes

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/HOWTO_RELEASE.rst.txt b/doc/HOWTO_RELEASE.rst.txt
index 3ed15e99c..f849effa1 100644
--- a/doc/HOWTO_RELEASE.rst.txt
+++ b/doc/HOWTO_RELEASE.rst.txt
@@ -18,16 +18,16 @@ Source tree
 NumPy Docs
 ----------
 * https://github.com/numpy/numpy/blob/master/doc/HOWTO_RELEASE.rst.txt
-* http://projects.scipy.org/numpy/wiki/MicrosoftToolchainSupport
+* http://projects.scipy.org/numpy/wiki/MicrosoftToolchainSupport (dead link)
 
 SciPy.org wiki
 --------------
-* http://www.scipy.org/Installing_SciPy and links on that page.
-* http://new.scipy.org/building/windows.html
+* https://www.scipy.org/Installing_SciPy and links on that page.
+* http://new.scipy.org/building/windows.html (dead link)
 
 Doc wiki
 --------
-* http://docs.scipy.org/numpy/docs/numpy-docs/user/install.rst/
+* http://docs.scipy.org/numpy/docs/numpy-docs/user/install.rst/ (dead link)
 
 Release Scripts
 ---------------
@@ -56,7 +56,7 @@ Windows
 We build 32- and 64-bit wheels for Python 2.7, 3.4, 3.5 on Windows. Windows
 XP, Vista, 7, 8 and 10 are supported.  We build numpy using the MSVC compilers
 on Appveyor, but we are hoping to update to a `mingw-w64 toolchain
-<http://mingwpy.github.io>`_.  The Windows wheels use ATLAS for BLAS / LAPACK.
+<https://mingwpy.github.io>`_.  The Windows wheels use ATLAS for BLAS / LAPACK.
 
 Linux
 -----
@@ -101,7 +101,7 @@ Building source archives and wheels
 You will need write permission for numpy-wheels in order to trigger wheel
 builds.
 
-* Python(s) from `python.org <http://python.org>`_ or linux distro.
+* Python(s) from `python.org <https://python.org>`_ or linux distro.
 * cython
 * virtualenv (pip)
 * Paver (pip)
@@ -131,7 +131,7 @@ Generating author/pr lists
 --------------------------
 
 You will need an personal access token
-`<https://help.github.com/articles/creating-an-access-token-for-command-line-use/>`_
+`<https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>`_
 so that scripts can access the github numpy repository
 
 * gitpython (pip)
@@ -206,7 +206,7 @@ Do::
 
 to check that the documentation is in a buildable state.  See
 doc/HOWTO_BUILD_DOCS.rst.txt for more details and for how to update
-http://docs.scipy.org.
+https://docs.scipy.org.
 
 Check deprecations
 ------------------
@@ -322,7 +322,7 @@ message).  Unfortunately the name of a tag can be changed without breaking the
 signature, the contents of the message cannot.
 
 See : https://github.com/scipy/scipy/issues/4919 for a discussion of signing
-release tags, and http://keyring.debian.org/creating-key.html for instructions
+release tags, and https://keyring.debian.org/creating-key.html for instructions
 on creating a GPG key if you do not have one.
 
 To make your key more readily identifiable as you, consider sending your key
@@ -387,7 +387,7 @@ The tar-files and binary releases for distribution should be uploaded to SourceF
 together with the Release Notes and the Changelog. Uploading can be done
 through a web interface or, more efficiently, through scp/sftp/rsync as
 described in the SourceForge
-`upload guide <https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download>`_.
+`upload guide <https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download>`_ (dead link).
 For example::
 
   scp <filename> <username>,numpy@frs.sourceforge.net:/home/frs/project/n/nu/numpy/NumPy/<releasedir>/
@@ -472,7 +472,7 @@ repository.
 Update docs.scipy.org
 ---------------------
 
-All documentation for a release can be updated on http://docs.scipy.org/ with:
+All documentation for a release can be updated on https://docs.scipy.org/ with:
 
     make dist
     make upload USERNAME=<yourname> RELEASE=1.11.0