1 files changed, 24 insertions, 24 deletions
diff --git a/man2/openat2.2 b/man2/openat2.2
index 4b9029a6b..c9afb5e11 100644
--- a/man2/openat2.2
+++ b/man2/openat2.2
@@ -23,12 +23,12 @@ Standard C library
 glibc provides no wrapper for
 .BR openat2 (),
 necessitating the use of
-.BR syscall (2).
+.MR syscall 2 .
 .SH DESCRIPTION
 The
 .BR openat2 ()
 system call is an extension of
-.BR openat (2)
+.MR openat 2
 and provides a superset of its functionality.
 .P
 The
@@ -42,7 +42,7 @@ is specified in
 be created.
 .P
 As with
-.BR openat (2),
+.MR openat 2 ,
 if
 .I pathname
 is a relative pathname, then it is interpreted relative to the
@@ -84,12 +84,12 @@ should be opened, and acts as a superset of the
 and
 .I mode
 arguments to
-.BR openat (2).
+.MR openat 2 .
 This argument is a pointer to an
 .I open_how
 structure,
 described in
-.BR open_how (2type).
+.MR open_how 2type .
 .P
 Any future extensions to
 .BR openat2 ()
@@ -116,13 +116,13 @@ the file creation and file status flags to use when opening the file.
 All of the
 .B O_*
 flags defined for
-.BR openat (2)
+.MR openat 2
 are valid
 .BR openat2 ()
 flag values.
 .IP
 Whereas
-.BR openat (2)
+.MR openat 2
 ignores unknown bits in its
 .I flags
 argument,
@@ -135,10 +135,10 @@ This field specifies the
 mode for the new file, with identical semantics to the
 .I mode
 argument of
-.BR openat (2).
+.MR openat 2 .
 .IP
 Whereas
-.BR openat (2)
+.MR openat 2
 ignores bits other than those in the range
 .I 07777
 in its
@@ -167,7 +167,7 @@ components of
 .I pathname
 will be resolved.
 (See
-.BR path_resolution (7)
+.MR path_resolution 7
 for background information.)
 .IP
 The primary use case for these flags is to allow trusted programs to restrict
@@ -218,12 +218,12 @@ is an absolute path, it is also interpreted relative to
 .IR dirfd .
 .IP
 The effect of this flag is as though the calling process had used
-.BR chroot (2)
+.MR chroot 2
 to (temporarily) modify its root directory (to the directory
 referred to by
 .IR dirfd ).
 However, unlike
-.BR chroot (2)
+.MR chroot 2
 (which changes the filesystem root permanently for a process),
 .B RESOLVE_IN_ROOT
 allows a program to efficiently restrict path resolution on a per-open basis.
@@ -239,13 +239,13 @@ the caller should explicitly specify
 Disallow all magic-link resolution during path resolution.
 .IP
 Magic links are symbolic link-like objects that are most notably found in
-.BR proc (5);
+.MR proc 5 ;
 examples include
 .IR /proc/ pid /exe
 and
 .IR /proc/ pid /fd/* .
 (See
-.BR symlink (7)
+.MR symlink 7
 for more details.)
 .IP
 Unknowingly opening magic links can be risky for some applications.
@@ -254,7 +254,7 @@ Examples of such risks include the following:
 .IP \[bu] 3
 If the process opening a pathname is a controlling process that
 currently has no controlling terminal (see
-.BR credentials (7)),
+.MR credentials 7 ),
 then opening a magic link inside
 .IR /proc/ pid /fd
 that happens to refer to a terminal
@@ -392,7 +392,7 @@ is set to indicate the error.
 The set of errors returned by
 .BR openat2 ()
 includes all of the errors returned by
-.BR openat (2),
+.MR openat 2 ,
 as well as the following additional errors:
 .TP
 .B E2BIG
@@ -491,10 +491,10 @@ acting as an implicit version number.
 (Because new extension fields will always
 be appended, the structure size will always increase.)
 This extensibility design is very similar to other system calls such as
-.BR sched_setattr (2),
-.BR perf_event_open (2),
+.MR sched_setattr 2 ,
+.MR perf_event_open 2 ,
 and
-.BR clone3 (2).
+.MR clone3 2 .
 .P
 If we let
 .I usize
@@ -557,7 +557,7 @@ struct open_how how = { .flags = O_RDWR,
 .in
 .P
 or explicitly using
-.BR memset (3)
+.MR memset 3
 or similar:
 .P
 .in +4n
@@ -576,7 +576,7 @@ with a structure which has every byte nonzero (to find the largest value
 which doesn't produce an error of
 .BR E2BIG ).
 .SH SEE ALSO
-.BR openat (2),
-.BR open_how (2type),
-.BR path_resolution (7),
-.BR symlink (7)
+.MR openat 2 ,
+.MR open_how 2type ,
+.MR path_resolution 7 ,
+.MR symlink 7