clone.2, execve.2, getpriority.2, ipc.2, kcmp.2, killpg.2, msgctl.2, msgget.2, msgop.2, select.2, semctl.2, semget.2, semop.2, setpgid.2, shmctl.2, shmget.2, shmop.2, sigaction.2, signal.2, socket.2, socketpair.2, syscalls.2, umask.2, unshare.2: ffix: Don't allow line break inside "System V"

man2/clone.2

@@ -288,7 +288,7 @@ the process is created in the same IPC namespace as
 the calling process.
 This flag is intended for the implementation of containers.
 
-An IPC namespace provides an isolated view of System V IPC objects (see
+An IPC namespace provides an isolated view of System\ V IPC objects (see
 .BR svipc (7))
 and (since Linux 2.6.30)
 .\" commit 7eafd7c74c3f2e67c27621b987b28397110d643f
@@ -617,7 +617,7 @@ altogether in Linux 2.6.38.
 If
 .B CLONE_SYSVSEM
 is set, then the child and the calling process share
-a single list of System V semaphore undo values (see
+a single list of System\ V semaphore undo values (see
 .BR semop (2)).
 If this flag is not set, then the child has a separate undo list,
 which is initially empty.

man2/execve.2

@@ -132,7 +132,7 @@ Any alternate signal stack is not preserved
 Memory mappings are not preserved
 .RB ( mmap (2)).
 .IP *
-Attached System V shared memory segments are detached
+Attached System\ V shared memory segments are detached
 .RB ( shmat (2)).
 .IP *
 POSIX shared memory regions are unmapped

man2/getpriority.2

@@ -182,7 +182,7 @@ The details on the condition for
 .B EPERM
 depend on the system.
 The above description is what POSIX.1-2001 says, and seems to be followed on
-all System V-like systems.
+all System\ V-like systems.
 Linux kernels before 2.6.12 required the real or
 effective user ID of the caller to match
 the real user of the process \fIwho\fP (instead of its effective user ID).

man2/ipc.2

@@ -33,7 +33,7 @@ ipc \- System V IPC system calls
 .fi
 .SH DESCRIPTION
 .BR ipc ()
-is a common kernel entry point for the System V IPC calls
+is a common kernel entry point for the System\ V IPC calls
 for messages, semaphores, and shared memory.
 .I call
 determines which IPC function to invoke;

man2/kcmp.2

@@ -100,7 +100,7 @@ are ignored.
 .TP
 .BR KCMP_SYSVSEM
 Check whether the processes share the same
-list of System V semaphore undo operations.
+list of System\ V semaphore undo operations.
 The arguments
 .I idx1
 and

man2/killpg.2

@@ -114,7 +114,7 @@ SVr4, 4.4BSD (the
 function call first appeared in 4BSD), POSIX.1-2001.
 .SH NOTES
 There are various differences between the permission checking
-in BSD-type systems and System V-type systems.
+in BSD-type systems and System\ V-type systems.
 See the POSIX rationale for
 .BR kill ().
 A difference not mentioned by POSIX concerns the return

man2/msgctl.2

@@ -49,7 +49,7 @@ msgctl \- System V message control operations
 .BR msgctl ()
 performs the control operation specified by
 .I cmd
-on the System V message queue with identifier
+on the System\ V message queue with identifier
 .IR msqid .
 .PP
 The

man2/msgget.2

@@ -46,7 +46,7 @@ msgget \- get a System V message queue identifier
 .SH DESCRIPTION
 The
 .BR msgget ()
-system call returns the System V message queue identifier associated
+system call returns the System\ V message queue identifier associated
 with the value of the
 .I key
 argument.

man2/msgop.2

@@ -59,7 +59,7 @@ The
 and
 .BR msgrcv ()
 system calls are used, respectively, to send messages to,
-and receive messages from, a System V message queue.
+and receive messages from, a System\ V message queue.
 The calling process must have write permission on the message queue
 in order to send a message, and read permission to receive a message.
 .PP

man2/select.2

@@ -347,8 +347,8 @@ conforms to POSIX.1-2001 and
 first appeared in 4.2BSD).
 Generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including
-System V variants).
-However, note that the System V variant typically
+System\ V variants).
+However, note that the System\ V variant typically
 sets the timeout variable before exit, but the BSD variant does not.
 .PP
 .BR pselect ()

man2/semctl.2

@@ -53,7 +53,7 @@ semctl \- System V semaphore control operations
 .BR semctl ()
 performs the control operation specified by
 .I cmd
-on the System V semaphore set identified by
+on the System\ V semaphore set identified by
 .IR semid ,
 or on the
 .IR semnum -th

man2/semget.2

@@ -49,7 +49,7 @@ semget \- get a System V semaphore set identifier
 .SH DESCRIPTION
 The
 .BR semget ()
-system call returns the System V semaphore set identifier
+system call returns the System\ V semaphore set identifier
 associated with the argument
 .IR key .
 A new set of

man2/semop.2

@@ -55,7 +55,7 @@ Feature Test Macro Requirements for glibc (see
 .BR semtimedop ():
 _GNU_SOURCE
 .SH DESCRIPTION
-Each semaphore in a System V semaphore set
+Each semaphore in a System\ V semaphore set
 has the following associated values:
 .sp
 .in +4n

man2/setpgid.2

@@ -148,7 +148,7 @@ necessary, and the POSIX.1
 .BR getpgrp ()
 is preferred for that task.)
 
-The System V-style
+The System\ V-style
 .BR setpgrp (),
 which takes no arguments, is equivalent to
 .IR "setpgid(0,\ 0)" .

man2/shmctl.2

@@ -57,7 +57,7 @@ shmctl \- System V shared memory control
 .BR shmctl ()
 performs the control operation specified by
 .I cmd
-on the System V shared memory segment whose identifier is given in
+on the System\ V shared memory segment whose identifier is given in
 .IR shmid .
 .PP
 The

man2/shmget.2

@@ -48,7 +48,7 @@ shmget \- allocates a System V shared memory segment
 .ad b
 .SH DESCRIPTION
 .BR shmget ()
-returns the identifier of the System V shared memory segment
+returns the identifier of the System\ V shared memory segment
 associated with the value of the argument
 .IR key .
 A new shared memory segment, with size equal to the value of

man2/shmop.2

@@ -53,7 +53,7 @@ shmat, shmdt \- System V shared memory operations
 .SH DESCRIPTION
 .SS shmat()
 .BR shmat ()
-attaches the System V shared memory segment identified by
+attaches the System\ V shared memory segment identified by
 .I shmid
 to the address space of the calling process.
 The attaching address is specified by

man2/sigaction.2

@@ -712,7 +712,7 @@ POSIX.1-2001 allows this possibility, so that ignoring
 .B SIGCHLD
 can be used to prevent the creation of zombies (see
 .BR wait (2)).
-Nevertheless, the historical BSD and System V behaviors for ignoring
+Nevertheless, the historical BSD and System\ V behaviors for ignoring
 .B SIGCHLD
 differ, so that the only completely portable method of ensuring that
 terminated children do not become zombies is to catch the

man2/signal.2

@@ -196,7 +196,7 @@ with the following flags:
 
     sa.sa_flags = SA_RESETHAND | SA_NODEFER;
 
-System V also provides these semantics for
+System\ V also provides these semantics for
 .BR signal ().
 This was bad because the signal might be delivered again
 before the handler had a chance to reestablish itself.
@@ -224,7 +224,7 @@ The situation on Linux is as follows:
 .IP * 2
 The kernel's
 .BR signal ()
-system call provides System V semantics.
+system call provides System\ V semantics.
 .IP *
 By default, in glibc 2 and later, the
 .BR signal ()
@@ -246,7 +246,7 @@ On glibc 2 and later, if the
 .B _BSD_SOURCE
 feature test macro is not defined, then
 .BR signal ()
-provides System V semantics.
+provides System\ V semantics.
 (The default implicit definition of
 .B _BSD_SOURCE
 is not provided if one invokes
@@ -267,7 +267,7 @@ see
 .IP *
 The
 .BR signal ()
-function in Linux libc4 and libc5 provide System V semantics.
+function in Linux libc4 and libc5 provide System\ V semantics.
 If one on a libc5 system includes
 .I <bsd/signal.h>
 instead of

man2/socket.2

@@ -358,7 +358,7 @@ flags are Linux-specific.
 appeared in 4.2BSD.
 It is generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including
-System V variants).
+System\ V variants).
 .SH NOTES
 POSIX.1-2001 does not require the inclusion of
 .IR <sys/types.h> ,

man2/socketpair.2

@@ -99,7 +99,7 @@ The
 function call appeared in 4.2BSD.
 It is generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including
-System V variants).
+System\ V variants).
 .SH NOTES
 On Linux, the only supported domain for this call is
 .B AF_UNIX

man2/syscalls.2

@@ -607,7 +607,7 @@ T}
 On many platforms, including x86-32, socket calls are all multiplexed
 (via glibc wrapper functions) through
 .BR socketcall (2)
-and similarly System V IPC calls are multiplexed through
+and similarly System\ V IPC calls are multiplexed through
 .BR ipc (2).
 
 Although slots are reserved for them in the system call table,

man2/umask.2

@@ -111,7 +111,7 @@ and UNIX domain sockets
 .RB ( unix (7))
 created by the process.
 The umask does not affect the permissions assigned
-to System V IPC objects created by the process (using
+to System\ V IPC objects created by the process (using
 .BR msgget (2),
 .BR semget (2),
 .BR shmget (2)).

man2/unshare.2

@@ -99,9 +99,9 @@ This flag has the same effect as the
 .BR clone (2)
 .B CLONE_NEWIPC
 flag.
-Unshare the System V IPC namespace,
+Unshare the System\ V IPC namespace,
 so that the calling process has a private copy of the
-System V IPC namespace which is not shared with any other process.
+System\ V IPC namespace which is not shared with any other process.
 Specifying this flag automatically implies
 .BR CLONE_SYSVSEM
 as well.
@@ -167,7 +167,7 @@ This flag reverses the effect of the
 .BR clone (2)
 .B CLONE_SYSVSEM
 flag.
-Unshare System V semaphore undo values,
+Unshare System\ V semaphore undo values,
 so that the calling process has a private copy
 which is not shared with any other process.
 Use of