Many pages: Use \[em] instead of \(em

Signed-off-by: Alejandro Colomar <alx@kernel.org>

100 files changed, 178 insertions, 178 deletions

diff --git a/man1/intro.1 b/man1/intro.1
index 7ae8ab0a6..a46665f8d 100644
--- a/man1/intro.1
+++ b/man1/intro.1
@@ -103,7 +103,7 @@ Here typing Control-D ended the session.
 .PP
 The
 .B $
-here was the command prompt\(emit is the shell's way of indicating
+here was the command prompt\[em]it is the shell's way of indicating
 that it is ready for the next command.
 The prompt can be customized
 in lots of ways, and one might include stuff like username,
@@ -119,7 +119,7 @@ We see that there are commands
 .PP
 The command
 .I ls
-lists the contents of the current directory\(emit tells you what
+lists the contents of the current directory\[em]it tells you what
 files you have.
 With a
 .I \-l
diff --git a/man2/bpf.2 b/man2/bpf.2
index 989e972f3..382669665 100644
--- a/man2/bpf.2
+++ b/man2/bpf.2
@@ -840,7 +840,7 @@ The eBPF program type
 .RI ( prog_type )
 determines the subset of kernel helper functions that the program
 may call.
-The program type also determines the program input (context)\(emthe
+The program type also determines the program input (context)\[em]the
 format of
 .I "struct bpf_context"
 (which is the data blob passed into the eBPF program as the first argument).
diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
index c913b7ac7..94328b446 100644
--- a/man2/clock_getres.2
+++ b/man2/clock_getres.2
@@ -137,8 +137,8 @@ The acronym TAI refers to International Atomic Time.
 .TP
 .B CLOCK_MONOTONIC
 A nonsettable system-wide clock that
-represents monotonic time since\(emas described
-by POSIX\(em"some unspecified point in the past".
+represents monotonic time since\[em]as described
+by POSIX\[em]"some unspecified point in the past".
 On Linux, that point corresponds to the number of seconds that the system
 has been running since it was booted.
 .IP
@@ -153,7 +153,7 @@ This clock does not count time that the system is suspended.
 All
 .B CLOCK_MONOTONIC
 variants guarantee that the time returned by consecutive calls will not go
-backwards, but successive calls may\(emdepending on the architecture\(emreturn
+backwards, but successive calls may\[em]depending on the architecture\[em]return
 identical (not-increased) time values.
 .TP
 .BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)"
diff --git a/man2/clone.2 b/man2/clone.2
index 3ca501b99..0751dc853 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -399,14 +399,14 @@ and
 allow a flags bit mask that modifies their behavior
 and allows the caller to specify what is shared between the calling process
 and the child process.
-This bit mask\(emthe
+This bit mask\[em]the
 .I flags
 argument of
 .BR clone ()
 or the
 .I cl_args.flags
 field passed to
-.BR clone3 ()\(emis
+.BR clone3 ()\[em]is
 referred to as the
 .I flags
 mask in the remainder of this page.
diff --git a/man2/dup.2 b/man2/dup.2
index 557c04ac7..68b2ee80e 100644
--- a/man2/dup.2
+++ b/man2/dup.2
@@ -232,8 +232,8 @@ was open, any errors that would have been reported at
 .BR close (2)
 time are lost.
 If this is of concern,
-then\(emunless the program is single-threaded and does not allocate
-file descriptors in signal handlers\(emthe correct approach is
+then\[em]unless the program is single-threaded and does not allocate
+file descriptors in signal handlers\[em]the correct approach is
 .I not
 to close
 .I newfd
diff --git a/man2/eventfd.2 b/man2/eventfd.2
index 0a7729868..5e70d2486 100644
--- a/man2/eventfd.2
+++ b/man2/eventfd.2
@@ -82,7 +82,7 @@ if the size of the supplied buffer is less than 8 bytes.
 .IP
 The value returned by
 .BR read (2)
-is in host byte order\(emthat is,
+is in host byte order\[em]that is,
 the native byte order for integers on the host machine.
 .IP
 The semantics of
diff --git a/man2/execve.2 b/man2/execve.2
index fd8ebea88..065395443 100644
--- a/man2/execve.2
+++ b/man2/execve.2
@@ -466,7 +466,7 @@ The filesystem is mounted
 .\" commit 72fa59970f8698023045ab0713d66f3f4f96945c
 Having changed its real UID using one of the
 .BR set*uid ()
-calls, the caller was\(emand is now still\(emabove its
+calls, the caller was\[em]and is now still\[em]above its
 .B RLIMIT_NPROC
 resource limit (see
 .BR setrlimit (2)).
@@ -714,7 +714,7 @@ Since Linux 3.1, the scenario just described no longer causes the
 call to fail,
 because it too often led to security holes where buggy applications
 didn't check the return status and assumed
-that\(emif the caller had root privileges\(emthe call would always succeed.
+that\[em]if the caller had root privileges\[em]the call would always succeed.
 Instead, the
 .BR set*uid ()
 calls now successfully change the real UID,
@@ -733,7 +733,7 @@ call, that call fails with the error
 This kernel logic ensures that the
 .B RLIMIT_NPROC
 resource limit is still enforced for the
-common privileged daemon workflow\(emnamely,
+common privileged daemon workflow\[em]namely,
 .BR fork (2)
 +
 .BR set*uid ()
diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2
index 3642ec882..23169047b 100644
--- a/man2/fanotify_mark.2
+++ b/man2/fanotify_mark.2
@@ -446,7 +446,7 @@ or
 is required.
 .TP
 .B FAN_ONDIR
-Create events for directories\(emfor example, when
+Create events for directories\[em]for example, when
 .BR opendir (3),
 .BR readdir (3)
 (but see BUGS), and
diff --git a/man2/fork.2 b/man2/fork.2
index 5c94d4b53..358e90349 100644
--- a/man2/fork.2
+++ b/man2/fork.2
@@ -147,7 +147,7 @@ the child must turn on any bits that it requires using
 .PP
 Note the following further points:
 .IP \(bu 3
-The child process is created with a single thread\(emthe
+The child process is created with a single thread\[em]the
 one that called
 .BR fork ().
 The entire virtual address space of the parent is replicated in the child,
diff --git a/man2/futex.2 b/man2/futex.2
index 0fe2d6081..fcb328c95 100644
--- a/man2/futex.2
+++ b/man2/futex.2
@@ -62,8 +62,8 @@ Other
 operations can be used to wake any processes or threads waiting
 for a particular condition.
 .PP
-A futex is a 32-bit value\(emreferred to below as a
-.IR "futex word" \(emwhose
+A futex is a 32-bit value\[em]referred to below as a
+.IR "futex word" \[em]whose
 address is supplied to the
 .BR futex ()
 system call.
@@ -1010,7 +1010,7 @@ The PI futex operations are as follows:
 .\" commit c87e2837be82df479a6bae9f155c43516d2feebc
 This operation is used after an attempt to acquire
 the lock via an atomic user-mode instruction failed
-because the futex word has a nonzero value\(emspecifically,
+because the futex word has a nonzero value\[em]specifically,
 because it contained the (PID-namespace-specific) TID of the lock owner.
 .IP
 The operation checks the value of the futex word at the address
@@ -1545,7 +1545,7 @@ employs one or both of the pointers
 .I uaddr
 and
 .IR uaddr2 ,
-but one of these does not point to a valid object\(emthat is,
+but one of these does not point to a valid object\[em]that is,
 the address is not four-byte-aligned.
 .TP
 .B EINVAL
@@ -1576,7 +1576,7 @@ is invalid.
 .BR FUTEX_CMP_REQUEUE )
 The kernel detected an inconsistency between the user-space state at
 .I uaddr
-and the kernel state\(emthat is, it detected a waiter which waits in
+and the kernel state\[em]that is, it detected a waiter which waits in
 .B FUTEX_LOCK_PI
 or
 .B FUTEX_LOCK_PI2
diff --git a/man2/get_mempolicy.2 b/man2/get_mempolicy.2
index d055fcb7a..e3b942f4c 100644
--- a/man2/get_mempolicy.2
+++ b/man2/get_mempolicy.2
@@ -123,7 +123,7 @@ in the location pointed to by this argument.
 .I maxnode
 specifies the number of node IDs
 that can be stored into
-.IR nodemask \(emthat
+.IR nodemask \[em]that
 is, the maximum node ID plus one.
 The value specified by
 .I maxnode
diff --git a/man2/getitimer.2 b/man2/getitimer.2
index 093752b62..f3fe06fb9 100644
--- a/man2/getitimer.2
+++ b/man2/getitimer.2
@@ -32,9 +32,9 @@ When a timer expires, a signal is generated for the calling process,
 and the timer is reset to the specified interval
 (if the interval is nonzero).
 .PP
-Three types of timers\(emspecified via the
+Three types of timers\[em]specified via the
 .I which
-argument\(emare provided,
+argument\[em]are provided,
 each of which counts against a different clock and
 generates a different signal on timer expiration:
 .TP
diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index f3e09683b..9b361df95 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -744,7 +744,7 @@ The most pertinent limit here is
 which specifies the maximum size to which a file can grow:
 to be useful, this limit must be represented using a type
 that is as wide as the type used to
-represent file offsets\(emthat is, as wide as a 64-bit
+represent file offsets\[em]that is, as wide as a 64-bit
 .B off_t
 (assuming a program compiled with
 .IR _FILE_OFFSET_BITS=64 ).
diff --git a/man2/ioctl_iflags.2 b/man2/ioctl_iflags.2
index 573edf91e..bf3840ecb 100644
--- a/man2/ioctl_iflags.2
+++ b/man2/ioctl_iflags.2
@@ -8,7 +8,7 @@
 ioctl_iflags \- ioctl() operations for inode flags
 .SH DESCRIPTION
 Various Linux filesystems support the notion of
-.IR "inode flags" \(emattributes
+.IR "inode flags" \[em]attributes
 that modify the semantics of files and directories.
 These flags can be retrieved and modified using two
 .BR ioctl (2)
diff --git a/man2/ipc.2 b/man2/ipc.2
index 0be238af5..ca61cda68 100644
--- a/man2/ipc.2
+++ b/man2/ipc.2
@@ -42,7 +42,7 @@ Only standard library implementors and kernel hackers need to know about
 is Linux-specific, and should not be used in programs
 intended to be portable.
 .SH NOTES
-On some architectures\(emfor example x86-64 and ARM\(emthere is no
+On some architectures\[em]for example x86-64 and ARM\[em]there is no
 .BR ipc ()
 system call; instead,
 .BR msgctl (2),
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 257efb7c8..6dcaa0aaa 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -120,8 +120,8 @@ does not exist depends on the value of
 .IR int ).
 If
 .I arg3
-contains a nonzero value, then\(emif it is appropriate to do so
-(e.g., when looking up the user, user-session, or session key)\(ema new key
+contains a nonzero value, then\[em]if it is appropriate to do so
+(e.g., when looking up the user, user-session, or session key)\[em]a new key
 is created and its real key ID returned as the function result.
 .\" The keyctl_get_keyring_ID.3 page says that a new key
 .\" "will be created *if it is appropriate to do so**. What is the
diff --git a/man2/madvise.2 b/man2/madvise.2
index 3cebb4c7a..9b4652a63 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -362,8 +362,8 @@ and file-backed pages.
 For all memory types,
 memory may only be replaced by huge pages on hugepage-aligned boundaries.
 For file-mapped memory
-\(emincluding tmpfs (see
-.BR tmpfs (2))\(em
+\[em]including tmpfs (see
+.BR tmpfs (2))\[em]
 the mapping must also be naturally hugepage-aligned within the file.
 Additionally,
 for file-backed,
diff --git a/man2/mbind.2 b/man2/mbind.2
index d57021d41..5eecb11f6 100644
--- a/man2/mbind.2
+++ b/man2/mbind.2
@@ -60,11 +60,11 @@ The memory policy defines from which node memory is allocated.
 .PP
 If the memory range specified by the
 .IR addr " and " len
-arguments includes an "anonymous" region of memory\(emthat is
+arguments includes an "anonymous" region of memory\[em]that is
 a region of memory created using the
 .BR mmap (2)
 system call with the
-.BR MAP_ANONYMOUS \(emor
+.BR MAP_ANONYMOUS \[em]or
 a memory-mapped file, mapped using the
 .BR mmap (2)
 system call with the
diff --git a/man2/mlock.2 b/man2/mlock.2
index fb2a49e84..3b3c7e2a3 100644
--- a/man2/mlock.2
+++ b/man2/mlock.2
@@ -352,7 +352,7 @@ after an
 .BR mlockall ()
 or
 .BR mlock ()
-operation\(emnot even from a thread which runs at a low priority within
+operation\[em]not even from a thread which runs at a low priority within
 a process which also has a thread running at elevated priority.
 .PP
 The memory lock on an address range is automatically removed
diff --git a/man2/mmap.2 b/man2/mmap.2
index 9c3c229d5..f45165eef 100644
--- a/man2/mmap.2
+++ b/man2/mmap.2
@@ -208,7 +208,7 @@ was added in Linux 2.4.
 .B MAP_DENYWRITE
 This flag is ignored.
 .\" Introduced in 1.1.36, removed in 1.3.24.
-(Long ago\(emLinux 2.0 and earlier\(emit signaled
+(Long ago\[em]Linux 2.0 and earlier\[em]it signaled
 that attempts to write to the underlying file should fail with
 .BR ETXTBSY .
 But this was a source of denial-of-service attacks.)
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index c54bf662a..463b2c1bf 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -564,7 +564,7 @@ to prevent sensitive mount properties from being altered.
 Since the newly created mount namespace will be owned by the
 newly created user namespace,
 a calling process that is privileged in the new
-user namespace would\(emin the absence of such locking\(embe
+user namespace would\[em]in the absence of such locking\[em]be
 able to alter sensitive mount properties (e.g., to remount a mount
 that was marked read-only as read-write in the new mount namespace).
 .RE
diff --git a/man2/mprotect.2 b/man2/mprotect.2
index d6f2ed5ae..2bf3098d0 100644
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@@ -87,7 +87,7 @@ can have one of the following flags set:
 Apply the protection mode up to the end of a mapping
 that grows upwards.
 (Such mappings are created for the stack area on
-architectures\(emfor example, HP-PARISC\(emthat
+architectures\[em]for example, HP-PARISC\[em]that
 have an upwardly growing stack.)
 .\" The VMA is one that was marked with VM_GROWSUP by the kernel
 .\" when the stack was created. Note that (unlike VM_GROWSDOWN),
diff --git a/man2/open.2 b/man2/open.2
index 42d62593e..398e30260 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -523,8 +523,8 @@ One example is NFS, where the server maintains the access time.
 .B O_NOCTTY
 If
 .I pathname
-refers to a terminal device\(emsee
-.BR tty (4)\(emit
+refers to a terminal device\[em]see
+.BR tty (4)\[em]it
 will not become the process's controlling terminal even if the
 process does not have one.
 .TP
@@ -1413,7 +1413,7 @@ entries in the system-wide table of open files.
 In other contexts, this object is
 variously also called an "open file object",
 a "file handle", an "open file table entry",
-or\(emin kernel-developer parlance\(ema
+or\[em]in kernel-developer parlance\[em]a
 .IR "struct file" .
 .PP
 When a file descriptor is duplicated (using
diff --git a/man2/openat2.2 b/man2/openat2.2
index 19693cd8c..205dc3930 100644
--- a/man2/openat2.2
+++ b/man2/openat2.2
@@ -332,8 +332,8 @@ Applications that employ the
 flag are encouraged to make its use configurable
 (unless it is used for a specific security purpose),
 as symbolic links are very widely used by end-users.
-Setting this flag indiscriminately\(emi.e.,
-for purposes not specifically related to security\(emfor all uses of
+Setting this flag indiscriminately\[em]i.e.,
+for purposes not specifically related to security\[em]for all uses of
 .BR openat2 ()
 may result in spurious errors on previously functional systems.
 This may occur if, for example,
@@ -359,8 +359,8 @@ Applications that employ the
 flag are encouraged to make its use configurable (unless it is
 used for a specific security purpose),
 as bind mounts are widely used by end-users.
-Setting this flag indiscriminately\(emi.e.,
-for purposes not specifically related to security\(emfor all uses of
+Setting this flag indiscriminately\[em]i.e.,
+for purposes not specifically related to security\[em]for all uses of
 .BR openat2 ()
 may result in spurious errors on previously functional systems.
 This may occur if, for example,
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 9582a07c6..a978bd1cb 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -124,7 +124,7 @@ An event group is scheduled onto the CPU as a unit: it will
 be put onto the CPU only if all of the events in the group can be put onto
 the CPU.
 This means that the values of the member events can be
-meaningfully compared\(emadded, divided (to get ratios), and so on\(emwith each
+meaningfully compared\[em]added, divided (to get ratios), and so on\[em]with each
 other, since they have counted events for the same set of executed
 instructions.
 .PP
diff --git a/man2/prctl.2 b/man2/prctl.2
index 75df89580..4e55dc55c 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -208,8 +208,8 @@ The setting is preserved across
 .IP
 Establishing a subreaper process is useful in session management frameworks
 where a hierarchical group of processes is managed by a subreaper process
-that needs to be informed when one of the processes\(emfor example,
-a double-forked daemon\(emterminates
+that needs to be informed when one of the processes\[em]for example,
+a double-forked daemon\[em]terminates
 (perhaps so that it can restart that process).
 Some
 .BR init (1)
@@ -1658,7 +1658,7 @@ see the kernel source file
 .TP
 .BR PR_SET_TAGGED_ADDR_CTRL " (since Linux 5.4, only on arm64)"
 Controls support for passing tagged user-space addresses to the kernel
-(i.e., addresses where bits 56\(em63 are not all zero).
+(i.e., addresses where bits 56\[em]63 are not all zero).
 .IP
 The level of support is selected by
 .IR "arg2" ,
diff --git a/man2/process_vm_readv.2 b/man2/process_vm_readv.2
index 208d83a77..712a19dd2 100644
--- a/man2/process_vm_readv.2
+++ b/man2/process_vm_readv.2
@@ -77,7 +77,7 @@ specifies the number of elements in
 The
 .BR process_vm_writev ()
 system call is the converse of
-.BR process_vm_readv ()\(emit
+.BR process_vm_readv ()\[em]it
 transfers data from the local process to the remote process.
 Other than the direction of the transfer, the arguments
 .IR liovcnt ,
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index a0cdede69..f57909a66 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1554,7 +1554,7 @@ The kernel behavior described in the previous paragraph
 causes a problem with transparent handling of stopping signals.
 If the tracer restarts the tracee after group-stop,
 the stopping signal
-is effectively ignored\(emthe tracee doesn't remain stopped, it runs.
+is effectively ignored\[em]the tracee doesn't remain stopped, it runs.
 If the tracer doesn't restart the tracee before entering into the next
 .BR waitpid (2),
 future
@@ -2158,7 +2158,7 @@ and needs to be restarted and waited for again, until
 is seen.
 Yet another complication is to be sure that
 the tracee is not already ptrace-stopped,
-because no signal delivery happens while it is\(emnot even
+because no signal delivery happens while it is\[em]not even
 .BR SIGSTOP .
 .\" FIXME Describe how to detach from a group-stopped tracee so that it
 .\" doesn't run, but continues to wait for SIGCONT.
@@ -2269,7 +2269,7 @@ On receiving the
 stop notification,
 the tracer should clean up all its internal
 data structures describing the threads of this process,
-and retain only one data structure\(emone which
+and retain only one data structure\[em]one which
 describes the single still running tracee, with
 .PP
 .in +4n
@@ -2484,7 +2484,7 @@ The checks are based on factors such as the credentials and capabilities
 of the two processes,
 whether or not the "target" process is dumpable,
 and the results of checks performed by any enabled Linux Security Module
-(LSM)\(emfor example, SELinux, Yama, or Smack\(emand by the commoncap LSM
+(LSM)\[em]for example, SELinux, Yama, or Smack\[em]and by the commoncap LSM
 (which is always invoked).
 .PP
 Prior to Linux 2.6.27, all access checks were of a single type.
@@ -2718,7 +2718,7 @@ More precisely, the Yama LSM limits two types of operations:
 .IP \(bu 3
 Any operation that performs a ptrace access mode
 .B PTRACE_MODE_ATTACH
-check\(emfor example,
+check\[em]for example,
 .BR ptrace ()
 .BR PTRACE_ATTACH .
 (See the "Ptrace access mode checking" discussion above.)
diff --git a/man2/rename.2 b/man2/rename.2
index e23e44324..6af25af36 100644
--- a/man2/rename.2
+++ b/man2/rename.2
@@ -310,7 +310,7 @@ this an error.
 (Note that there is no requirement to return
 .B EBUSY
 in such
-cases\(emthere is nothing wrong with doing the rename anyway\(embut
+cases\[em]there is nothing wrong with doing the rename anyway\[em]but
 it is allowed to return
 .B EBUSY
 if the system cannot otherwise
diff --git a/man2/request_key.2 b/man2/request_key.2
index e6c774af2..b1f8cce7e 100644
--- a/man2/request_key.2
+++ b/man2/request_key.2
@@ -362,8 +362,8 @@ is no longer accessible from the
 .BR request\-key (8)
 program.
 .PP
-If a key is created, then\(emregardless of whether it is a valid key or
-a negatively instantiated key\(emit will displace any other key with
+If a key is created, then\[em]regardless of whether it is a valid key or
+a negatively instantiated key\[em]it will displace any other key with
 the same type and description from the keyring specified in
 .IR dest_keyring .
 .SH RETURN VALUE
diff --git a/man2/restart_syscall.2 b/man2/restart_syscall.2
index 739067cea..1ed8c5568 100644
--- a/man2/restart_syscall.2
+++ b/man2/restart_syscall.2
@@ -35,7 +35,7 @@ This system call is designed only for internal use by the kernel.
 .PP
 .BR restart_syscall ()
 is used for restarting only those system calls that,
-when restarted, should adjust their time-related parameters\(emnamely
+when restarted, should adjust their time-related parameters\[em]namely
 .BR poll (2)
 (since Linux 2.6.24),
 .BR nanosleep (2)
diff --git a/man2/seccomp.2 b/man2/seccomp.2
index fdfdbab6f..aacdfbb01 100644
--- a/man2/seccomp.2
+++ b/man2/seccomp.2
@@ -454,7 +454,7 @@ the least significant 16-bits (defined by the constant
 are "data" to be associated with this return value.
 .PP
 If multiple filters exist, they are \fIall\fP executed,
-in reverse order of their addition to the filter tree\(emthat is,
+in reverse order of their addition to the filter tree\[em]that is,
 the most recently installed filter is executed first.
 (Note that all filters will be called
 even if one of the earlier filters returns
@@ -660,9 +660,9 @@ notified.
 (This means that, on older kernels, seccomp-based sandboxes
 .B "must not"
 allow use of
-.BR ptrace (2)\(emeven
+.BR ptrace (2)\[em]even
 of other
-sandboxed processes\(emwithout extreme care;
+sandboxed processes\[em]without extreme care;
 ptracers can use this mechanism to escape from the seccomp sandbox.)
 .IP
 Note that a tracer process will not be notified
diff --git a/man2/select.2 b/man2/select.2
index aad161673..5e31bc892 100644
--- a/man2/select.2
+++ b/man2/select.2
@@ -61,7 +61,7 @@ Feature Test Macro Requirements for glibc (see
 .BR select ()
 can monitor only file descriptors numbers that are less than
 .B FD_SETSIZE
-(1024)\(eman unreasonably low limit for many modern applications\(emand
+(1024)\[em]an unreasonably low limit for many modern applications\[em]and
 this limitation will not change.
 All modern applications should instead use
 .BR poll (2)
diff --git a/man2/select_tut.2 b/man2/select_tut.2
index 9d62db023..8fb04e9d4 100644
--- a/man2/select_tut.2
+++ b/man2/select_tut.2
@@ -620,7 +620,7 @@ inefficient timeouts.
 .PP
 The program does not handle more than one simultaneous connection at a
 time, although it could easily be extended to do this with a linked list
-of buffers\(emone for each connection.
+of buffers\[em]one for each connection.
 At the moment, new
 connections cause the current connection to be dropped.
 .SH SEE ALSO
diff --git a/man2/semop.2 b/man2/semop.2
index f496a9e10..1a878f2da 100644
--- a/man2/semop.2
+++ b/man2/semop.2
@@ -115,7 +115,7 @@ is specified for this operation, the system subtracts the value
 from the semaphore adjustment
 .RI ( semadj )
 value for this semaphore.
-This operation can always proceed\(emit never forces a thread to wait.
+This operation can always proceed\[em]it never forces a thread to wait.
 The calling process must have alter permission on the semaphore set.
 .PP
 If
@@ -388,7 +388,7 @@ of all operations performed on a semaphore specifying the
 flag.
 Each process has a list of
 .I semadj
-values\(emone value for each semaphore on which it has operated using
+values\[em]one value for each semaphore on which it has operated using
 .BR SEM_UNDO .
 When a process terminates, each of its per-semaphore
 .I semadj
diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2
index 4998ecb53..844fa0839 100644
--- a/man2/set_mempolicy.2
+++ b/man2/set_mempolicy.2
@@ -179,7 +179,7 @@ argument must include one of the following values:
 .B MPOL_DEFAULT
 This mode specifies that any nondefault thread memory policy be removed,
 so that the memory policy "falls back" to the system default policy.
-The system default policy is "local allocation"\(emthat is,
+The system default policy is "local allocation"\[em]that is,
 allocate memory on the node of the CPU that triggered the allocation.
 .I nodemask
 must be specified as NULL.
diff --git a/man2/sigreturn.2 b/man2/sigreturn.2
index 69d7b1d16..a4f0e1315 100644
--- a/man2/sigreturn.2
+++ b/man2/sigreturn.2
@@ -38,8 +38,8 @@ The signal trampoline code in turn calls
 This
 .BR sigreturn ()
 call undoes everything that was
-done\(emchanging the process's signal mask, switching signal stacks (see
-.BR sigaltstack "(2))\(emin"
+done\[em]changing the process's signal mask, switching signal stacks (see
+.BR sigaltstack "(2))\[em]in"
 order to invoke the signal handler.
 Using the information that was earlier saved on the user-space stack
 .BR sigreturn ()
diff --git a/man2/socketcall.2 b/man2/socketcall.2
index 47d38d6ce..a5803eea6 100644
--- a/man2/socketcall.2
+++ b/man2/socketcall.2
@@ -146,7 +146,7 @@ T}
 This call is specific to Linux, and should not be used in programs
 intended to be portable.
 .SH NOTES
-On some architectures\(emfor example, x86-64 and ARM\(emthere is no
+On some architectures\[em]for example, x86-64 and ARM\[em]there is no
 .BR socketcall ()
 system call; instead
 .BR socket (2),
diff --git a/man2/spu_create.2 b/man2/spu_create.2
index ae59baeb9..d7215fd78 100644
--- a/man2/spu_create.2
+++ b/man2/spu_create.2
@@ -102,7 +102,7 @@ argument to
 Create an SPU gang instead of a context.
 (A gang is a group of SPU contexts that are
 functionally related to each other and which share common scheduling
-parameters\(empriority and policy.
+parameters\[em]priority and policy.
 In the future, gang scheduling may be implemented causing
 the group to be switched in and out as a single unit.)
 .IP
diff --git a/man2/stat.2 b/man2/stat.2
index e4e7eaeb3..8479befcc 100644
--- a/man2/stat.2
+++ b/man2/stat.2
@@ -63,11 +63,11 @@ Feature Test Macro Requirements for glibc (see
 .SH DESCRIPTION
 These functions return information about a file, in the buffer pointed to by
 .IR statbuf .
-No permissions are required on the file itself, but\(emin the case of
+No permissions are required on the file itself, but\[em]in the case of
 .BR stat (),
 .BR fstatat (),
 and
-.BR lstat ()\(emexecute
+.BR lstat ()\[em]execute
 (search) permission is required on all of the directories in
 .I pathname
 that lead to the file.
diff --git a/man2/syscall.2 b/man2/syscall.2
index a66338d59..d7b744862 100644
--- a/man2/syscall.2
+++ b/man2/syscall.2
@@ -333,7 +333,7 @@ arguments 5 through 8 on the user stack.
 .ft P
 \}
 .PP
-Note that these tables don't cover the entire calling convention\(emsome
+Note that these tables don't cover the entire calling convention\[em]some
 architectures may indiscriminately clobber other registers not listed here.
 .SH EXAMPLES
 .\" SRC BEGIN (syscall.c)
diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2
index 5ccc165a3..ccb0e4f29 100644
--- a/man2/timerfd_create.2
+++ b/man2/timerfd_create.2
@@ -255,7 +255,7 @@ then the buffer given to
 returns an unsigned 8-byte integer
 .RI ( uint64_t )
 containing the number of expirations that have occurred.
-(The returned value is in host byte order\(emthat is,
+(The returned value is in host byte order\[em]that is,
 the native byte order for integers on the host machine.)
 .IP
 If no timer expirations have occurred at the time of the
diff --git a/man2/uname.2 b/man2/uname.2
index b86bc4dfa..c44f9cf26 100644
--- a/man2/uname.2
+++ b/man2/uname.2
@@ -89,7 +89,7 @@ or
 Clearly, it is a bad
 idea to use any of these constants; just use sizeof(...).
 SVr4 uses 257, "to support Internet hostnames"
-\(em this is the largest value likely to be encountered in the wild.
+\[em] this is the largest value likely to be encountered in the wild.
 .PP
 Part of the utsname information is also accessible via
 .IR /proc/sys/kernel/ { ostype ,
diff --git a/man3/aio_read.3 b/man3/aio_read.3
index fa1a10d38..d4cbbe5ef 100644
--- a/man3/aio_read.3
+++ b/man3/aio_read.3
@@ -85,7 +85,7 @@ be reported via
 .BR aio_return (3)
 (returns status \-1) and
 .BR aio_error (3)
-(error status\(emwhatever one would have gotten in
+(error status\[em]whatever one would have gotten in
 .IR errno ,
 such as
 .BR EBADF ).
diff --git a/man3/aio_write.3 b/man3/aio_write.3
index 7c043f0b4..b96a9fd3b 100644
--- a/man3/aio_write.3
+++ b/man3/aio_write.3
@@ -92,7 +92,7 @@ be reported via
 .BR aio_return (3)
 (returns status \-1) and
 .BR aio_error (3)
-(error status\(emwhatever one would have gotten in
+(error status\[em]whatever one would have gotten in
 .IR errno ,
 such as
 .BR EBADF ).
diff --git a/man3/dlopen.3 b/man3/dlopen.3
index 20a342d88..907a4088a 100644
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
@@ -245,7 +245,7 @@ fails for any reason, it returns NULL.
 .\"
 .SS dlmopen()
 This function performs the same task as
-.BR dlopen ()\(emthe
+.BR dlopen ()\[em]the
 .I filename
 and
 .I flags
@@ -400,7 +400,7 @@ objects that have been (explicitly and implicitly) loaded into the namespace.
 .PP
 The
 .BR dlmopen ()
-function permits object-load isolation\(emthe ability
+function permits object-load isolation\[em]the ability
 to load a shared object in a new namespace without
 exposing the rest of the application to the symbols
 made available by the new object.
diff --git a/man3/expm1.3 b/man3/expm1.3
index 96b2beb7c..ed3e7c341 100644
--- a/man3/expm1.3
+++ b/man3/expm1.3
@@ -54,7 +54,7 @@ These functions return a value equivalent to
 The result is computed in a way that is accurate even if the value of
 .I x
 is near
-zero\(ema case where
+zero\[em]a case where
 .I "exp(x) \- 1"
 would be inaccurate due to
 subtraction of two numbers that are nearly equal.
diff --git a/man3/fwide.3 b/man3/fwide.3
index 94746068a..867c1dce2 100644
--- a/man3/fwide.3
+++ b/man3/fwide.3
@@ -39,7 +39,7 @@ orientation of \fIstream\fP.
 It returns a positive value if \fIstream\fP is
 wide-character oriented, that is, if wide-character I/O is permitted but char
 I/O is disallowed.
-It returns a negative value if \fIstream\fP is byte oriented\(emthat is,
+It returns a negative value if \fIstream\fP is byte oriented\[em]that is,
 if char I/O is permitted but wide-character I/O is disallowed.
 It
 returns zero if \fIstream\fP has no orientation yet; in this case the next
diff --git a/man3/getifaddrs.3 b/man3/getifaddrs.3
index a327bd926..20c5bfb5d 100644
--- a/man3/getifaddrs.3
+++ b/man3/getifaddrs.3
@@ -172,7 +172,7 @@ T}	Thread safety	MT-Safe
 Not in POSIX.1.
 This function first appeared in BSDi and is
 present on the BSD systems, but with slightly different
-semantics documented\(emreturning one entry per interface,
+semantics documented\[em]returning one entry per interface,
 not per address.
 This means
 .I ifa_addr
diff --git a/man3/isalpha.3 b/man3/isalpha.3
index 78acf5361..668369bcf 100644
--- a/man3/isalpha.3
+++ b/man3/isalpha.3
@@ -139,7 +139,7 @@ locale, it is equivalent to
 .BI "(isupper(" c ") || islower(" c "))" \fR.
 In some locales, there may be additional characters for which
 .BR isalpha ()
-is true\(emletters which are neither uppercase nor lowercase.
+is true\[em]letters which are neither uppercase nor lowercase.
 .TP
 .BR isascii ()
 checks whether \fIc\fP is a 7-bit
diff --git a/man3/mallinfo.3 b/man3/mallinfo.3
index abf2314d6..4326c0ef7 100644
--- a/man3/mallinfo.3
+++ b/man3/mallinfo.3
@@ -94,7 +94,7 @@ The number of bytes in blocks currently allocated using
 .I usmblks
 This field is unused, and is always 0.
 .\" It seems to have been zero since at least as far back as glibc 2.15
-Historically, it was the "highwater mark" for allocated space\(emthat is,
+Historically, it was the "highwater mark" for allocated space\[em]that is,
 the maximum amount of space that was ever allocated (in bytes);
 this field was maintained only in nonthreading environments.
 .TP
diff --git a/man3/mkstemp.3 b/man3/mkstemp.3
index e1936cea6..15262df0e 100644
--- a/man3/mkstemp.3
+++ b/man3/mkstemp.3
@@ -85,8 +85,8 @@ The
 .BR mkostemp ()
 function is like
 .BR mkstemp (),
-with the difference that the following bits\(emwith the same meaning as for
-.BR open (2)\(emmay
+with the difference that the following bits\[em]with the same meaning as for
+.BR open (2)\[em]may
 be specified in
 .IR flags :
 .BR O_APPEND ,
diff --git a/man3/netlink.3 b/man3/netlink.3
index 119db8d68..4e6709a9f 100644
--- a/man3/netlink.3
+++ b/man3/netlink.3
@@ -62,7 +62,7 @@ The caller must check if the current
 .I nlmsghdr
 didn't have the
 .B NLMSG_DONE
-set\(emthis function doesn't return NULL on end.
+set\[em]this function doesn't return NULL on end.
 The
 .I len
 argument is an lvalue containing the remaining length
diff --git a/man3/posix_spawn.3 b/man3/posix_spawn.3
index d2d168d89..7509f2fce 100644
--- a/man3/posix_spawn.3
+++ b/man3/posix_spawn.3
@@ -409,7 +409,7 @@ If
 .I file_actions
 is NULL, then no special action is taken, and standard
 .BR exec (3)
-semantics apply\(emfile descriptors open before the exec
+semantics apply\[em]file descriptors open before the exec
 remain open in the new process,
 except those for which the
 .B FD_CLOEXEC
diff --git a/man3/pthread_create.3 b/man3/pthread_create.3
index 2f0d3c7f6..4fa3965f1 100644
--- a/man3/pthread_create.3
+++ b/man3/pthread_create.3
@@ -163,7 +163,7 @@ by
 Unless real-time scheduling policies are being employed,
 after a call to
 .BR pthread_create (),
-it is indeterminate which thread\(emthe caller or the new thread\(emwill
+it is indeterminate which thread\[em]the caller or the new thread\[em]will
 next execute.
 .PP
 A thread may either be
diff --git a/man3/pthread_getattr_default_np.3 b/man3/pthread_getattr_default_np.3
index 458f5a50b..29c795f83 100644
--- a/man3/pthread_getattr_default_np.3
+++ b/man3/pthread_getattr_default_np.3
@@ -22,7 +22,7 @@ POSIX threads library
 The
 .BR pthread_setattr_default_np ()
 function sets the default attributes used for creation of a new
-thread\(emthat is, the attributes that are used when
+thread\[em]that is, the attributes that are used when
 .BR pthread_create (3)
 is called with a second argument that is NULL.
 The default attributes are set using the attributes supplied in
diff --git a/man3/random.3 b/man3/random.3
index f712ad9d5..5ad72d878 100644
--- a/man3/random.3
+++ b/man3/random.3
@@ -76,7 +76,7 @@ The size of the state array
 \fIn\fP is used by
 .BR initstate ()
 to decide how sophisticated a
-random number generator it should use\(emthe larger the state array,
+random number generator it should use\[em]the larger the state array,
 the better the random numbers will be.
 Current "optimal" values for the size of the state array \fIn\fP are
 8, 32, 64, 128, and 256 bytes; other amounts will be rounded down to
diff --git a/man3/resolver.3 b/man3/resolver.3
index 6734ee870..b19b89e54 100644
--- a/man3/resolver.3
+++ b/man3/resolver.3
@@ -299,7 +299,7 @@ by the domain name server, not by
 If set,
 .BR res_search ()
 will append the default domain name to
-single component names\(emthat is, those that do not contain a dot.
+single component names\[em]that is, those that do not contain a dot.
 [Enabled by default].
 .TP
 .B RES_STAYOPEN
diff --git a/man3/shm_open.3 b/man3/shm_open.3
index e25e103a3..16bf212b2 100644
--- a/man3/shm_open.3
+++ b/man3/shm_open.3
@@ -90,7 +90,7 @@ is listed in
 (Symbolic definitions of these constants can be obtained by including
 .IR <sys/stat.h> .)
 .IP
-A new shared memory object initially has zero length\(emthe size of the
+A new shared memory object initially has zero length\[em]the size of the
 object can be set using
 .BR ftruncate (2).
 The newly allocated bytes of a shared memory
@@ -257,7 +257,7 @@ and
 .B O_TRUNC
 unspecified.
 On Linux, this will successfully truncate an existing
-shared memory object\(emthis may not be so on other UNIX systems.
+shared memory object\[em]this may not be so on other UNIX systems.
 .PP
 The POSIX shared memory object implementation on Linux makes use
 of a dedicated
diff --git a/man3/sscanf.3 b/man3/sscanf.3
index 470010d85..f0c771f7a 100644
--- a/man3/sscanf.3
+++ b/man3/sscanf.3
@@ -123,7 +123,7 @@ this specification, and the result is placed in the corresponding
 .I pointer
 argument.
 If the next item of input does not match the conversion specification,
-the conversion fails\(emthis is a
+the conversion fails\[em]this is a
 .IR "matching failure" .
 .PP
 Each
diff --git a/man3/strftime.3 b/man3/strftime.3
index af5ef5ce9..67ccf15cf 100644
--- a/man3/strftime.3
+++ b/man3/strftime.3
@@ -147,7 +147,7 @@ The day of the month as a decimal number (range 01 to 31).
 .B %D
 Equivalent to
 .BR %m/%d/%y .
-(Yecch\(emfor Americans only.
+(Yecch\[em]for Americans only.
 Americans should note that in other countries
 .B %d/%m/%y
 is rather common.
diff --git a/man3type/size_t.3type b/man3type/size_t.3type
index 74577dc0b..6a71be7a8 100644
--- a/man3type/size_t.3type
+++ b/man3type/size_t.3type
@@ -79,7 +79,7 @@ Although
 works for
 .I ssize_t
 on most implementations,
-portable POSIX programs should avoid using it\(emfor example,
+portable POSIX programs should avoid using it\[em]for example,
 by converting the value to
 .I intmax_t
 and using its length modifier
diff --git a/man3type/stat.3type b/man3type/stat.3type
index 0905e0ea5..5f6e07886 100644
--- a/man3type/stat.3type
+++ b/man3type/stat.3type
@@ -119,10 +119,10 @@ For further information on the above fields, see
 .SH VERSIONS
 Old kernels and old standards did not support nanosecond timestamp fields.
 Instead, there were three timestamp
-.RI fields\(em st_atime ,
+.RI fields\[em] st_atime ,
 .IR st_mtime ,
 and
-.IR st_ctime \(emtyped
+.IR st_ctime \[em]typed
 as
 .I time_t
 that recorded timestamps with one-second precision.
diff --git a/man4/console_codes.4 b/man4/console_codes.4
index 3780aac8e..a25c54c8b 100644
--- a/man4/console_codes.4
+++ b/man4/console_codes.4
@@ -470,14 +470,14 @@ DECARM (default on): Set keyboard autorepeat on.
 .TP
 ESC [ ? 9 h
 X10 Mouse Reporting (default off): Set reporting mode to 1 (or reset to
-0)\(emsee below.
+0)\[em]see below.
 .TP
 ESC [ ? 25 h
 DECTECM (default on): Make cursor visible.
 .TP
 ESC [ ? 1000 h
 X11 Mouse Reporting (default off): Set reporting mode to 2 (or reset
-to 0)\(emsee below.
+to 0)\[em]see below.
 .\"
 .PP
 .B Linux Console Private CSI Sequences
diff --git a/man4/intro.4 b/man4/intro.4
index a12c38c2d..1a3aadabb 100644
--- a/man4/intro.4
+++ b/man4/intro.4
@@ -10,7 +10,7 @@ intro \- introduction to special files
 .SH DESCRIPTION
 Section 4 of the manual describes special files (devices).
 .SH FILES
-/dev/* \(em device files
+/dev/* \[em] device files
 .SH NOTES
 .SS Authors and copyright conditions
 Look at the header of the manual page source for the author(s) and copyright
diff --git a/man4/sk98lin.4 b/man4/sk98lin.4
index dc971e8c9..bb747d9b3 100644
--- a/man4/sk98lin.4
+++ b/man4/sk98lin.4
@@ -453,13 +453,13 @@ depending on the load of the system.
 If the driver detects that the system load is too high,
 the driver tries to shield the system against too much network
 load by enabling interrupt moderation.
-If\(emat a later time\(emthe CPU utilization decreases
+If\[em]at a later time\[em]the CPU utilization decreases
 again (or if the network load is negligible), the interrupt
 moderation will automatically be disabled.
 .IP
 Interrupt moderation should be used when the driver has to
 handle one or more interfaces with a high network load,
-which\(emas a consequence\(emleads also to a high CPU utilization.
+which\[em]as a consequence\[em]leads also to a high CPU utilization.
 When moderation is applied in such high network load situations,
 CPU load might be reduced by 20\[en]30% on slow computers.
 .IP
@@ -573,9 +573,9 @@ It denotes also common problems and provides the solution to them.
 .SH BUGS
 Report any bugs to linux@syskonnect.de
 .\" .SH AUTHORS
-.\" Ralph Roesler \(em rroesler@syskonnect.de
+.\" Ralph Roesler \[em] rroesler@syskonnect.de
 .\" .br
-.\" Mirko Lindner \(em mlindner@syskonnect.de
+.\" Mirko Lindner \[em] mlindner@syskonnect.de
 .SH SEE ALSO
 .BR ifconfig (8),
 .BR insmod (8),
diff --git a/man4/st.4 b/man4/st.4
index b38711f53..9e15078fd 100644
--- a/man4/st.4
+++ b/man4/st.4
@@ -217,7 +217,7 @@ driver are passed to the
 driver.
 The definitions below are from
 .IR /usr/include/linux/mtio.h :
-.SS MTIOCTOP \(em perform a tape operation
+.SS MTIOCTOP \[em] perform a tape operation
 This request takes an argument of type
 .IR "(struct mtop\ *)" .
 Not all drives support all operations.
@@ -332,7 +332,7 @@ is enabled for the drive (see
 below).
 .TP
 .B MTNOP
-No op\(emflushes the driver's buffer as a side effect.
+No op\[em]flushes the driver's buffer as a side effect.
 Should be used before reading status with
 .BR MTIOCGET .
 .TP
@@ -667,7 +667,7 @@ the cleaning request.
 If the pattern is nonzero, the pattern must match
 the masked sense data byte.
 .RE
-.SS MTIOCGET \(em get status
+.SS MTIOCGET \[em] get status
 This request takes an argument of type
 .IR "(struct mtget\ *)" .
 .PP
@@ -799,7 +799,7 @@ This value is set to \-1 when the block number is unknown (e.g., after
 .BR MTBSS ,
 or
 .BR MTSEEK ).
-.SS MTIOCPOS \(em get tape position
+.SS MTIOCPOS \[em] get tape position
 This request takes an argument of type
 .I "(struct mtpos\ *)"
 and reports the drive's notion of the current tape block number,
diff --git a/man4/wavelan.4 b/man4/wavelan.4
index b55c1be5e..a54144034 100644
--- a/man4/wavelan.4
+++ b/man4/wavelan.4
@@ -125,9 +125,9 @@ Some of the mentioned features are optional.
 You may enable or disable
 them by changing flags in the driver header and recompile.
 .\" .SH AUTHOR
-.\" Bruce Janson \(em bruce@cs.usyd.edu.au
+.\" Bruce Janson \[em] bruce@cs.usyd.edu.au
 .\" .br
-.\" Jean Tourrilhes \(em jt@hplb.hpl.hp.com
+.\" Jean Tourrilhes \[em] jt@hplb.hpl.hp.com
 .\" .br
 .\" (and others; see source code for details)
 .\"
diff --git a/man5/core.5 b/man5/core.5
index 472edbf0c..c9b50efc2 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -75,7 +75,7 @@ The binary being executed by the process does not have read
 permission enabled.
 (This is a security measure to
 ensure that an executable whose contents are not readable
-does not produce a\(empossibly readable\(emcore dump containing
+does not produce a\[em]possibly readable\[em]core dump containing
 an image of the executable.)
 .IP \(bu
 The process is executing a set-user-ID (set-group-ID) program
@@ -151,7 +151,7 @@ Core file size soft resource limit of crashing process (since Linux 2.6.24).
 .TP
 %d
 .\" Added in git commit 12a2b4b2241e318b4f6df31228e4272d2c2968a1
-Dump mode\(emsame as value returned by
+Dump mode\[em]same as value returned by
 .BR prctl (2)
 .B PR_GET_DUMPABLE
 (since Linux 3.7).
diff --git a/man5/proc.5 b/man5/proc.5
index 0284d2624..2b0a8af69 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -521,7 +521,7 @@ Think of this file as the command line that the process wants you to see.
 .\" commit 4614a696bd1c3a9af3a08f0e5874830a85b889d4
 This file exposes the process's
 .I comm
-value\(emthat is, the command name associated with the process.
+value\[em]that is, the command name associated with the process.
 Different threads in the same process may have different
 .I comm
 values, accessible via
@@ -1148,14 +1148,14 @@ Similar caveats apply here as with
 .IR rchar .
 .TP
 .IR syscr ": read syscalls"
-Attempt to count the number of read I/O operations\(emthat is,
+Attempt to count the number of read I/O operations\[em]that is,
 system calls such as
 .BR read (2)
 and
 .BR pread (2).
 .TP
 .IR syscw ": write syscalls"
-Attempt to count the number of write I/O operations\(emthat is,
+Attempt to count the number of write I/O operations\[em]that is,
 system calls such as
 .BR write (2)
 and
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 7a8f24dcf..b9ca2ac26 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -299,7 +299,7 @@ will clear the counters.
 .SS Boot arguments for ramdisk use
 (Only if the kernel was compiled with
 .BR CONFIG_BLK_DEV_RAM .)
-In general it is a bad idea to use a ramdisk under Linux\(emthe
+In general it is a bad idea to use a ramdisk under Linux\[em]the
 system will use available memory more efficiently itself.
 But while booting,
 it is often useful to load the floppy contents into a
diff --git a/man7/capabilities.7 b/man7/capabilities.7
index cb0725d25..7c4268adf 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1290,9 +1290,9 @@ a process with UID 0 (root) executes a program and
 when a set-user-ID-root program is executed.
 .PP
 After having performed any changes to the process effective ID that
-were triggered by the set-user-ID mode bit of the binary\(eme.g.,
+were triggered by the set-user-ID mode bit of the binary\[em]e.g.,
 switching the effective user ID to 0 (root) because
-a set-user-ID-root program was executed\(emthe
+a set-user-ID-root program was executed\[em]the
 kernel calculates the file capability sets as follows:
 .IP (1) 5
 If the real or effective user ID of the process is 0 (root),
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 3206bc5d3..cd68ff77d 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -840,7 +840,7 @@ other children.
 The "no internal processes" rule is in fact more subtle than stated above.
 More precisely, the rule is that a (nonroot) cgroup can't both
 (1) have member processes, and
-(2) distribute resources into child cgroups\(emthat is, have a nonempty
+(2) distribute resources into child cgroups\[em]that is, have a nonempty
 .I cgroup.subtree_control
 file.
 Thus, it
@@ -1632,7 +1632,7 @@ cgroup,
 .IR x ,
 can revert to the type
 .I domain
-if the above conditions no longer hold true\(emthat is, if all
+if the above conditions no longer hold true\[em]that is, if all
 .I threaded
 child cgroups of
 .I x
diff --git a/man7/cpuset.7 b/man7/cpuset.7
index 4d3132dc2..57a21f62c 100644
--- a/man7/cpuset.7
+++ b/man7/cpuset.7
@@ -531,8 +531,8 @@ single read, instead of having to read and accumulate results
 for a period of time.
 .IP \(bu
 Because this meter is per-cpuset rather than per-process,
-the batch scheduler can obtain the key information\(emmemory
-pressure in a cpuset\(emwith a single read, rather than having to
+the batch scheduler can obtain the key information\[em]memory
+pressure in a cpuset\[em]with a single read, rather than having to
 query and accumulate results over all the (dynamically changing)
 set of processes in the cpuset.
 .PP
diff --git a/man7/fanotify.7 b/man7/fanotify.7
index 01872057e..43580d347 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -1236,8 +1236,8 @@ a command-line argument
 and waits until an event of type
 .B FAN_CREATE
 has occurred.
-The event mask indicates which type of filesystem object\(emeither
-a file or a directory\(emwas created.
+The event mask indicates which type of filesystem object\[em]either
+a file or a directory\[em]was created.
 Once all events have been read from the buffer and processed accordingly,
 the program simply terminates.
 .PP
diff --git a/man7/inotify.7 b/man7/inotify.7
index f755548f8..265b73f52 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -185,7 +185,7 @@ File was accessed (e.g.,
 .BR execve (2)).
 .TP
 .BR IN_ATTRIB " (*)"
-Metadata changed\(emfor example, permissions (e.g.,
+Metadata changed\[em]for example, permissions (e.g.,
 .BR chmod (2)),
 timestamps (e.g.,
 .BR utimensat (2)),
diff --git a/man7/ip.7 b/man7/ip.7
index f69af1b32..2b689b22f 100644
--- a/man7/ip.7
+++ b/man7/ip.7
@@ -399,7 +399,7 @@ structure similar to
 .BR IP_ADD_MEMBERSHIP .
 .TP
 .BR IP_DROP_SOURCE_MEMBERSHIP " (since Linux 2.4.22 / 2.5.68)"
-Leave a source-specific group\(emthat is, stop receiving data from
+Leave a source-specific group\[em]that is, stop receiving data from
 a given multicast group that come from a given source.
 If the application has subscribed to multiple sources within
 the same group, data from the remaining sources will still be delivered.
@@ -1143,7 +1143,7 @@ IP forwarding can be also set on a per-interface basis.
 .IR ip_local_port_range " (since Linux 2.2)"
 .\" Precisely: since Linux 2.1.68
 This file contains two integers that define the default local port range
-allocated to sockets that are not explicitly bound to a port number\(emthat
+allocated to sockets that are not explicitly bound to a port number\[em]that
 is, the range used for
 .IR "ephemeral ports" .
 An ephemeral port is allocated to a socket in the following circumstances:
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 785127755..772abd4ed 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -68,7 +68,7 @@ Much as files do,
 each key has an owning user ID, an owning group ID, and a security label.
 Each key also has a set of permissions,
 though there are more than for a normal UNIX file,
-and there is an additional category\(empossessor\(embeyond the usual user,
+and there is an additional category\[em]possessor\[em]beyond the usual user,
 group, and other (see
 .IR Possession ,
 below).
diff --git a/man7/locale.7 b/man7/locale.7
index b6567e8fd..02fdd57f4 100644
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -163,7 +163,7 @@ elements, which return strings such as "Herr" and "Frau"
 .TP
 .B LC_NUMERIC
 This category determines the formatting rules used for nonmonetary
-numeric values\(emfor example,
+numeric values\[em]for example,
 the thousands separator and the radix character
 (a period in most English-speaking countries,
 but a comma in many other regions).
diff --git a/man7/man-pages.7 b/man7/man-pages.7
index e5b111283..51b0b1d42 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -463,8 +463,8 @@ Hyphenation of individual page names can be prevented
 by preceding words with the string "\e%".
 .IP
 Given the distributed, autonomous nature of FOSS projects
-and their documentation, it is sometimes necessary\(emand in many cases
-desirable\(emthat the SEE ALSO section includes references to
+and their documentation, it is sometimes necessary\[em]and in many cases
+desirable\[em]that the SEE ALSO section includes references to
 manual pages provided by other projects.
 .SH FORMATTING AND WORDING CONVENTIONS
 The following subsections note some details for preferred formatting and
@@ -993,8 +993,8 @@ parenthetical asides (e.g., like this one).
 Always include periods in such abbreviations, as shown here.
 In addition, "e.g." and "i.e." should always be followed by a comma.
 .SS Em-dashes
-The way to write an em-dash\(emthe glyph that appears
-at either end of this subphrase\(emin *roff is with the macro "\e[em]".
+The way to write an em-dash\[em]the glyph that appears
+at either end of this subphrase\[em]in *roff is with the macro "\e[em]".
 (On an ASCII terminal, an em-dash typically renders as two hyphens,
 but in other typographical contexts it renders as a long dash.)
 Em-dashes should be written
diff --git a/man7/man.7 b/man7/man.7
index fcabbf1fa..65b2c9a66 100644
--- a/man7/man.7
+++ b/man7/man.7
@@ -483,15 +483,15 @@ The Sun macro
 .B TX
 is not implemented.
 .\" .SH AUTHORS
-.\" .IP \(em 3m
+.\" .IP \[em] 3m
 .\" James Clark (jjc@jclark.com) wrote the implementation of the macro package.
-.\" .IP \(em
+.\" .IP \[em]
 .\" Rickard E. Faith (faith@cs.unc.edu) wrote the initial version of
 .\" this manual page.
-.\" .IP \(em
+.\" .IP \[em]
 .\" Jens Schweikhardt (schweikh@noc.fdn.de) wrote the Linux Man-Page Mini-HOWTO
 .\" (which influenced this manual page).
-.\" .IP \(em
+.\" .IP \[em]
 .\" David A. Wheeler (dwheeler@ida.org) heavily modified this
 .\" manual page, such as adding detailed information on sections and macros.
 .SH SEE ALSO
diff --git a/man7/numa.7 b/man7/numa.7
index 81fd51c6f..f5a314b56 100644
--- a/man7/numa.7
+++ b/man7/numa.7
@@ -37,7 +37,7 @@ This file displays information about a process's
 NUMA memory policy and allocation.
 .PP
 Each line contains information about a memory range used by the process,
-displaying\(emamong other information\(emthe effective memory policy for
+displaying\[em]among other information\[em]the effective memory policy for
 that memory range and on which nodes the pages have been allocated.
 .PP
 .I numa_maps
diff --git a/man7/packet.7 b/man7/packet.7
index c42761998..4bfd55d9f 100644
--- a/man7/packet.7
+++ b/man7/packet.7
@@ -492,9 +492,9 @@ By default, packets sent through packet sockets pass through the kernel's
 qdisc (traffic control) layer, which is fine for the vast majority of use
 cases.
 For traffic generator appliances using packet sockets
-that intend to brute-force flood the network\(emfor example,
+that intend to brute-force flood the network\[em]for example,
 to test devices under load in a similar
-fashion to pktgen\(emthis layer can be bypassed by setting
+fashion to pktgen\[em]this layer can be bypassed by setting
 this integer option to 1.
 A side effect is that packet buffering in the qdisc layer is avoided,
 which will lead to increased drops when network
diff --git a/man7/path_resolution.7 b/man7/path_resolution.7
index ec9524d28..74edb6b5f 100644
--- a/man7/path_resolution.7
+++ b/man7/path_resolution.7
@@ -22,7 +22,7 @@ with the
 flag set.
 .PP
 A process may get an entirely private mount namespace in case
-it\(emor one of its ancestors\(emwas started by an invocation of the
+it\[em]or one of its ancestors\[em]was started by an invocation of the
 .BR clone (2)
 system call that had the
 .B CLONE_NEWNS
@@ -31,7 +31,7 @@ This handles the \[aq]/\[aq] part of the pathname.
 .PP
 If the pathname does not start with the \[aq]/\[aq] character, the starting
 lookup directory of the resolution process is the current working directory of
-the process \(em or in the case of
+the process \[em] or in the case of
 .BR openat (2)-style
 system calls, the
 .I dfd
@@ -125,9 +125,9 @@ The lookup of the final component of the pathname goes just like
 that of all other components, as described in the previous step,
 with two differences: (i) the final component need not be a
 directory (at least as far as the path resolution process is
-concerned\(emit may have to be a directory, or a nondirectory, because of
+concerned\[em]it may have to be a directory, or a nondirectory, because of
 the requirements of the specific system call), and (ii) it
-is not necessarily an error if the component is not found\(emmaybe
+is not necessarily an error if the component is not found\[em]maybe
 we are just creating it.
 The details on the treatment
 of the final entry are described in the manual pages of the specific
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index 05415d88a..d32985485 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -82,8 +82,8 @@ and prevents other members of the PID namespace from
 accidentally killing the "init" process.
 .PP
 Likewise, a process in an ancestor namespace
-can\(emsubject to the usual permission checks described in
-.BR kill (2)\(emsend
+can\[em]subject to the usual permission checks described in
+.BR kill (2)\[em]send
 signals to the "init" process of a child PID namespace only
 if the "init" process has established a handler for that signal.
 (Within the handler, the
diff --git a/man7/spufs.7 b/man7/spufs.7
index 2fd2d13d0..39fdf583a 100644
--- a/man7/spufs.7
+++ b/man7/spufs.7
@@ -291,7 +291,7 @@ whenever space is available for writing.
 .TP
 .IR /mbox_stat ", " /ibox_stat ", " /wbox_stat
 These are read-only files that contain the length of the current
-queue of each mailbox\(emthat is, how many words can be read from
+queue of each mailbox\[em]that is, how many words can be read from
 .IR mbox " or " ibox
 or how many words can be written to
 .I wbox
diff --git a/man7/symlink.7 b/man7/symlink.7
index ac758142a..1ddc03976 100644
--- a/man7/symlink.7
+++ b/man7/symlink.7
@@ -297,11 +297,11 @@ which performs a tree traversal, is not.
 (The latter is described in the third area, below.)
 .PP
 If it is explicitly intended that the command operate on the symbolic
-link instead of following the symbolic link\(emfor example, it is desired that
+link instead of following the symbolic link\[em]for example, it is desired that
 .I "chown slink"
 change the ownership of the file that
 .I slink
-is, whether it is a symbolic link or not\(emthen the
+is, whether it is a symbolic link or not\[em]then the
 .I \-h
 option should be used.
 In the above example,
@@ -331,7 +331,7 @@ The
 command is also an exception to this rule.
 For compatibility with historic systems (when
 .BR ls (1)
-is not doing a tree walk\(emthat is,
+is not doing a tree walk\[em]that is,
 .I \-R
 option is not specified),
 the
diff --git a/man7/tcp.7 b/man7/tcp.7
index 1d8a26818..557660293 100644
--- a/man7/tcp.7
+++ b/man7/tcp.7
@@ -1498,7 +1498,7 @@ level
 socket option.
 When this option is enabled, all incoming
 errors are immediately passed to the user program.
-Use this option with care \(em it makes TCP less tolerant to routing
+Use this option with care \[em] it makes TCP less tolerant to routing
 changes and other normal network conditions.
 .SH ERRORS
 .TP
diff --git a/man7/time_namespaces.7 b/man7/time_namespaces.7
index a8006e405..1316bff09 100644
--- a/man7/time_namespaces.7
+++ b/man7/time_namespaces.7
@@ -14,8 +14,8 @@ Time namespaces virtualize the values of two system clocks:
 .B CLOCK_MONOTONIC_COARSE
 and
 .BR CLOCK_MONOTONIC_RAW ),
-a nonsettable clock that represents monotonic time  since\(emas
-described  by  POSIX\(em"some  unspecified  point in the past".
+a nonsettable clock that represents monotonic time  since\[em]as
+described  by  POSIX\[em]"some  unspecified  point in the past".
 .IP \(bu
 .B CLOCK_BOOTTIME
 (and likewise
diff --git a/man7/udplite.7 b/man7/udplite.7
index db5a90103..6e2330340 100644
--- a/man7/udplite.7
+++ b/man7/udplite.7
@@ -33,7 +33,7 @@ If this option is not set, the only difference from UDP is
 in using a different IP protocol identifier (IANA number 136).
 .PP
 The UDP-Lite implementation is a full extension of
-.BR udp (7)\(emthat
+.BR udp (7)\[em]that
 is, it shares the same API and API behavior, and in addition
 offers two socket options to control the checksum coverage.
 .SS Address format
diff --git a/man7/unicode.7 b/man7/unicode.7
index 2e1a605e1..1811de989 100644
--- a/man7/unicode.7
+++ b/man7/unicode.7
@@ -196,8 +196,8 @@ and plane 16 (Supplementary Private Use Area-B, range
 0x100000 to 0x10fffd).
 .SS Literature
 .IP \(bu 3
-Information technology \(em Universal Multiple-Octet Coded Character
-Set (UCS) \(em Part 1: Architecture and Basic Multilingual Plane.
+Information technology \[em] Universal Multiple-Octet Coded Character
+Set (UCS) \[em] Part 1: Architecture and Basic Multilingual Plane.
 International Standard ISO/IEC 10646-1, International Organization
 for Standardization, Geneva, 2000.
 .IP
diff --git a/man7/uri.7 b/man7/uri.7
index 2767d9f12..7528f771f 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -523,8 +523,8 @@ the HTML 4.01 specification (section B.2) and
 IETF RFC\~3986 (last paragraph of section 2.5)
 recommend the following approach:
 .IP (1) 5
-translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee
-.BR utf\-8 (7)\(emand
+translate the character sequences into UTF-8 (IETF RFC\~3629)\[em]see
+.BR utf\-8 (7)\[em]and
 then
 .IP (2)
 use the URI escaping mechanism, that is,
diff --git a/man7/user-keyring.7 b/man7/user-keyring.7
index a6e29c9db..f384774fd 100644
--- a/man7/user-keyring.7
+++ b/man7/user-keyring.7
@@ -60,9 +60,9 @@ excepting that the keyring is destroyed when the UID record is destroyed when
 the last process pinning it exits.
 .PP
 If it is necessary for a key associated with a user to exist beyond the UID
-record being garbage collected\(emfor example, for use by a
+record being garbage collected\[em]for example, for use by a
 .BR cron (8)
-script\(emthen the
+script\[em]then the
 .BR persistent\-keyring (7)
 should be used instead.
 .PP
diff --git a/man7/user-session-keyring.7 b/man7/user-session-keyring.7
index bd0ba3d23..edecb84aa 100644
--- a/man7/user-session-keyring.7
+++ b/man7/user-session-keyring.7
@@ -66,8 +66,8 @@ If a user session keyring does not exist when it is accessed,
 it will be created.
 .PP
 Rather than relying on the user session keyring,
-it is strongly recommended\(emespecially if the process
-is running as root\(emthat a
+it is strongly recommended\[em]especially if the process
+is running as root\[em]that a
 .BR session\-keyring (7)
 be set explicitly, for example by
 .BR pam_keyinit (8).
diff --git a/man7/user_namespaces.7 b/man7/user_namespaces.7
index 894635008..d968769dc 100644
--- a/man7/user_namespaces.7
+++ b/man7/user_namespaces.7
@@ -35,8 +35,8 @@ but is unprivileged for operations outside the namespace.
 .\"
 .SS Nested namespaces, namespace membership
 User namespaces can be nested;
-that is, each user namespace\(emexcept the initial ("root")
-namespace\(emhas a parent user namespace,
+that is, each user namespace\[em]except the initial ("root")
+namespace\[em]has a parent user namespace,
 and can have zero or more child user namespaces.
 The parent user namespace is the user namespace
 of the process that creates the user namespace via a call to
@@ -431,11 +431,11 @@ that created this user namespace.
 The length of the range of user IDs that is mapped between the two
 user namespaces.
 .PP
-System calls that return user IDs (group IDs)\(emfor example,
+System calls that return user IDs (group IDs)\[em]for example,
 .BR getuid (2),
 .BR getgid (2),
 and the credential fields in the structure returned by
-.BR stat (2)\(emreturn
+.BR stat (2)\[em]return
 the user ID (group ID) mapped into the caller's user namespace.
 .PP
 When a process accesses a file, its user and group IDs
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 797481cac..abdf6244c 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -15,7 +15,7 @@ The Unicode 3.0 character set occupies a 16-bit code space.
 The most obvious
 Unicode encoding (known as UCS-2)
 consists of a sequence of 16-bit words.
-Such strings can contain\(emas part of many 16-bit characters\(embytes
+Such strings can contain\[em]as part of many 16-bit characters\[em]bytes
 such as \[aq]\e0\[aq] or \[aq]/\[aq], which have a
 special meaning in filenames and other C library function arguments.
 In addition, the majority of UNIX tools expect ASCII files and can't
@@ -25,7 +25,7 @@ UCS-2 is not a suitable external encoding of Unicode
 in filenames, text files, environment variables, and so on.
 The ISO 10646 Universal Character Set (UCS),
 a superset of Unicode, occupies an even larger code
-space\(em31\ bits\(emand the obvious
+space\[em]31\ bits\[em]and the obvious
 UCS-4 encoding for it (a sequence of 32-bit words) has the same problems.
 .PP
 The UTF-8 encoding of Unicode and UCS
diff --git a/man7/vdso.7 b/man7/vdso.7
index 2cb3b9636..9bfac91b1 100644
--- a/man7/vdso.7
+++ b/man7/vdso.7
@@ -69,9 +69,9 @@ One frequently used system call is
 This system call is called both directly by user-space applications
 as well as indirectly by
 the C library.
-Think timestamps or timing loops or polling\(emall of these
+Think timestamps or timing loops or polling\[em]all of these
 frequently need to know what time it is right now.
-This information is also not secret\(emany application in any
+This information is also not secret\[em]any application in any
 privilege mode (root or any unprivileged user) will get the same answer.
 Thus the kernel arranges for the information required to answer
 this question to be placed in memory the process can access.
@@ -252,7 +252,7 @@ a fixed location in memory.
 User-space applications then call directly into that region.
 There is no provision for backward compatibility
 beyond sniffing raw opcodes,
-but as this is an embedded CPU, it can get away with things\(emsome of the
+but as this is an embedded CPU, it can get away with things\[em]some of the
 object formats it runs aren't even ELF based (they're bFLT/FLAT).
 .PP
 For information on this code page,
@@ -588,7 +588,7 @@ __vdso_time	LINUX_2.6
 .ft P
 \}
 .SS History
-The vDSO was originally just a single function\(emthe vsyscall.
+The vDSO was originally just a single function\[em]the vsyscall.
 In older kernels, you might see that name
 in a process's memory map rather than "vdso".
 Over time, people realized that this mechanism
diff --git a/man7/x25.7 b/man7/x25.7
index 9cebe7cf2..446d314cf 100644
--- a/man7/x25.7
+++ b/man7/x25.7
@@ -29,7 +29,7 @@ X25 sockets can also be used for communication
 without an intermediate X.25 network (X.25 DTE-DTE mode) as described
 in ISO-8208.
 .PP
-Message boundaries are preserved \(em a
+Message boundaries are preserved \[em] a
 .BR read (2)
 from a socket will
 retrieve the same chunk of data as output with the corresponding
diff --git a/man7/xattr.7 b/man7/xattr.7
index b5057270c..51fe4c8d7 100644
--- a/man7/xattr.7
+++ b/man7/xattr.7
@@ -21,7 +21,7 @@ associated with all inodes in the system (i.e., the
 .BR stat (2)
 data).
 They are often used to provide additional functionality
-to a filesystem\(emfor example, additional security features such as
+to a filesystem\[em]for example, additional security features such as
 Access Control Lists (ACLs) may be implemented using extended attributes.
 .PP
 Users with search access to a file or directory may use
diff --git a/man8/ld.so.8 b/man8/ld.so.8
index 9c2ec807d..05f66ae3d 100644
--- a/man8/ld.so.8
+++ b/man8/ld.so.8
@@ -474,9 +474,9 @@ and there is no support for escaping the separator.
 is ignored in secure-execution mode.
 .IP
 The dynamic linker will notify the audit
-shared objects at so-called auditing checkpoints\(emfor example,
+shared objects at so-called auditing checkpoints\[em]for example,
 loading a new shared object, resolving a symbol,
-or calling a symbol from another shared object\(emby
+or calling a symbol from another shared object\[em]by
 calling an appropriate function within the audit shared object.
 For details, see
 .BR rtld\-audit (7).