Fix some incorrect links

Author: slateny

committing.rst

@@ -60,9 +60,9 @@ to enter the public source tree. Ask yourself the following questions:
    Licensing Agreement <https://www.python.org/psf/contrib/contrib-form/>`_ 
    (CLA), unless their change has no possible intellectual property 
    associated with it (e.g. fixing a spelling mistake in documentation). 
-   To check if a contributor’s CLA has been received, go
-   to `Check Python CLA <https://check-python-cla.herokuapp.com/>`_ and
-   put in their GitHub username. For further questions about the CLA
+   The `CPython CLA Bot <https://github.com/apps/cpython-cla-bot/>`_
+   checks whether the author has signed the CLA, and replies in the PR
+   if they haven't. For further questions about the CLA
    process, write to [email protected].
 
 * **Were** ``What's New in Python`` **and** ``Misc/NEWS.d/next`` **updated?** 

compiler.rst

@@ -686,7 +686,7 @@ References
    https://www.cs.princeton.edu/research/techreps/TR-554-97
 
 .. [#skip-peephole] Skip Montanaro's Peephole Optimizer Paper
-   (https://drive.google.com/open?id=0B2InO7qBBGRXQXlDM3FVdWZxQWc)
+   (https://legacy.python.org/workshops/1998-11/proceedings/papers/montanaro/montanaro.html)
 
 .. [#Bytecodehacks] Bytecodehacks Project
    (http://bytecodehacks.sourceforge.net/bch-docs/bch/index.html)

docquality.rst

@@ -62,7 +62,7 @@ If you see a documentation issue that you would like to tackle, you can:
 By following the steps in the :ref:`Quick Guide to Pull Requests <pullrequest-quickguide>`,
 you will learn the workflow for documentation pull requests.
 
-.. _documentation issues: https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocumentation
+.. _documentation issues: https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs
 .. _octocat: https://github.com/logos