get_mempolicy.2, mq_getsetattr.2, poll.2: ffix

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

man2/get_mempolicy.2

@@ -32,8 +32,8 @@ get_mempolicy \- retrieve NUMA memory policy for a thread
 .nf
 .PP
 .BI "long get_mempolicy(int *" mode ", unsigned long *" nodemask ,
-.BI "                  unsigned long " maxnode ", void *" addr ,
-.BI "                  unsigned long " flags );
+.BI "                   unsigned long " maxnode ", void *" addr ,
+.BI "                   unsigned long " flags );
 .PP
 Link with \fI\-lnuma\fP.
 .fi

man2/ioctl_userfaultfd.2

@@ -686,13 +686,13 @@ struct uffdio_writeprotect {
 .EE
 .in
 .PP
-There're two mode bits that are supported in this structure:
+There are two mode bits that are supported in this structure:
 .TP
 .B UFFDIO_WRITEPROTECT_MODE_WP
 When this mode bit is set,
 the ioctl will be a write-protect operation upon the memory range specified by
 .IR range .
-Otherwise it'll be a write-unprotect operation upon the specified range,
+Otherwise it will be a write-unprotect operation upon the specified range,
 which can be used to resolve a userfaultfd write-protect page fault.
 .TP
 .B UFFDIO_WRITEPROTECT_MODE_DONTWAKE

man2/mount.2

@@ -151,7 +151,7 @@ Reduce on-disk updates of inode timestamps (atime, mtime, ctime)
 by maintaining these changes only in memory.
 The on-disk timestamps are updated only when:
 .RS
-.IP (a) 5
+.IP (a) 4
 the inode needs to be updated for some change unrelated to file timestamps;
 .IP (b)
 the application employs

man2/mq_getsetattr.2

@@ -30,7 +30,7 @@ mq_getsetattr \- get/set message queue attributes
 .B #include <mqueue.h>
 .PP
 .BI "int mq_getsetattr(mqd_t " mqdes ", const struct mq_attr *" newattr ,
-.BI "                 struct mq_attr *" oldattr );
+.BI "                  struct mq_attr *" oldattr );
 .fi
 .PP
 .IR Note :

man2/pipe.2

@@ -40,13 +40,6 @@ pipe, pipe2 \- create pipe
 .nf
 .B #include <unistd.h>
 .PP
-/* On Alpha, IA-64, MIPS, SuperH, and SPARC/SPARC64; see NOTES */
-.B struct fd_pair {
-.B "    long fd[2];"
-.B "};"
-.B struct fd_pair pipe();
-.PP
-/* On all other architectures */
 .BI "int pipe(int " pipefd "[2]);"
 .PP
 .BR "#define _GNU_SOURCE" "             /* See feature_test_macros(7) */"
@@ -54,6 +47,16 @@ pipe, pipe2 \- create pipe
 .B #include <unistd.h>
 .PP
 .BI "int pipe2(int " pipefd "[2], int " flags );
+.PP
+/* On Alpha, IA-64, MIPS, SuperH, and SPARC/SPARC64, pipe() has the
+   following prototype; see NOTES */
+.PP
+.B #include <unistd.h>
+.PP
+.B struct fd_pair {
+.B "    long fd[2];"
+.B "};"
+.B struct fd_pair pipe();
 .fi
 .SH DESCRIPTION
 .BR pipe ()

man2/poll.2

@@ -41,7 +41,7 @@ poll, ppoll \- wait for some event on a file descriptor
 .B #include <poll.h>
 .PP
 .BI "int ppoll(struct pollfd *" fds ", nfds_t " nfds ,
-.BI "        const struct timespec *" tmo_p ", const sigset_t *" sigmask );
+.BI "         const struct timespec *" tmo_p ", const sigset_t *" sigmask );
 .fi
 .SH DESCRIPTION
 .BR poll ()

man2/userfaultfd.2

@@ -271,7 +271,7 @@ To register with userfaultfd write-protect mode, the user needs to initiate the
 ioctl with mode
 .B UFFDIO_REGISTER_MODE_WP
 set.
-Note that it's legal to monitor the same memory range with multiple modes.
+Note that it is legal to monitor the same memory range with multiple modes.
 For example, the user can do
 .B UFFDIO_REGISTER
 with the mode set to
@@ -467,8 +467,8 @@ otherwise it is a read fault.
 .B UFFD_PAGEFAULT_FLAG_WP
 If the address is in a range that was registered with the
 .B UFFDIO_REGISTER_MODE_WP
-flag, when this bit is set, it means it's a write-protect fault.
-Otherwise it's a page-missing fault.
+flag, when this bit is set, it means it is a write-protect fault.
+Otherwise it is a page-missing fault.
 .RE
 .TP
 .I pagefault.feat.pid

man7/mount_namespaces.7

@@ -1133,6 +1133,7 @@ See
 .BR user_namespaces (7),
 .BR findmnt (8),
 .BR mount (8),
+.BR pam_namespace (8),
 .BR pivot_root (8),
 .BR umount (8)
 .PP

man7/namespaces.7

@@ -436,5 +436,4 @@ and
 .BR user_namespaces (7),
 .BR uts_namespaces (7),
 .BR lsns (8),
-.BR pam_namespace (8),
 .BR switch_root (8)

man7/vsock.7

@@ -91,10 +91,10 @@ a single machine.
 .in +4n
 .EX
 struct sockaddr_vm {
-    sa_family_t    svm_family;     /* Address family: AF_VSOCK */
+    sa_family_t    svm_family;    /* Address family: AF_VSOCK */
     unsigned short svm_reserved1;
-    unsigned int   svm_port;       /* Port # in host byte order */
-    unsigned int   svm_cid;        /* Address in host byte order */
+    unsigned int   svm_port;      /* Port # in host byte order */
+    unsigned int   svm_cid;       /* Address in host byte order */
     unsigned char  svm_zero[sizeof(struct sockaddr) \-
                             sizeof(sa_family_t) \-
                             sizeof(unsigned short) \-
@@ -236,7 +236,8 @@ Support for VMware (VMCI) has been available since Linux 3.9.
 KVM (virtio) is supported since Linux 4.8.
 Hyper-V is supported since Linux 4.14.
 .PP
-VMADDR_CID_LOCAL is supported since Linux 5.6.
+.B VMADDR_CID_LOCAL
+is supported since Linux 5.6.
 .\" commit ef343b35d46667668a099655fca4a5b2e43a5dfe
 Local communication in the guest and on the host is available since Linux 5.6.
 Previous versions supported only local communication within a guest