1 files changed, 11 insertions, 11 deletions
diff --git a/man2/mprotect.2 b/man2/mprotect.2
index 63781f536..309de1ff6 100644
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@@ -60,7 +60,7 @@ The memory can be executed.
 .BR PROT_SEM " (since Linux 2.5.7)"
 The memory can be used for atomic operations.
 This flag was introduced as part of the
-.BR futex (2)
+.MR futex 2
 implementation (in order to guarantee the ability to perform atomic
 operations required by commands such as
 .BR FUTEX_WAIT ),
@@ -111,14 +111,14 @@ and
 The
 .I pkey
 argument specifies the protection key (see
-.BR pkeys (7))
+.MR pkeys 7 )
 to assign to the memory.
 The protection key must be allocated with
-.BR pkey_alloc (2)
+.MR pkey_alloc 2
 before it is passed to
 .BR pkey_mprotect ().
 For an example of the use of this system call, see
-.BR pkeys (7).
+.MR pkeys 7 .
 .SH RETURN VALUE
 On success,
 .BR mprotect ()
@@ -133,7 +133,7 @@ is set to indicate the error.
 .B EACCES
 The memory cannot be given the specified access.
 This can happen, for example, if you
-.BR mmap (2)
+.MR mmap 2
 a file to which you have read-only access, then ask
 .BR mprotect ()
 to mark it
@@ -146,7 +146,7 @@ or not a multiple of the system page size.
 .B EINVAL
 .RB ( pkey_mprotect ())
 \fIpkey\fP has not been allocated with
-.BR pkey_alloc (2)
+.MR pkey_alloc 2
 .TP
 .B EINVAL
 Both
@@ -198,7 +198,7 @@ POSIX says that the behavior of
 .BR mprotect ()
 is unspecified if it is applied to a region of memory that
 was not obtained via
-.BR mmap (2).
+.MR mmap 2 .
 .P
 On Linux, it is always permissible to call
 .BR mprotect ()
@@ -215,7 +215,7 @@ depends on processor architecture, kernel version, and process state.
 If
 .B READ_IMPLIES_EXEC
 is set in the process's personality flags (see
-.BR personality (2)),
+.MR personality 2 ),
 specifying
 .B PROT_READ
 will implicitly add
@@ -358,6 +358,6 @@ main(void)
 .EE
 .\" SRC END
 .SH SEE ALSO
-.BR mmap (2),
-.BR sysconf (3),
-.BR pkeys (7)
+.MR mmap 2 ,
+.MR sysconf 3 ,
+.MR pkeys 7