intro.1, fork.2, futex.2, open.2, rename.2, select_tut.2, semop.2, spu_create.2, stat.2, netlink.3, random.3, scanf.3, shm_open.3, strftime.3, console.4, console_codes.4, sk98lin.4, st.4, bootparam.7, cpuset.7, credentials.7, man-pages.7, path_resolution.7, uri.7: Global fix: remove spaces around em-dash

Normal English typographical convention is not to have
spaces around em dashes.

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

man1/intro.1

@@ -135,7 +135,7 @@ maja    0501\-1136285
 and here typing Control-D ended the session.
 The
 .B "% "
-here was the command prompt \(em it is the shell's way of indicating
+here was the command prompt\(emit 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,
@@ -151,7 +151,7 @@ We see that there are commands
 .LP
 The command
 .I ls
-lists the contents of the current directory \(em it tells you what
+lists the contents of the current directory\(emit tells you what
 files you have.
 With a
 .I \-l

man2/fork.2

@@ -118,7 +118,7 @@ The termination signal of the child is always
 .PP
 Note the following further points:
 .IP * 3
-The child process is created with a single thread \(em the
+The child process is created with a single thread\(emthe
 one that called
 .BR fork ().
 The entire virtual address space of the parent is replicated in the child,

man2/futex.2

@@ -242,7 +242,7 @@ A 4-argument system call with the semantics
 described in this page was introduced in Linux 2.5.40.
 In Linux 2.5.70 one argument
 was added.
-In Linux 2.6.7 a sixth argument was added \(em messy, especially
+In Linux 2.6.7 a sixth argument was added\(emmessy, especially
 on the s390 architecture.
 .SH "CONFORMING TO"
 This system call is Linux-specific.

man2/open.2

@@ -403,9 +403,9 @@ One example is NFS, where the server maintains the access time.
 .B O_NOCTTY
 If
 .I pathname
-refers to a terminal device \(em see
-.BR tty (4)
-\(em it will not become the process's controlling terminal even if the
+refers to a terminal device\(emsee
+.BR tty (4)\(em
+it will not become the process's controlling terminal even if the
 process does not have one.
 .TP
 .B O_NOFOLLOW
@@ -835,7 +835,7 @@ as a performance option which is disabled by default.
 .RS
 "The thing that has always disturbed me about O_DIRECT is that the whole
 interface is just stupid, and was probably designed by a deranged monkey
-on some serious mind-controlling substances." \(em Linus
+on some serious mind-controlling substances."\(emLinus
 .RE
 .SH BUGS
 Currently, it is not possible to enable signal-driven

man2/rename.2

@@ -125,8 +125,8 @@ this an error.
 (Note that there is no requirement to return
 .B EBUSY
 in such
-cases \(em there is nothing wrong with doing the rename anyway \(em
-but it is allowed to return
+cases\(emthere is nothing wrong with doing the rename anyway\(embut
+it is allowed to return
 .B EBUSY
 if the system cannot otherwise
 handle such situations.)

man2/select_tut.2

@@ -811,7 +811,7 @@ inefficient timeouts.
 
 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 \(em one for each connection.
+of buffers\(emone for each connection.
 At the moment, new
 connections cause the current connection to be dropped.
 .SH SEE ALSO

man2/semop.2

@@ -126,7 +126,7 @@ Furthermore, if
 is specified for this operation, the system updates the process undo count
 .RI ( semadj )
 for this semaphore.
-This operation can always proceed \(em it never forces a process to wait.
+This operation can always proceed\(emit never forces a process to wait.
 The calling process must have alter permission on the semaphore set.
 .PP
 If

man2/spu_create.2

@@ -87,7 +87,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 \(em priority and policy.
+parameters\(empriority and policy.
 In the future, gang scheduling may be implemented causing
 the group to be switched in and out as a single unit.)
 

man2/stat.2

@@ -72,7 +72,7 @@ _XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED
 .SH DESCRIPTION
 .PP
 These functions return information about a file.
-No permissions are required on the file itself, but \(em in the case of
+No permissions are required on the file itself, but\(emin the case of
 .BR stat ()
 and
 .BR lstat ()

man3/netlink.3

@@ -65,7 +65,7 @@ The caller must check if the current
 .I nlmsghdr
 didn't have the
 .B NLMSG_DONE
-set \(em this function doesn't return NULL on end.
+set\(emthis function doesn't return NULL on end.
 The
 .I len
 argument is an lvalue containing the remaining length

man3/random.3

@@ -92,7 +92,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 \(em the larger the state array,
+random number generator it should use\(emthe larger the state array,
 the better the random numbers will be.
 \fIseed\fP is the seed for the
 initialization, which specifies a starting point for the random number

man3/scanf.3

@@ -175,7 +175,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 \(em this is a
+the conversion fails\(emthis is a
 .IR "matching failure" .
 .PP
 Each

man3/shm_open.3

@@ -108,7 +108,7 @@ is listed in
 (Symbolic definitions of these constants can be obtained by including
 .IR <sys/stat.h> .)
 .sp
-A new shared memory object initially has zero length \(em the size of the
+A new shared memory object initially has zero length\(emthe size of the
 object can be set using
 .BR ftruncate (2).
 The newly allocated bytes of a shared memory
@@ -260,7 +260,7 @@ and
 .B O_TRUNC
 unspecified.
 On Linux, this will successfully truncate an existing
-shared memory object \(em this may not be so on other UNIX systems.
+shared memory object\(emthis may not be so on other UNIX systems.
 .LP
 The POSIX shared memory object implementation on Linux 2.4 makes use
 of a dedicated file system, which is normally

man3/strftime.3

@@ -88,7 +88,7 @@ The day of the month as a decimal number (range 01 to 31).
 .B %D
 Equivalent to
 .BR %m/%d/%y .
-(Yecch \(em for Americans only.
+(Yecch\(emfor Americans only.
 Americans should note that in other countries
 .B %d/%m/%y
 is rather common.

man4/console.4

@@ -41,7 +41,7 @@ on the console;
 (b) ask
 .BR openvt (1)
 to start a process on the console;
-(c) start X \(em it will find the first unused console,
+(c) start X\(emit will find the first unused console,
 and display its output there.
 (There is also the ancient
 .BR doshell (8).)

man4/console_codes.4

@@ -342,14 +342,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) \(em see below.
+0)\(emsee 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) \(em see below.
+to 0)\(emsee below.
 .\"
 .PP
 .B Linux Console Private CSI Sequences

man4/sk98lin.4

@@ -469,13 +469,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 \(em at a later time \(em the CPU utilization decreases
+If\(emat a later time\(emthe CPU utilization decreases
 again (or if the network load is negligible) the interrupt
 moderation will automatically be disabled.
 
 Interrupt moderation should be used when the driver has to
 handle one or more interfaces with a high network load,
-which \(em as a consequence \(em leads also to a high CPU utilization.
+which\(emas a consequence\(emleads also to a high CPU utilization.
 When moderation is applied in such high network load situations,
 CPU load might be reduced by 20-30% on slow computers.
 

man4/st.4

@@ -345,7 +345,7 @@ is enabled for the drive (see
 below).
 .TP
 .B MTNOP
-No op \(em flushes the driver's buffer as a side effect.
+No op\(emflushes the driver's buffer as a side effect.
 Should be used before reading status with
 .BR MTIOCGET .
 .TP

man7/bootparam.7

@@ -187,7 +187,7 @@ the device type ('hd' for ST-506 compatible hard disk, with Y in
 \&'ad' for Atari ACSI disk, with Y in 'a'-'e',
 \&'ez' for a Syquest EZ135 parallel port removable drive, with Y='a',
 \&'xd' for XT compatible disk, with Y either 'a' or 'b'; 'fd' for
-floppy disk, with Y the floppy drive number \(em fd0 would be
+floppy disk, with Y the floppy drive number\(emfd0 would be
 the DOS 'A:' drive, and fd1 would be 'B:'), Y the driver letter or
 number, and N the number (in decimal) of the partition on this device
 (absent in the case of floppies).
@@ -367,8 +367,8 @@ For kernel tuners only.
 .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 \(em
-the system will use available memory more efficiently itself.
+In general it is a bad idea to use a ramdisk under Linux\(emthe
+system will use available memory more efficiently itself.
 But while booting (or while constructing boot floppies)
 it is often useful to load the floppy contents into a
 ramdisk.

man7/cpuset.7

@@ -548,8 +548,8 @@ single read, instead of having to read and accumulate results
 for a period of time.
 .IP *
 Because this meter is per-cpuset rather than per-process,
-the batch scheduler can obtain the key information \(em memory
-pressure in a cpuset \(em with a single read, rather than having to
+the batch scheduler can obtain the key information\(emmemory
+pressure in a cpuset\(emwith a single read, rather than having to
 query and accumulate results over all the (dynamically changing)
 set of processes in the cpuset.
 .PP

man7/credentials.7

@@ -210,7 +210,7 @@ the effective and saved set IDs may be changed, as described in
 Aside from the purposes noted above,
 a process's user IDs are also employed in a number of other contexts:
 .IP * 3
-when determining the permissions for sending signals \(em see
+when determining the permissions for sending signals\(emsee
 .BR kill (2);
 .IP *
 when determining the permissions for setting

man7/man-pages.7

@@ -117,7 +117,7 @@ The section number in which the man page should be placed (e.g.,
 .IR 7 ).
 .TP
 .I date
-The date of the last revision \(em remember to change this every time a
+The date of the last revision\(emremember to change this every time a
 change is made to the man page,
 since this is the most general way of doing version control.
 Dates should be written in the form YYYY-MM-DD.

man7/path_resolution.7

@@ -39,7 +39,7 @@ by use of the
 .BR chroot (2)
 system call.
 A process may get an entirely private mount namespace in case
-it \(em or one of its ancestors \(em was started by an invocation of the
+it\(emor one of its ancestors\(emwas started by an invocation of the
 .BR clone (2)
 system call that had the
 .B CLONE_NEWNS
@@ -109,11 +109,11 @@ exceeded ("Too many levels of symbolic links").
 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 \(em
-it may have to be a directory, or a nondirectory, because of
+directory (at least as far as the path resolution process is
+concerned\(emit 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 \(em
-maybe we are just creating it.
+is not necessarily an error if the component is not found\(emmaybe
+we are just creating it.
 The details on the treatment
 of the final entry are described in the manual pages of the specific
 system calls.

man7/uri.7

@@ -526,9 +526,9 @@ For URIs which must handle characters outside the US ASCII character set,
 the HTML 4.01 specification (section B.2) and
 IETF RFC\ 2718 (section 2.2.5) recommend the following approach:
 .IP 1. 4
-translate the character sequences into UTF-8 (IETF RFC\ 2279) \(em see
-.BR utf-8 (7)
-\(em and then
+translate the character sequences into UTF-8 (IETF RFC\ 2279)\(emsee
+.BR utf-8 (7)\(emand
+then
 .IP 2.
 use the URI escaping mechanism, that is,
 use the %HH encoding for unsafe octets.