[PATCH v2] capget.2, execve.2, readv.2, socketpair.2, utime.2, utimensat.2, getloadavg.3, proc.5, mount_namespaces.7, unix.7: ffix

[Alejandro Colomar <alx.manpages@gmail.com>]

{.IR var [x]} -> {.I var[x]}

There were around 15 entries of the former,
and around 360 of the latter.

Found using:
$ grep -rn '^\.I[ |R].* \[.*\]' |sort

Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man2/capget.2     | 6 +++---
 man2/execve.2     | 2 +-
 man2/readv.2      | 8 ++++----
 man2/socketpair.2 | 4 ++--
 man2/utime.2      | 4 ++--
 man2/utimensat.2  | 4 ++--
 man3/getloadavg.3 | 2 +-
 7 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/man2/capget.2 b/man2/capget.2
index 9d2f6d90c..36ad7c27c 100644
--- a/man2/capget.2
+++ b/man2/capget.2
@@ -98,11 +98,11 @@ There was, however, an API glitch, and Linux 2.6.26 added
 to fix the problem.
 .PP
 Note that 64-bit capabilities use
-.IR datap [0]
+.I datap[0]
 and
-.IR datap [1],
+.IR datap[1] ,
 whereas 32-bit capabilities use only
-.IR datap [0].
+.IR datap[0] .
 .PP
 On kernels that support file capabilities (VFS capabilities support),
 these system calls behave slightly differently.
diff --git a/man2/execve.2 b/man2/execve.2
index 5f33332ca..5e995f289 100644
--- a/man2/execve.2
+++ b/man2/execve.2
@@ -354,7 +354,7 @@ is the series of words pointed to by the
 argument of
 .BR execve (),
 starting at
-.IR argv [1].
+.IR argv[1] .
 Note that there is no way to get the
 .IR argv[0]
 that was passed to the
diff --git a/man2/readv.2 b/man2/readv.2
index 5a8b74168..d8ae756a9 100644
--- a/man2/readv.2
+++ b/man2/readv.2
@@ -119,9 +119,9 @@ Buffers are processed in array order.
 This means that
 .BR readv ()
 completely fills
-.IR iov [0]
+.I iov[0]
 before proceeding to
-.IR iov [1],
+.IR iov[1] ,
 and so on.
 (If there is insufficient data, then not all buffers pointed to by
 .I iov
@@ -129,9 +129,9 @@ may be filled.)
 Similarly,
 .BR writev ()
 writes out the entire contents of
-.IR iov [0]
+.I iov[0]
 before proceeding to
-.IR iov [1],
+.IR iov[1] ,
 and so on.
 .PP
 The data transfers performed by
diff --git a/man2/socketpair.2 b/man2/socketpair.2
index 60a90f640..0cc6e5ae1 100644
--- a/man2/socketpair.2
+++ b/man2/socketpair.2
@@ -62,9 +62,9 @@ For further details of these arguments, see
 .BR socket (2).
 .PP
 The file descriptors used in referencing the new sockets are returned in
-.IR sv [0]
+.I sv[0]
 and
-.IR sv [1].
+.IR sv[1] .
 The two sockets are indistinguishable.
 .SH RETURN VALUE
 On success, zero is returned.
diff --git a/man2/utime.2 b/man2/utime.2
index 03a43a416..24f397b1b 100644
--- a/man2/utime.2
+++ b/man2/utime.2
@@ -110,9 +110,9 @@ struct timeval {
 .EE
 .in
 .PP
-.IR times [0]
+.I times[0]
 specifies the new access time, and
-.IR times [1]
+.I times[1]
 specifies the new modification time.
 If
 .I times
diff --git a/man2/utimensat.2 b/man2/utimensat.2
index b75adbaef..eb9d2a2af 100644
--- a/man2/utimensat.2
+++ b/man2/utimensat.2
@@ -89,9 +89,9 @@ an open file descriptor,
 .PP
 For both calls, the new file timestamps are specified in the array
 .IR times :
-.IR times [0]
+.I times[0]
 specifies the new "last access time" (\fIatime\fP);
-.IR times [1]
+.I times[1]
 specifies the new "last modification time" (\fImtime\fP).
 Each of the elements of
 .I times
diff --git a/man3/getloadavg.3 b/man3/getloadavg.3
index be1f114db..015c41dfb 100644
--- a/man3/getloadavg.3
+++ b/man3/getloadavg.3
@@ -61,7 +61,7 @@ averaged over various periods of time.
 Up to
 .I nelem
 samples are retrieved and assigned to successive elements of
-.IR loadavg [].
+.IR loadavg[] .
 The system imposes a maximum of 3 samples, representing averages
 over the last 1, 5, and 15 minutes, respectively.
 .SH RETURN VALUE
-- 
2.29.2