From 35b86d50c3d32360ec69800078928dff95f9ff46 Mon Sep 17 00:00:00 2001
From: Steve Piercy <web@stevepiercy.com>
Date: Sat, 17 Aug 2019 02:44:45 -0700
Subject: run linkcheck, fix redirects, change busted links to inline literals

---
 docs/narr/introduction.rst | 6 +++---
 docs/narr/renderers.rst    | 4 ++--
 docs/narr/templates.rst    | 2 +-
 docs/narr/testing.rst      | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

(limited to 'docs/narr')

diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index b32013931..f62e28905 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -35,7 +35,7 @@ Reliability
   :app:`Pyramid` is developed conservatively and tested exhaustively. Our motto is: "If it ain't tested, it's broke".
 
 Openness
-  As with Python, the :app:`Pyramid` software is distributed under a `permissive open source license <http://repoze.org/license.html>`_.
+  As with Python, the :app:`Pyramid` software is distributed under a `permissive open source license <https://web.archive.org/web/20190401024809/http://repoze.org/license.html>`_.
 
 .. _why_pyramid:
 
@@ -52,7 +52,7 @@ Modern
 Tested
 ~~~~~~
 
-Untested code is broken by design. The :app:`Pyramid` community has a strong testing culture and our framework reflects that. Every release of :app:`Pyramid` has 100% statement coverage (as measured by `coverage <https://coverage.readthedocs.io/en/latest/>`_) and 95% decision/condition coverage. (as measured by `instrumental <https://instrumental.readthedocs.io/en/latest/intro.html>`_) It is automatically tested using `Travis <https://travis-ci.org/Pylons/pyramid>`_ and `Jenkins <http://jenkins.pylonsproject.org/job/pyramid/>`_ on supported versions of Python after each commit to its GitHub repository. `Official Pyramid add-ons <https://trypyramid.com/extending-pyramid.html>`_ are held to a similar testing standard.
+Untested code is broken by design. The :app:`Pyramid` community has a strong testing culture and our framework reflects that. Every release of :app:`Pyramid` has 100% statement coverage (as measured by `coverage <https://coverage.readthedocs.io/en/latest/>`_) and 95% decision/condition coverage. (as measured by `instrumental <https://instrumental.readthedocs.io/en/latest/intro.html>`_) It is automatically tested using `Travis <https://travis-ci.org/Pylons/pyramid>`_ and Jenkins on supported versions of Python after each commit to its GitHub repository. `Official Pyramid add-ons <https://trypyramid.com/extending-pyramid.html>`_ are held to a similar testing standard.
 
 We still find bugs in :app:`Pyramid`, but we've noticed we find a lot fewer of them while working on projects with a solid testing regime.
 
@@ -70,7 +70,7 @@ You can get help quickly with :app:`Pyramid`. It's our goal that no :app:`Pyrami
 
 .. seealso::
 
-    See also our `#pyramid IRC channel <https://webchat.freenode.net/?channels=pyramid>`_, our `pylons-discuss mailing list <https://groups.google.com/forum/#!forum/pylons-discuss>`_, and :ref:`support-and-development`.
+    See also our `#pyramid IRC channel <https://webchat.freenode.net/#pyramid>`_, our `pylons-discuss mailing list <https://groups.google.com/forum/#!forum/pylons-discuss>`_, and :ref:`support-and-development`.
 
 .. _what_makes_pyramid_unique:
 
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index 6b4982e4b..21cfa0497 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -357,9 +357,9 @@ When a view is called that uses a JSONP renderer:
 
 Javscript library AJAX functionality will help you make JSONP requests.
 For example, JQuery has a `getJSON function
-<http://api.jquery.com/jQuery.getJSON/>`_, and has equivalent (but more
+<https://api.jquery.com/jQuery.getJSON/>`_, and has equivalent (but more
 complicated) functionality in its `ajax function
-<http://api.jquery.com/jQuery.ajax/>`_.
+<https://api.jquery.com/jQuery.ajax/>`_.
 
 For example (JavaScript):
 
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index e5244e1ad..34d9a115c 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -452,7 +452,7 @@ templating languages including the following:
 .. _pyramid_chameleon:
    https://docs.pylonsproject.org/projects/pyramid-chameleon/en/latest/
 
-.. _Jinja2: http://jinja.pocoo.org/docs/dev/
+.. _Jinja2: https://jinja.palletsprojects.com/en/2.10.x/
 .. _pyramid_jinja2:
    https://docs.pylonsproject.org/projects/pyramid-jinja2/en/latest/
 
diff --git a/docs/narr/testing.rst b/docs/narr/testing.rst
index 01cea969e..883bb7c7b 100644
--- a/docs/narr/testing.rst
+++ b/docs/narr/testing.rst
@@ -50,7 +50,7 @@ The suggested mechanism for unit and integration testing of a :app:`Pyramid`
 application is the Python :mod:`unittest` module.  Although this module is
 named :mod:`unittest`, it is actually capable of driving both unit and
 integration tests.  A good :mod:`unittest` tutorial is available within `Dive
-Into Python 3 <https://www.diveinto.org/python3/unit-testing.html>`_ by Mark
+Into Python 3 <https://diveinto.org/python3/unit-testing.html>`_ by Mark
 Pilgrim.
 
 :app:`Pyramid` provides a number of facilities that make unit, integration, and
-- 
cgit v1.2.3