1 files changed, 13 insertions, 13 deletions
diff --git a/man7/random.7 b/man7/random.7
index 5062b1900..76a2debe0 100644
--- a/man7/random.7
+++ b/man7/random.7
@@ -25,12 +25,12 @@ The
 and
 .I /dev/random
 devices, both described in
-.BR random (4).
+.MR random 4 .
 These devices have been present on Linux since early times,
 and are also available on many other systems.
 .IP \[bu]
 The Linux-specific
-.BR getrandom (2)
+.MR getrandom 2
 system call, available since Linux 3.17.
 This system call provides access either to the same source as
 .I /dev/urandom
@@ -50,9 +50,9 @@ source is selected by specifying the
 .B GRND_RANDOM
 flag to the system call.
 (The
-.BR getentropy (3)
+.MR getentropy 3
 function provides a slightly more portable interface on top of
-.BR getrandom (2).)
+.MR getrandom 2 .)
 .\"
 .SS Initialization of the entropy pool
 The kernel collects bits of entropy from the environment.
@@ -63,14 +63,14 @@ Unless you are doing long-term key generation (and most likely not even
 then), you probably shouldn't be reading from the
 .I /dev/random
 device or employing
-.BR getrandom (2)
+.MR getrandom 2
 with the
 .B GRND_RANDOM
 flag.
 Instead, either read from the
 .I /dev/urandom
 device or employ
-.BR getrandom (2)
+.MR getrandom 2
 without the
 .B GRND_RANDOM
 flag.
@@ -105,7 +105,7 @@ The following table summarizes the behavior of the various
 interfaces that can be used to obtain randomness.
 .B GRND_NONBLOCK
 is a flag that can be used to control the blocking behavior of
-.BR getrandom (2).
+.MR getrandom 2 .
 The final column of the table considers the case that can occur
 in early boot time when the entropy pool is not yet initialized.
 .ad l
@@ -205,9 +205,9 @@ than one minute), that should be taken as a sign that its cryptography is
 skillfully implemented.
 .\"
 .SH SEE ALSO
-.BR getrandom (2),
-.BR getauxval (3),
-.BR getentropy (3),
-.BR random (4),
-.BR urandom (4),
-.BR signal (7)
+.MR getrandom 2 ,
+.MR getauxval 3 ,
+.MR getentropy 3 ,
+.MR random 4 ,
+.MR urandom 4 ,
+.MR signal 7