Replaced references in docs to accepted PEPs with specific Python docs links.

Where the docs used `:pep:` links for established Python language
features, replaced them with direct references to the Python docs
(usually glossary terms).

4 files changed, 9 insertions, 10 deletions

diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt
index 93c6ec4203..4ffff03457 100644
--- a/docs/ref/exceptions.txt
+++ b/docs/ref/exceptions.txt
@@ -285,9 +285,9 @@ The Django wrappers for database exceptions behave exactly the same as
 the underlying database exceptions. See :pep:`249`, the Python Database API
 Specification v2.0, for further information.
 
-As per :pep:`3134`, a ``__cause__`` attribute is set with the original
-(underlying) database exception, allowing access to any additional
-information provided.
+A :attr:`~BaseException.__cause__` attribute is set with the original
+(underlying) database exception, allowing access to any additional information
+provided.
 
 .. exception:: models.ProtectedError
 
diff --git a/docs/ref/files/uploads.txt b/docs/ref/files/uploads.txt
index dd8ff99689..510b7df546 100644
--- a/docs/ref/files/uploads.txt
+++ b/docs/ref/files/uploads.txt
@@ -76,7 +76,7 @@ Here are some useful attributes of ``UploadedFile``:
         for line in uploadedfile:
             do_something_with(line)
 
-    Lines are split using :pep:`universal newlines <278>`. The following are
+    Lines are split using :term:`python:universal newlines`. The following are
     recognized as ending a line: the Unix end-of-line convention ``'\n'``, the
     Windows convention ``'\r\n'``, and the old Macintosh convention ``'\r'``.
 
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index ee401a569d..15bb800670 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -2637,9 +2637,9 @@ If you pass ``in_bulk()`` an empty list, you'll get an empty dictionary.
 
 *Asynchronous version*: ``aiterator()``
 
-Evaluates the ``QuerySet`` (by performing the query) and returns an iterator
-(see :pep:`234`) over the results, or an asynchronous iterator (see :pep:`492`)
-if you call its asynchronous version ``aiterator``.
+Evaluates the ``QuerySet`` (by performing the query) and returns an
+:term:`python:iterator` over the results, or an :term:`python:asynchronous
+iterator` if you call its asynchronous version ``aiterator``.
 
 A ``QuerySet`` typically caches its results internally so that repeated
 evaluations do not result in additional queries. In contrast, ``iterator()``
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index eda1849334..7c238702bf 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -1337,7 +1337,7 @@ Overriding settings
 
 For testing purposes it's often useful to change a setting temporarily and
 revert to the original value after running the testing code. For this use case
-Django provides a standard Python context manager (see :pep:`343`) called
+Django provides a standard :ref:`context manager <context-managers>` called
 :meth:`~django.test.SimpleTestCase.settings`, which can be used like this::
 
     from django.test import TestCase
@@ -1390,8 +1390,7 @@ neither does ``remove`` when the value doesn't exist.
 .. function:: override_settings(**kwargs)
 
 In case you want to override a setting for a test method, Django provides the
-:func:`~django.test.override_settings` decorator (see :pep:`318`). It's used
-like this::
+:func:`~django.test.override_settings` :term:`python:decorator`::
 
     from django.test import TestCase, override_settings