1 files changed, 37 insertions, 37 deletions
diff --git a/man2/mount.2 b/man2/mount.2
index d8a691e13..7dc2bda36 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -60,7 +60,7 @@ argument is interpreted by the different filesystems.
 Typically it is a string of comma-separated options
 understood by this filesystem.
 See
-.BR mount (8)
+.MR mount 8
 for details of the options available for each filesystem type.
 This argument may be specified as NULL, if there are no options.
 .P
@@ -124,7 +124,7 @@ as described later in this page.
 Make directory changes on this filesystem synchronous.
 (This property can be obtained for individual directories
 or subtrees using
-.BR chattr (1).)
+.MR chattr 1 .)
 .TP
 .BR MS_LAZYTIME " (since Linux 4.0)"
 .\" commit 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8
@@ -138,10 +138,10 @@ The on-disk timestamps are updated only when:
 the inode needs to be updated for some change unrelated to file timestamps;
 .IP \[bu]
 the application employs
-.BR fsync (2),
-.BR syncfs (2),
+.MR fsync 2 ,
+.MR syncfs 2 ,
 or
-.BR sync (2);
+.MR sync 2 ;
 .IP \[bu]
 an undeleted inode is evicted from memory; or
 .IP \[bu]
@@ -163,7 +163,7 @@ mount option is also enabled.
 and
 .B MS_LAZYTIME
 is that
-.BR stat (2)
+.MR stat 2
 will return the correctly updated atime, but the atime updates
 will be flushed to disk only in the cases listed above.)
 .TP
@@ -171,7 +171,7 @@ will be flushed to disk only in the cases listed above.)
 Permit mandatory locking on files in this filesystem.
 (Mandatory locking must still be enabled on a per-file basis,
 as described in
-.BR fcntl (2).)
+.MR fcntl 2 .)
 Since Linux 4.5,
 .\" commit 95ace75414f312f9a7b93d873f386987b92a5301
 this mount option requires the
@@ -232,7 +232,7 @@ update the file's last access time (atime) only if the current value
 of atime is less than or equal to the file's last modification time (mtime)
 or last status change time (ctime).
 This option is useful for programs, such as
-.BR mutt (1),
+.MR mutt 1 ,
 that need to know when a file has been read since it was last modified.
 Since Linux 2.6.30, the kernel defaults to the behavior provided
 by this flag (unless
@@ -270,7 +270,7 @@ Make writes on this filesystem synchronous (as though
 the
 .B O_SYNC
 flag to
-.BR open (2)
+.MR open 2
 was specified for all file opens to this filesystem).
 .TP
 .BR MS_NOSYMFOLLOW " (since Linux 5.10)"
@@ -278,11 +278,11 @@ was specified for all file opens to this filesystem).
 Do not follow symbolic links when resolving paths.
 Symbolic links can still be created,
 and
-.BR readlink (1),
-.BR readlink (2),
-.BR realpath (1),
+.MR readlink 1 ,
+.MR readlink 2 ,
+.MR realpath 1 ,
 and
-.BR realpath (3)
+.MR realpath 3
 all still work properly.
 .P
 From Linux 2.4 onward, some of the above flags are
@@ -445,7 +445,7 @@ then perform a bind mount.
 A bind mount makes a file or a directory subtree visible at
 another point within the single directory hierarchy.
 Bind mounts may cross filesystem boundaries and span
-.BR chroot (2)
+.MR chroot 2
 jails.
 .P
 The
@@ -564,7 +564,7 @@ is also changed.
 .P
 For further details regarding mount propagation types
 (including the default propagation type assigned to new mounts), see
-.BR mount_namespaces (7).
+.MR mount_namespaces 7 .
 .\"
 .SS Moving a mount
 If
@@ -630,7 +630,7 @@ See the Linux kernel source code for details.
 .B EACCES
 A component of a path was not searchable.
 (See also
-.BR path_resolution (7).)
+.MR path_resolution 7 .)
 .TP
 .B EACCES
 Mounting a read-only filesystem was attempted without giving the
@@ -822,7 +822,7 @@ flag, or one of the "atime" flags
 .BR MS_NODIRATIME ,
 .BR MS_RELATIME )
 of an existing mount, but the mount is locked; see
-.BR mount_namespaces (7).
+.MR mount_namespaces 7 .
 .TP
 .B EROFS
 Mounting a read-only filesystem was attempted without giving the
@@ -896,22 +896,22 @@ are visible to all other processes sharing the same namespace.
 a single namespace was shared by every process on the system.)
 .P
 A child process created by
-.BR fork (2)
+.MR fork 2
 shares its parent's mount namespace;
 the mount namespace is preserved across an
-.BR execve (2).
+.MR execve 2 .
 .P
 A process can obtain a private mount namespace if:
 it was created using the
-.BR clone (2)
+.MR clone 2
 .B CLONE_NEWNS
 flag,
 in which case its new namespace is initialized to be a
 .I copy
 of the namespace of the process that called
-.BR clone (2);
+.MR clone 2 ;
 or it calls
-.BR unshare (2)
+.MR unshare 2
 with the
 .B CLONE_NEWNS
 flag,
@@ -922,7 +922,7 @@ to other processes (except child processes that the caller
 subsequently creates) and vice versa.
 .P
 For further details on mount namespaces, see
-.BR mount_namespaces (7).
+.MR mount_namespaces 7 .
 .\"
 .SS Parental relationship between mounts
 Each mount has a parent mount.
@@ -952,20 +952,20 @@ file exposes even more information about mounts,
 including the propagation type and mount ID information that makes it
 possible to discover the parental relationship between mounts.
 See
-.BR proc (5)
+.MR proc 5
 and
-.BR mount_namespaces (7)
+.MR mount_namespaces 7
 for details of this file.
 .SH SEE ALSO
-.BR mountpoint (1),
-.BR chroot (2),
-.BR ioctl_iflags (2),
-.BR mount_setattr (2),
-.BR pivot_root (2),
-.BR umount (2),
-.BR mount_namespaces (7),
-.BR path_resolution (7),
-.BR findmnt (8),
-.BR lsblk (8),
-.BR mount (8),
-.BR umount (8)
+.MR mountpoint 1 ,
+.MR chroot 2 ,
+.MR ioctl_iflags 2 ,
+.MR mount_setattr 2 ,
+.MR pivot_root 2 ,
+.MR umount 2 ,
+.MR mount_namespaces 7 ,
+.MR path_resolution 7 ,
+.MR findmnt 8 ,
+.MR lsblk 8 ,
+.MR mount 8 ,
+.MR umount 8