Used :rfc: role in various docs.

5 files changed, 8 insertions, 15 deletions

diff --git a/docs/ref/contrib/gis/geos.txt b/docs/ref/contrib/gis/geos.txt
index 536c42f74e..cfb207288f 100644
--- a/docs/ref/contrib/gis/geos.txt
+++ b/docs/ref/contrib/gis/geos.txt
@@ -212,14 +212,12 @@ Format                   Input Type
 WKT / EWKT               ``str``
 HEX / HEXEWKB            ``str``
 WKB / EWKB               ``buffer``
-GeoJSON_                 ``str``
+:rfc:`GeoJSON <7946>`    ``str``
 =======================  ==========
 
 For the GeoJSON format, the SRID is set based on the ``crs`` member. If ``crs``
 isn't provided, the SRID defaults to 4326.
 
-.. _GeoJSON: https://tools.ietf.org/html/rfc7946
-
 .. classmethod:: GEOSGeometry.from_gml(gml_string)
 
     Constructs a :class:`GEOSGeometry` from the given GML string.
diff --git a/docs/ref/contrib/syndication.txt b/docs/ref/contrib/syndication.txt
index ad41ebd68e..4d2bf806ad 100644
--- a/docs/ref/contrib/syndication.txt
+++ b/docs/ref/contrib/syndication.txt
@@ -7,7 +7,7 @@ The syndication feed framework
               quite easily.
 
 Django comes with a high-level syndication-feed-generating framework for
-creating RSS_ and Atom_ feeds.
+creating RSS_ and :rfc:`Atom <4287>` feeds.
 
 To create any syndication feed, all you have to do is write a short
 Python class. You can create as many feeds as you want.
@@ -17,7 +17,6 @@ you want to generate feeds outside of a Web context, or in some other
 lower-level way.
 
 .. _RSS: http://www.whatisrss.com/
-.. _Atom: https://tools.ietf.org/html/rfc4287
 
 The high-level framework
 ========================
diff --git a/docs/ref/files/uploads.txt b/docs/ref/files/uploads.txt
index cd6cc0df5f..0021800a64 100644
--- a/docs/ref/files/uploads.txt
+++ b/docs/ref/files/uploads.txt
@@ -61,9 +61,7 @@ Here are some useful attributes of ``UploadedFile``:
     header. This is typically provided by services, such as Google App Engine,
     that intercept and handle file uploads on your behalf. As a result your
     handler may not receive the uploaded file content, but instead a URL or
-    other pointer to the file. (see `RFC 2388`_ section 5.3).
-
-    .. _RFC 2388: https://www.ietf.org/rfc/rfc2388.txt
+    other pointer to the file (see :rfc:`RFC 2388 <2388#section-5.3>`).
 
 .. attribute:: UploadedFile.charset
 
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt
index 2c69d669b0..e980147f49 100644
--- a/docs/ref/unicode.txt
+++ b/docs/ref/unicode.txt
@@ -143,11 +143,12 @@ from then on, you can treat the result as always being a string.
 URI and IRI handling
 ~~~~~~~~~~~~~~~~~~~~
 
-Web frameworks have to deal with URLs (which are a type of IRI_). One
+Web frameworks have to deal with URLs (which are a type of IRI). One
 requirement of URLs is that they are encoded using only ASCII characters.
 However, in an international environment, you might need to construct a
-URL from an IRI_ -- very loosely speaking, a URI_ that can contain Unicode
-characters. Use these functions for quoting and converting an IRI to a URI:
+URL from an :rfc:`IRI <3987>` -- very loosely speaking, a :rfc:`URI <2396>`
+that can contain Unicode characters. Use these functions for quoting and
+converting an IRI to a URI:
 
 * The :func:`django.utils.encoding.iri_to_uri()` function, which implements the
   conversion from IRI to URI as required by :rfc:`3987#section-3.1`.
@@ -213,9 +214,6 @@ following is always true::
 So you can safely call it multiple times on the same URI/IRI without risking
 double-quoting problems.
 
-.. _URI: https://www.ietf.org/rfc/rfc2396.txt
-.. _IRI: https://www.ietf.org/rfc/rfc3987.txt
-
 Models
 ======
 
diff --git a/docs/ref/utils.txt b/docs/ref/utils.txt
index a9f4107d8c..87c9f43baa 100644
--- a/docs/ref/utils.txt
+++ b/docs/ref/utils.txt
@@ -464,7 +464,7 @@ https://web.archive.org/web/20110718035220/http://diveintomark.org/archives/2004
 
 .. class:: Atom1Feed(SyndicationFeed)
 
-    Spec: https://tools.ietf.org/html/rfc4287
+    Spec: :rfc:`4287`
 
 ``django.utils.functional``
 ===========================