getrusage.2, madvise.2, memfd_create.2, mlock.2, mount.2, getauxval.3, core.5, capabilities.7, pid_namespaces.7, symlink.7, user_namespaces.7: Consistently use /proc/[pid] (not /proc/PID)

Reported-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/getrusage.2

@@ -260,7 +260,7 @@ All new applications should be written using
 .BR getrusage ().
 
 See also the description of
-.IR /proc/PID/stat
+.IR /proc/[pid]/stat
 in
 .BR proc (5).
 .SH SEE ALSO

man2/madvise.2

@@ -363,7 +363,7 @@ that are known not to be useful in a core dump.
 The effect of
 .BR MADV_DONTDUMP
 takes precedence over the bit mask that is set via the
-.I /proc/PID/coredump_filter
+.I /proc/[pid]/coredump_filter
 file (see
 .BR core (5)).
 .TP

man2/memfd_create.2

@@ -339,11 +339,11 @@ From another program, we can obtain a file descriptor for the
 file created by
 .BR memfd_create ()
 by opening the
-.IR /proc/PID/fd
+.IR /proc/[pid]/fd
 file that corresponds to the file descriptor opened by
 .BR memfd_create ().
 Using that pathname, we inspect the content of the
-.IR /proc/PID/fd
+.IR /proc/[pid]/fd
 symbolic link, and use our
 .I t_get_seals
 program to view the seals that have been placed on the file:

man2/mlock.2

@@ -421,7 +421,7 @@ is page aligned, so portable applications should ensure this.
 The
 .I VmLck
 field of the Linux-specific
-.I /proc/PID/status
+.I /proc/[pid]/status
 file shows how many kilobytes of memory the process with ID
 .I PID
 has locked using

man2/mount.2

@@ -775,7 +775,7 @@ to other processes (except child processes that the caller
 subsequently creates) and vice versa.
 
 The Linux-specific
-.I /proc/PID/mounts
+.I /proc/[pid]/mounts
 file exposes the list of mount points in the mount
 namespace of the process with the specified ID; see
 .BR proc (5)

man3/getauxval.3

@@ -230,7 +230,7 @@ environment variable when running a program:
 
 The auxiliary vector of any process can (subject to file permissions)
 be obtained via
-.IR /proc/PID/auxv ;
+.IR /proc/[pid]/auxv ;
 see
 .BR proc (5)
 for more information.

man5/core.5

@@ -287,12 +287,12 @@ in an argument.
 When collecting core dumps via a pipe to a user-space program,
 it can be useful for the collecting program to gather data about
 the crashing process from that process's
-.IR /proc/PID
+.IR /proc/[pid]
 directory.
 In order to do this safely,
 the kernel must wait for the program collecting the core dump to exit,
 so as not to remove the crashing process's
-.IR /proc/PID
+.IR /proc/[pid]
 files prematurely.
 This in turn creates the
 possibility that a misbehaving collecting program can block
@@ -317,7 +317,7 @@ The default value for this file is 0.
 .\"
 .SS Controlling which mappings are written to the core dump
 Since kernel 2.6.23, the Linux-specific
-.IR /proc/PID/coredump_filter
+.IR /proc/[pid]/coredump_filter
 file can be used to control which memory segments are written to the
 core dump file in the event that a core dump is performed for the
 process with the corresponding process ID.

man7/capabilities.7

@@ -612,7 +612,7 @@ employ
 operation;
 .IP *
 set
-.IR /proc/PID/oom_score_adj
+.IR /proc/[pid]/oom_score_adj
 to a value lower than the value last set by a process with
 .BR CAP_SYS_RESOURCE .
 .RE
@@ -1226,10 +1226,10 @@ and could be enabled/disabled via the
 kernel configuration option.
 
 The
-.I /proc/PID/task/TID/status
+.I /proc/[pid]/task/TID/status
 file can be used to view the capability sets of a thread.
 The
-.I /proc/PID/status
+.I /proc/[pid]/status
 file shows the capability sets of a process's main thread.
 Before Linux 3.8, nonexistent capabilities were shown as being
 enabled (1) in these sets.

man7/pid_namespaces.7

@@ -298,7 +298,7 @@ Thus, call sequences such as the following will fail (with the error
 A
 .I /proc
 filesystem shows (in the
-.I /proc/PID
+.I /proc/[pid]
 directories) only processes visible in the PID namespace
 of the process that performed the mount, even if the
 .I /proc

man7/symlink.7

@@ -107,7 +107,7 @@ and can't be changed.
 (Note that there are some "magic" symbolic links in the
 .I /proc
 directory tree\(emfor example, the
-.IR /proc/PID/fd/*
+.IR /proc/[pid]/fd/*
 files\(emthat have different permissions.)
 .\"
 .\" The

man7/user_namespaces.7

@@ -882,7 +882,7 @@ and the System V IPC "ctl"
 .B IPC_STAT
 operations,
 credentials exposed by
-.IR /proc/PID/status
+.IR /proc/[pid]/status
 and the files in
 .IR /proc/sysvipc/* ,
 credentials returned via the