Anywhere we tell someone to randomly generate something, link the RNG docs. Fixes #1559

1 files changed, 7 insertions, 7 deletions

diff --git a/docs/hazmat/primitives/twofactor.rst b/docs/hazmat/primitives/twofactor.rst
index f19cf0e6..0d86f7cc 100644
--- a/docs/hazmat/primitives/twofactor.rst
+++ b/docs/hazmat/primitives/twofactor.rst
@@ -18,9 +18,9 @@ codes (HMAC).
     .. versionadded:: 0.3
 
     HOTP objects take a ``key``, ``length`` and ``algorithm`` parameter. The
-    ``key`` should be randomly generated bytes and is recommended to be 160
-    bits in length. The ``length`` parameter controls the length of the
-    generated one time password and must be >= 6 and <= 8.
+    ``key`` should be :doc:`randomly generated bytes </random-numbers>` and is
+    recommended to be 160 bits in length. The ``length`` parameter controls the
+    length of the generated one time password and must be >= 6 and <= 8.
 
     This is an implementation of :rfc:`4226`.
 
@@ -113,10 +113,10 @@ similar to the following code.
 .. class:: TOTP(key, length, algorithm, time_step, backend)
 
     TOTP objects take a ``key``, ``length``, ``algorithm`` and ``time_step``
-    parameter. The ``key`` should be randomly generated bytes and is recommended
-    to be as long as your hash function's output (e.g 256-bit for SHA256).
-    The ``length`` parameter controls the length of the generated one time
-    password and must be >= 6 and <= 8.
+    parameter. The ``key`` should be :doc:`randomly generated bytes
+    </random-numbers>` and is recommended to be as long as your hash function's
+    output (e.g 256-bit for SHA256). The ``length`` parameter controls the
+    length of the generated one time password and must be >= 6 and <= 8.
 
     This is an implementation of :rfc:`6238`.