1 files changed, 24 insertions, 24 deletions
diff --git a/man5/passwd.5 b/man5/passwd.5
index 24164cb73..b4c9cb697 100644
--- a/man5/passwd.5
+++ b/man5/passwd.5
@@ -16,7 +16,7 @@ The
 .I /etc/passwd
 file is a text file that describes user login accounts for the system.
 It should have read permission allowed for all users (many utilities, like
-.BR ls (1)
+.MR ls 1
 use it to map user IDs to usernames), but write access only for the
 superuser.
 .P
@@ -43,7 +43,7 @@ or configurable (for example using the
 or
 .RB \[dq] nonull \[dq]
 arguments to
-.BR pam_unix (8)).
+.MR pam_unix 8 ).
 .P
 If the encrypted password in
 .I /etc/passwd
@@ -58,7 +58,7 @@ password.
 .P
 If you create a new login, first put an asterisk (*) in the password field,
 then use
-.BR passwd (1)
+.MR passwd 1
 to set it.
 .P
 Each line of the file describes a single user,
@@ -80,7 +80,7 @@ It should not contain capital letters.
 This is either the encrypted user password,
 an asterisk (*), or the letter \[aq]x\[aq].
 (See
-.BR pwconv (8)
+.MR pwconv 8
 for an explanation of \[aq]x\[aq].)
 .TP
 .I UID
@@ -91,14 +91,14 @@ login account (superuser) has the user ID 0.
 .I GID
 This is the numeric primary group ID for this user.
 (Additional groups for the user are defined in the system group file; see
-.BR group (5)).
+.MR group 5 ).
 .TP
 .I GECOS
 This field (sometimes called the "comment field")
 is optional and used only for informational purposes.
 Usually, it contains the full username.
 Some programs (for example,
-.BR finger (1))
+.MR finger 1 )
 display information from this field.
 .IP
 GECOS stands for "General Electric Comprehensive Operating System",
@@ -122,7 +122,7 @@ This is the program to run at login (if empty, use
 .IR /bin/sh ).
 If set to a nonexistent executable, the user will be unable to login
 through
-.BR login (1).
+.MR login 1 .
 The value in this field is used to set the
 .B SHELL
 environment variable.
@@ -135,26 +135,26 @@ or no group will exist.
 .P
 If the encrypted password is set to an asterisk (*), the user will be unable
 to login using
-.BR login (1),
+.MR login 1 ,
 but may still login using
-.BR rlogin (1),
+.MR rlogin 1 ,
 run existing processes and initiate new ones through
-.BR rsh (1),
-.BR cron (8),
-.BR at (1),
+.MR rsh 1 ,
+.MR cron 8 ,
+.MR at 1 ,
 or mail filters, etc.
 Trying to lock an account by simply changing the
 shell field yields the same result and additionally allows the use of
-.BR su (1).
+.MR su 1 .
 .SH SEE ALSO
-.BR chfn (1),
-.BR chsh (1),
-.BR login (1),
-.BR passwd (1),
-.BR su (1),
-.BR crypt (3),
-.BR getpwent (3),
-.BR getpwnam (3),
-.BR group (5),
-.BR shadow (5),
-.BR vipw (8)
+.MR chfn 1 ,
+.MR chsh 1 ,
+.MR login 1 ,
+.MR passwd 1 ,
+.MR su 1 ,
+.MR crypt 3 ,
+.MR getpwent 3 ,
+.MR getpwnam 3 ,
+.MR group 5 ,
+.MR shadow 5 ,
+.MR vipw 8