access.2, chmod.2, chown.2, link.2, mkdir.2, open.2, readlink.2, rename.2, stat.2, symlink.2, unlink.2, mkfifo.3, scandir.3: Minor fix: remove section numbers in references to functions inside page

With the page merges, we now have some references to functions
within the page that have section numbers. Remove those.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/access.2

@@ -115,7 +115,7 @@ is enabled for any of the file owner, group, or other.
 The
 .BR faccessat ()
 system call operates in exactly the same way as
-.BR access (2),
+.BR access (),
 except for the differences described here.
 
 If the pathname given in
@@ -125,7 +125,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR access (2)
+.BR access()
 for a relative pathname).
 
 If
@@ -138,7 +138,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR access (2)).
+.BR access()).
 
 If
 .I pathname
@@ -154,7 +154,7 @@ Perform access checks using the effective user and group IDs.
 By default,
 .BR faccessat ()
 uses the real IDs (like
-.BR access (2)).
+.BR access()).
 .TP
 .B AT_SYMLINK_NOFOLLOW
 If
@@ -260,10 +260,10 @@ is a file descriptor referring to a file other than a directory.
 was added to Linux in kernel 2.6.16;
 library support was added to glibc in version 2.4.
 .SH "CONFORMING TO"
-.BR access (2):
+.BR access():
 SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008.
 
-.BR faccessat (2):
+.BR faccessat ():
 POSIX.1-2008.
 .SH NOTES
 .PP

man2/chmod.2

@@ -183,7 +183,7 @@ delayed for other clients if attribute caching is enabled on them.
 The
 .BR fchmodat ()
 system call operates in exactly the same way as
-.BR chmod (2),
+.BR chmod (),
 except for the differences described here.
 
 If the pathname given in
@@ -193,7 +193,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR chmod (2)
+.BR chmod()
 for a relative pathname).
 
 If
@@ -206,7 +206,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR chmod (2)).
+.BR chmod()).
 
 If
 .I pathname
@@ -298,7 +298,7 @@ See above.
 See above.
 .PP
 The same errors that occur for
-.BR chmod (2)
+.BR chmod()
 can also occur for
 .BR fchmodat ().
 The following additional errors can occur for

man2/chown.2

@@ -146,7 +146,7 @@ bit indicates mandatory locking, and is not cleared by a
 The
 .BR fchownat ()
 system call operates in exactly the same way as
-.BR chown (2),
+.BR chown (),
 except for the differences described here.
 
 If the pathname given in
@@ -156,7 +156,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR chown (2)
+.BR chown()
 for a relative pathname).
 
 If
@@ -169,7 +169,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR chown (2)).
+.BR chown()).
 
 If
 .I pathname
@@ -206,11 +206,11 @@ If
 .I pathname
 is a symbolic link, do not dereference it:
 instead operate on the link itself, like
-.BR lchown (2).
+.BR lchown().
 (By default,
 .BR fchownat ()
 dereferences symbolic links, like
-.BR chown (2).)
+.BR chown().)
 .PP
 See
 .BR openat (2)
@@ -282,7 +282,7 @@ See above.
 See above.
 .PP
 The same errors that occur for
-.BR chown (2)
+.BR chown()
 can also occur for
 .BR fchownat ().
 The following additional errors can occur for

man2/link.2

@@ -81,7 +81,7 @@ and ownership) and it is impossible to tell which name was the
 The
 .BR linkat ()
 system call operates in exactly the same way as
-.BR link (2),
+.BR link (),
 except for the differences described here.
 
 If the pathname given in
@@ -91,7 +91,7 @@ referred to by the file descriptor
 .I olddirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR link (2)
+.BR link ()
 for a relative pathname).
 
 If
@@ -104,7 +104,7 @@ then
 .I oldpath
 is interpreted relative to the current working
 directory of the calling process (like
-.BR link (2)).
+.BR link ()).
 
 If
 .I oldpath
@@ -156,7 +156,7 @@ By default,
 does not dereference
 .I oldpath
 if it is a symbolic link (like
-.BR link (2)).
+.BR link ()).
 The flag
 .B AT_SYMLINK_FOLLOW
 can be specified in

man2/mkdir.2

@@ -77,7 +77,7 @@ newly created directory.
 The
 .BR mkdirat ()
 system call operates in exactly the same way as
-.BR mkdir (2),
+.BR mkdir (),
 except for the differences described here.
 
 If the pathname given in
@@ -87,7 +87,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR mkdir (2)
+.BR mkdir ()
 for a relative pathname).
 
 If
@@ -100,7 +100,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR mkdir (2)).
+.BR mkdir ()).
 
 If
 .I pathname

man2/open.2

@@ -687,7 +687,7 @@ equal to
 The
 .BR openat ()
 system call operates in exactly the same way as
-.BR open (2),
+.BR open (),
 except for the differences described here.
 
 If the pathname given in
@@ -697,7 +697,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR open (2)
+.BR open ()
 for a relative pathname).
 
 If
@@ -710,7 +710,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR open (2)).
+.BR open ()).
 
 If
 .I pathname
@@ -1138,13 +1138,13 @@ First,
 .BR openat ()
 allows an application to avoid race conditions that could
 occur when using
-.BR open (2)
+.BR open ()
 to open files in directories other than the current working directory.
 These race conditions result from the fact that some component
 of the directory prefix given to
-.BR open (2)
+.BR open ()
 could be changed in parallel with the call to
-.BR open (2).
+.BR open ().
 Such races can be avoided by
 opening a file descriptor for the target directory,
 and then specifying that file descriptor as the

man2/readlink.2

@@ -101,7 +101,7 @@ characters), in case the buffer is too small to hold all of the contents.
 The
 .BR readlinkat ()
 system call operates in exactly the same way as
-.BR readlink (2),
+.BR readlink (),
 except for the differences described here.
 
 If the pathname given in
@@ -111,7 +111,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR readlink (2)
+.BR readlink ()
 for a relative pathname).
 
 If
@@ -124,7 +124,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR readlink (2)).
+.BR readlink ()).
 
 If
 .I pathname

man2/rename.2

@@ -120,7 +120,7 @@ refers to a symbolic link, the link will be overwritten.
 The
 .BR renameat ()
 system call operates in exactly the same way as
-.BR rename (2),
+.BR rename (),
 except for the differences described here.
 
 If the pathname given in
@@ -130,7 +130,7 @@ referred to by the file descriptor
 .I olddirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR rename (2)
+.BR rename ()
 for a relative pathname).
 
 If
@@ -143,7 +143,7 @@ then
 .I oldpath
 is interpreted relative to the current working
 directory of the calling process (like
-.BR rename (2)).
+.BR rename ()).
 
 If
 .I oldpath

man2/stat.2

@@ -338,7 +338,7 @@ process.
 The
 .BR fstatat ()
 system call operates in exactly the same way as
-.BR stat (2),
+.BR stat (),
 except for the differences described here.
 
 If the pathname given in
@@ -348,7 +348,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR stat (2)
+.BR stat ()
 for a relative pathname).
 
 If
@@ -361,7 +361,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR stat (2)).
+.BR stat ()).
 
 If
 .I pathname
@@ -411,11 +411,11 @@ If
 .I pathname
 is a symbolic link, do not dereference it:
 instead return information about the link itself, like
-.BR lstat (2).
+.BR lstat ().
 (By default,
 .BR fstatat ()
 dereferences symbolic links, like
-.BR stat (2).)
+.BR stat ().)
 .PP
 See
 .BR openat (2)

man2/symlink.2

@@ -107,7 +107,7 @@ be overwritten.
 The
 .BR symlinkat ()
 system call operates in exactly the same way as
-.BR symlink (2),
+.BR symlink (),
 except for the differences described here.
 
 If the pathname given in
@@ -117,7 +117,7 @@ referred to by the file descriptor
 .I newdirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR symlink (2)
+.BR symlink ()
 for a relative pathname).
 
 If
@@ -130,7 +130,7 @@ then
 .I linkpath
 is interpreted relative to the current working
 directory of the calling process (like
-.BR symlink (2)).
+.BR symlink ()).
 
 If
 .I linkpath

man2/unlink.2

@@ -83,7 +83,7 @@ it.
 The
 .BR unlinkat ()
 system call operates in exactly the same way as either
-.BR unlink (2)
+.BR unlink()
 or
 .BR rmdir (2)
 (depending on whether or not
@@ -100,7 +100,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR unlink (2)
+.BR unlink()
 and
 .BR rmdir (2)
 for a relative pathname).
@@ -115,7 +115,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR unlink (2)
+.BR unlink()
 and
 .BR rmdir (2)).
 
@@ -135,7 +135,7 @@ Currently only one such flag is defined:
 By default,
 .BR unlinkat ()
 performs the equivalent of
-.BR unlink (2)
+.BR unlink()
 on
 .IR pathname .
 If the
@@ -238,7 +238,7 @@ capability).
 refers to a file on a read-only filesystem.
 .PP
 The same errors that occur for
-.BR unlink (2)
+.BR unlink()
 and
 .BR rmdir (2)
 can also occur for

man3/mkfifo.3

@@ -87,7 +87,7 @@ for nonblocking handling of FIFO special files.
 The
 .BR mkfifoat ()
 function operates in exactly the same way as
-.BR mkfifo (3),
+.BR mkfifo (),
 except for the differences described here.
 
 If the pathname given in
@@ -97,7 +97,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR mkfifo (3)
+.BR mkfifo ()
 for a relative pathname).
 
 If
@@ -110,7 +110,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR mkfifo (3)).
+.BR mkfifo ()).
 
 If
 .I pathname

man3/scandir.3

@@ -146,7 +146,7 @@ on the strings \fI(*a)\->d_name\fP and \fI(*b)\->d_name\fP.
 The
 .BR scandirat ()
 function operates in exactly the same way as
-.BR scandir (3),
+.BR scnadir (),
 except for the differences described here.
 
 If the pathname given in
@@ -156,7 +156,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR scandir (3)
+.BR scnadir ()
 for a relative pathname).
 
 If
@@ -169,7 +169,7 @@ then
 .I dirp
 is interpreted relative to the current working
 directory of the calling process (like
-.BR scandir (3)).
+.BR scnadir ()).
 
 If
 .I dirp