1 files changed, 16 insertions, 16 deletions
diff --git a/man2/shmget.2 b/man2/shmget.2
index 96c2e6108..5b636e520 100644
--- a/man2/shmget.2
+++ b/man2/shmget.2
@@ -77,7 +77,7 @@ set to
 (This is analogous to the effect of the combination
 .B O_CREAT | O_EXCL
 for
-.BR open (2).)
+.MR open 2 .)
 .P
 The value
 .I shmflg
@@ -125,11 +125,11 @@ Thus, the above two constants are defined as:
 .IP
 For some additional details,
 see the discussion of the similarly named constants in
-.BR mmap (2).
+.MR mmap 2 .
 .TP
 .BR SHM_NORESERVE " (since Linux 2.6.15)"
 This flag serves the same purpose as the
-.BR mmap (2)
+.MR mmap 2
 .B MAP_NORESERVE
 flag.
 Do not reserve swap space for this segment.
@@ -142,7 +142,7 @@ if no physical memory is available.
 See also the discussion of the file
 .I /proc/sys/vm/overcommit_memory
 in
-.BR proc (5).
+.MR proc 5 .
 .\" As at 2.6.17-rc2, this flag has no effect if SHM_HUGETLB was also
 .\" specified.
 .P
@@ -153,7 +153,7 @@ These bits have the same format, and the same
 meaning, as the
 .I mode
 argument of
-.BR open (2).
+.MR open 2 .
 Presently, execute permissions are not used by the system.
 .P
 When a new shared memory segment is created,
@@ -161,7 +161,7 @@ its contents are initialized to zero values, and
 its associated data structure,
 .I shmid_ds
 (see
-.BR shmctl (2)),
+.MR shmctl 2 ),
 is initialized as follows:
 .IP \[bu] 3
 .I shm_perm.cuid
@@ -262,7 +262,7 @@ and is not a member of the
 group; see the description of
 .I /proc/sys/vm/sysctl_hugetlb_shm_group
 in
-.BR proc (5).
+.MR proc 5 .
 .SH STANDARDS
 POSIX.1-2008.
 .P
@@ -400,13 +400,13 @@ was perhaps unfortunate,
 would more clearly show its function.
 .SH EXAMPLES
 See
-.BR shmop (2).
+.MR shmop 2 .
 .SH SEE ALSO
-.BR memfd_create (2),
-.BR shmat (2),
-.BR shmctl (2),
-.BR shmdt (2),
-.BR ftok (3),
-.BR capabilities (7),
-.BR shm_overview (7),
-.BR sysvipc (7)
+.MR memfd_create 2 ,
+.MR shmat 2 ,
+.MR shmctl 2 ,
+.MR shmdt 2 ,
+.MR ftok 3 ,
+.MR capabilities 7 ,
+.MR shm_overview 7 ,
+.MR sysvipc 7