consistently linky RFC in the docs (#4716)

* consistently linky RFC in the docs

* oops
diff --git a/docs/development/custom-vectors/arc4.rst b/docs/development/custom-vectors/arc4.rst
index ed8cd54..5b1b65d 100644
--- a/docs/development/custom-vectors/arc4.rst
+++ b/docs/development/custom-vectors/arc4.rst
@@ -2,14 +2,14 @@
 ====================
 
 This page documents the code that was used to generate the ARC4 test
-vectors for key lengths not available in RFC 6229. All the vectors
+vectors for key lengths not available in :rfc:`6229`. All the vectors
 were generated using OpenSSL and verified with Go.
 
 Creation
 --------
 
 ``cryptography`` was modified to support ARC4 key lengths not listed
-in RFC 6229. Then the following Python script was run to generate the
+in :rfc:`6229`. Then the following Python script was run to generate the
 vector files.
 
 .. literalinclude:: /development/custom-vectors/arc4/generate_arc4.py
diff --git a/docs/development/custom-vectors/hkdf.rst b/docs/development/custom-vectors/hkdf.rst
index 0e1a729..6d7e861 100644
--- a/docs/development/custom-vectors/hkdf.rst
+++ b/docs/development/custom-vectors/hkdf.rst
@@ -2,7 +2,7 @@
 ====================
 
 This page documents the code that was used to generate a longer
-HKDF test vector (1200 bytes) than is available in RFC 5869. All
+HKDF test vector (1200 bytes) than is available in :rfc:`5869`. All
 the vectors were generated using OpenSSL and verified with Go.
 
 Creation
diff --git a/docs/development/test-vectors.rst b/docs/development/test-vectors.rst
index 6d4d3d1..df1ecfa 100644
--- a/docs/development/test-vectors.rst
+++ b/docs/development/test-vectors.rst
@@ -154,7 +154,7 @@
   Diffie-Hellman parameters and key respectively. The keys were
   generated using OpenSSL following `DHKE`_ guide. When creating the
   parameters we added the `-pkeyopt dh_rfc5114:2` option to use
-  RFC5114 2048 bit DH parameters with 224 bit subgroup.
+  :rfc:`5114` 2048 bit DH parameters with 224 bit subgroup.
   ``vectors/cryptography_vectors/asymmetric/DH/dhkey_rfc5114_2.txt`` contains
   all parameter in text.
   ``vectors/cryptography_vectors/asymmetric/DH/dhp_rfc5114_2.der``,
diff --git a/docs/x509/reference.rst b/docs/x509/reference.rst
index 6b2f74c..b2278d5 100644
--- a/docs/x509/reference.rst
+++ b/docs/x509/reference.rst
@@ -1250,7 +1250,7 @@
 
         .. versionadded:: 2.5
 
-        :return str: Format the given name as a `RFC 4514`_ Distinguished Name
+        :return str: Format the given name as a :rfc:`4514` Distinguished Name
             string, for example ``CN=mydomain.com,O=My Org,C=US``.
 
 
@@ -1291,7 +1291,7 @@
 
         .. versionadded:: 2.5
 
-        :return str: Format the given attribute as a `RFC 4514`_ Distinguished
+        :return str: Format the given attribute as a :rfc:`4514` Distinguished
             Name string.
 
 
@@ -1314,7 +1314,7 @@
 
         .. versionadded:: 2.5
 
-        :return str: Format the given RDN set as a `RFC 4514`_ Distinguished
+        :return str: Format the given RDN set as a :rfc:`4514` Distinguished
             Name string.
 
 
@@ -1331,7 +1331,6 @@
 
         The dotted string value of the OID (e.g. ``"2.5.4.3"``)
 
-.. _`RFC 4514`: https://tools.ietf.org/html/rfc4514
 
 .. _general_name_classes:
 
@@ -2794,7 +2793,7 @@
 
         Corresponds to the dotted string ``"1.2.840.113549.1.1.10"``. This is
         signed by an RSA key using the Probabilistic Signature Scheme (PSS)
-        padding from RFC 4055. The hash function and padding are defined by
+        padding from :rfc:`4055`. The hash function and padding are defined by
         signature algorithm parameters.
 
     .. attribute:: ECDSA_WITH_SHA1