Various pages: use "\-" to generate real minus in circumstances where appropriate

Use \- for math formulas, pathnames, manual page cross references,
etc.

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

man1/ldd.1

@@ -59,9 +59,9 @@ For each dependency,
 displays the location of the matching object
 and the (hexadecimal) address at which it is loaded.
 (The
-.I linux-vdso
+.I linux\-vdso
 and
-.I ld-linux
+.I ld\-linux
 shared dependencies are special; see
 .BR vdso (7)
 and
@@ -70,7 +70,7 @@ and
 .SS Security
 Be aware that in some circumstances
 (e.g., where the program specifies an ELF interpreter other than
-.IR ld-linux.so ),
+.IR ld\-linux.so ),
 .\" The circumstances are where the program has an interpreter
 .\" other than ld-linux.so. In this case, ldd tries to execute the
 .\" program directly with LD_TRACE_LOADED_OBJECTS=1, with the

man1/locale.1

@@ -73,7 +73,7 @@ The
 command can also be provided with one or more arguments,
 which are the names of locale keywords (for example,
 .IR date_fmt ,
-.IR ctype-class-names ,
+.IR ctype\-class\-names ,
 .IR yesexpr ,
 or
 .IR decimal_point )

man1/localedef.1

@@ -113,7 +113,7 @@ not already been created.
 If no
 .I charmapfile
 is given, the value
-.I ANSI_X3.4-1968
+.I ANSI_X3.4\-1968
 (for ASCII) is used by default.
 If no
 .I inputfile

man2/add_key.2

@@ -69,23 +69,23 @@ Alternatively, it may be one of the following special keyring IDs:
 .TP
 .B KEY_SPEC_THREAD_KEYRING
 This specifies the caller's thread-specific keyring
-.RB ( thread-keyring (7)).
+.RB ( thread\-keyring (7)).
 .TP
 .B KEY_SPEC_PROCESS_KEYRING
 This specifies the caller's process-specific keyring
-.RB ( process-keyring (7)).
+.RB ( process\-keyring (7)).
 .TP
 .B KEY_SPEC_SESSION_KEYRING
 This specifies the caller's session-specific keyring
-.RB ( session-keyring (7)).
+.RB ( session\-keyring (7)).
 .TP
 .B KEY_SPEC_USER_KEYRING
 This specifies the caller's UID-specific keyring
-.RB ( user-keyring (7)).
+.RB ( user\-keyring (7)).
 .TP
 .B KEY_SPEC_USER_SESSION_KEYRING
 This specifies the caller's UID-session keyring
-.RB ( user-session-keyring (7)).
+.RB ( user\-session\-keyring (7)).
 .SS Key types
 The key
 .I type

man2/bpf.2

@@ -323,7 +323,7 @@ bpf_map_lookup_elem(map_fd, void *key)
 expects to read 8 bytes from the location pointed to by
 .IR key ,
 but the
-.I fp\ -\ 4
+.I fp\ \-\ 4
 (where
 .I fp
 is the top of the stack)

man2/cacheflush.2

@@ -41,7 +41,7 @@ flushes the contents of the indicated cache(s) for the
 user addresses in the range
 .I addr
 to
-.IR (addr+nbytes-1) .
+.IR (addr+nbytes\-1) .
 .I cache
 may be one of:
 .TP
@@ -66,7 +66,7 @@ to indicate the error.
 Some or all of the address range
 .I addr
 to
-.I (addr+nbytes-1)
+.I (addr+nbytes\-1)
 is not accessible.
 .TP
 .B EINVAL

man2/capget.2

@@ -114,7 +114,7 @@ For
 .BR capget ()
 calls, one can probe the capabilities of any process by specifying its
 process ID with the
-.I hdrp->pid
+.I hdrp\->pid
 field value.
 .PP
 For details on the data, see
@@ -129,7 +129,7 @@ asynchronously setting the capabilities of another.
 That is, on kernels that have VFS capabilities support, when calling
 .BR capset (),
 the only permitted values for
-.I hdrp->pid
+.I hdrp\->pid
 are 0 or, equivalently, the value returned by
 .BR gettid (2).
 .\"

man2/fcntl.2

@@ -2114,7 +2114,7 @@ It is therefore inadvisable to rely on mandatory locking.
 .BR lslocks (8)
 .PP
 .IR locks.txt ,
-.IR mandatory-locking.txt ,
+.IR mandatory\-locking.txt ,
 and
 .I dnotify.txt
 in the Linux kernel source directory
@@ -2122,6 +2122,6 @@ in the Linux kernel source directory
 (on older kernels, these files are directly under the
 .I Documentation/
 directory, and
-.I mandatory-locking.txt
+.I mandatory\-locking.txt
 is called
 .IR mandatory.txt )

man2/kexec_load.2

@@ -300,7 +300,7 @@ Two or more of the kernel target buffers overlap.
 .TP
 .B EINVAL
 The value in
-.I cmdline[cmdline_len-1]
+.I cmdline[cmdline_len\-1]
 is not \(aq\e0\(aq.
 .TP
 .B EINVAL

man2/keyctl.2

@@ -940,27 +940,27 @@ otherwise the user-specific keyring.
 .TP
 .BR KEY_REQKEY_DEFL_THREAD_KEYRING
 Use the thread-specific keyring
-.RB ( thread-keyring (7))
+.RB ( thread\-keyring (7))
 as the new default keyring.
 .TP
 .BR KEY_REQKEY_DEFL_PROCESS_KEYRING
 Use the process-specific keyring
-.RB ( process-keyring (7))
+.RB ( process\-keyring (7))
 as the new default keyring.
 .TP
 .BR KEY_REQKEY_DEFL_SESSION_KEYRING
 Use the session-specific keyring
-.RB ( session-keyring (7))
+.RB ( session\-keyring (7))
 as the new default keyring.
 .TP
 .BR KEY_REQKEY_DEFL_USER_KEYRING
 Use the UID-specific keyring
-.RB ( user-keyring (7))
+.RB ( user\-keyring (7))
 as the new default keyring.
 .TP
 .BR KEY_REQKEY_DEFL_USER_SESSION_KEYRING
 Use the UID-specific session keyring
-.RB ( user-session-keyring (7))
+.RB ( user\-session\-keyring (7))
 as the new default keyring.
 .TP
 .BR KEY_REQKEY_DEFL_REQUESTOR_KEYRING " (since Linux 2.6.29)"
@@ -1357,7 +1357,7 @@ via the function
 .BR KEYCTL_GET_PERSISTENT " (since Linux 3.13)"
 .\" commit f36f8c75ae2e7d4da34f4c908cebdb4aa42c977e
 Get the persistent keyring
-.RB ( persistent-keyring (7))
+.RB ( persistent\-keyring (7))
 for a specified user and link it to a specified keyring.
 .IP
 The user ID is specified in

man2/migrate_pages.2

@@ -167,7 +167,7 @@ nodes used by
 The
 .I <numaif.h>
 header is not included with glibc, but requires installing
-.I libnuma-devel
+.I libnuma\-devel
 or a similar package.
 .SH SEE ALSO
 .BR get_mempolicy (2),

man2/move_pages.2

@@ -245,7 +245,7 @@ nodes used by
 The
 .I <numaif.h>
 header is not included with glibc, but requires installing
-.I libnuma-devel
+.I libnuma\-devel
 or a similar package.
 .SH SEE ALSO
 .BR get_mempolicy (2),

man2/open.2

@@ -1208,7 +1208,7 @@ The usual scenario here is that an application compiled
 on a 32-bit platform without
 .I \-D_FILE_OFFSET_BITS=64
 tried to open a file whose size exceeds
-.I (1<<31)-1
+.I (1<<31)\-1
 bytes;
 see also
 .B O_LARGEFILE

man2/open_by_handle_at.2

@@ -101,12 +101,12 @@ field is updated to contain the number of bytes actually written to
 The caller can discover the required size for the
 .I file_handle
 structure by making a call in which
-.IR handle->handle_bytes
+.IR handle\->handle_bytes
 is zero;
 in this case, the call fails with the error
 .BR EOVERFLOW
 and
-.IR handle->handle_bytes
+.IR handle\->handle_bytes
 is set to indicate the required size;
 the caller can then use this information to allocate a structure
 of the correct size (see EXAMPLES below).
@@ -334,10 +334,10 @@ The filesystem does not support decoding of a pathname to a file handle.
 .TP
 .B EOVERFLOW
 The
-.I handle->handle_bytes
+.I handle\->handle_bytes
 value passed into the call was too small.
 When this error occurs,
-.I handle->handle_bytes
+.I handle\->handle_bytes
 is updated to indicate the required size for the handle.
 .\"
 .\"
@@ -354,7 +354,7 @@ is not an open file descriptor.
 points outside your accessible address space.
 .TP
 .B EINVAL
-.I handle->handle_bytes
+.I handle\->handle_bytes
 is greater than
 .BR MAX_HANDLE_SZ
 or is equal to zero.
@@ -759,7 +759,7 @@ The
 and
 .I libmount
 documentation in the latest
-.I util-linux
+.I util\-linux
 release at
 .UR https://www.kernel.org/pub/linux/utils/util\-linux/
 .UE

man2/ptrace.2

@@ -1788,7 +1788,7 @@ by examining registers.
 For example, on x86,
 .I rax
 ==
-.RB - ENOSYS
+.RB \- ENOSYS
 in syscall-enter-stop.
 Since
 .B SIGTRAP
@@ -1798,7 +1798,7 @@ syscall-exit-stop,
 and at this point
 .I rax
 almost never contains
-.RB - ENOSYS ,
+.RB \- ENOSYS ,
 the
 .B SIGTRAP
 looks like "syscall-stop which is not syscall-enter-stop";

man2/rt_sigqueueinfo.2

@@ -162,7 +162,7 @@ For the required permissions, see
 .B EPERM
 .I tgid
 specifies a process other than the caller and
-.I info->si_code
+.I info\->si_code
 is invalid.
 .TP
 .B ESRCH

man2/stat.2

@@ -428,7 +428,7 @@ an application compiled on a 32-bit platform without
 calls
 .BR stat ()
 on a file whose size exceeds
-.I (1<<31)-1
+.I (1<<31)\-1
 bytes.
 .PP
 The following additional errors can occur for

man2/sync_file_range.2

@@ -56,7 +56,7 @@ through to the end of file are synchronized.
 Synchronization is in units of the system page size:
 .I offset
 is rounded down to a page boundary;
-.I (offset+nbytes-1)
+.I (offset+nbytes\-1)
 is rounded up to a page boundary.
 .PP
 The

man2/timer_settime.2

@@ -88,7 +88,7 @@ that was specified when the timer was created by
 .BR timer_create (2).
 .PP
 If
-.I new_value->it_value
+.I new_value\->it_value
 specifies a nonzero value (i.e., either subfield is nonzero), then
 .BR timer_settime ()
 arms (starts) the timer,
@@ -96,25 +96,25 @@ setting it to initially expire at the given time.
 (If the timer was already armed,
 then the previous settings are overwritten.)
 If
-.I new_value->it_value
+.I new_value\->it_value
 specifies a zero value
 (i.e., both subfields are zero),
 then the timer is disarmed.
 .PP
 The
-.I new_value->it_interval
+.I new_value\->it_interval
 field specifies the period of the timer, in seconds and nanoseconds.
 If this field is nonzero, then each time that an armed timer expires,
 the timer is reloaded from the value specified in
-.IR new_value->it_interval .
+.IR new_value\->it_interval .
 If
-.I new_value->it_interval
+.I new_value\->it_interval
 specifies a zero value,
 then the timer expires just once, at the time specified by
 .IR it_value .
 .PP
 By default, the initial expiration time specified in
-.I new_value->it_value
+.I new_value\->it_value
 is interpreted relative to the current time on the timer's
 clock at the time of the call.
 This can be modified by specifying
@@ -122,11 +122,11 @@ This can be modified by specifying
 in
 .IR flags ,
 in which case
-.I new_value->it_value
+.I new_value\->it_value
 is interpreted as an absolute value as measured on the timer's clock;
 that is, the timer will expire when the clock value reaches the
 value specified by
-.IR new_value->it_value .
+.IR new_value\->it_value .
 If the specified absolute time has already passed,
 then the timer expires immediately,
 and the overrun count (see
@@ -148,10 +148,10 @@ If
 .I old_value
 is not NULL, then it points to a buffer
 that is used to return the previous interval of the timer (in
-.IR old_value->it_interval )
+.IR old_value\->it_interval )
 and the amount of time until the timer
 would previously have next expired (in
-.IR old_value->it_value ).
+.IR old_value\->it_value ).
 .PP
 .BR timer_gettime ()
 returns the time until next expiration, and the interval,
@@ -160,17 +160,17 @@ for the timer specified by
 in the buffer pointed to by
 .IR curr_value .
 The time remaining until the next timer expiration is returned in
-.IR curr_value->it_value ;
+.IR curr_value\->it_value ;
 this is always a relative value, regardless of whether the
 .BR TIMER_ABSTIME
 flag was used when arming the timer.
 If the value returned in
-.IR curr_value->it_value
+.IR curr_value\->it_value
 is zero, then the timer is currently disarmed.
 The timer interval is returned in
-.IR curr_value->it_interval .
+.IR curr_value\->it_interval .
 If the value returned in
-.IR curr_value->it_interval
+.IR curr_value\->it_interval
 is zero, then this is a "one-shot" timer.
 .SH RETURN VALUE
 On success,

man3/CPU_SET.3

@@ -188,12 +188,12 @@ The following macros are used to allocate and deallocate CPU sets:
 .BR CPU_ALLOC ()
 Allocate a CPU set large enough to hold CPUs
 in the range 0 to
-.IR num_cpus-1 .
+.IR num_cpus\-1 .
 .TP
 .BR CPU_ALLOC_SIZE ()
 Return the size in bytes of the CPU set that would be needed to
 hold CPUs in the range 0 to
-.IR num_cpus-1 .
+.IR num_cpus\-1 .
 This macro provides the value that can be used for the
 .I setsize
 argument in the

man3/bindresvport.3

@@ -89,7 +89,7 @@ All privileged ports are in use.
 .BR EAFNOSUPPORT " (" EPFNOSUPPORT " in glibc 2.7 and earlier)"
 .I sin
 is not NULL and
-.I sin->sin_family
+.I sin\->sin_family
 is not
 .BR AF_INET .
 .SH ATTRIBUTES

man3/crypt.3

@@ -129,7 +129,7 @@ The structure pointed to by
 is used to store result data and bookkeeping information.
 Other than allocating it,
 the only thing that the caller should do with this structure is to set
-.I data->initialized
+.I data\->initialized
 to zero before the first call to
 .BR crypt_r ().
 .SH RETURN VALUE

man3/dladdr.3

@@ -217,9 +217,9 @@ If the address specified in
 .I addr
 could be matched to a shared object,
 but not to a symbol in the shared object, then the
-.I info->dli_sname
+.I info\->dli_sname
 and
-.I info->dli_saddr
+.I info\->dli_saddr
 fields are set to NULL.
 .PP
 If the address specified in

man3/expm1.3

@@ -100,10 +100,10 @@ is negative infinity, \-1 is returned.
 .PP
 If the result overflows, a range error occurs,
 and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 .SH ERRORS
 See

man3/killpg.3

@@ -128,7 +128,7 @@ only when the permission check failed for all target processes.
 On Linux,
 .BR killpg ()
 is implemented as a library function that makes the call
-.IR "kill(-pgrp,\ sig)" .
+.IR "kill(\-pgrp,\ sig)" .
 .SH SEE ALSO
 .BR getpgrp (2),
 .BR kill (2),

man3/lockf.3

@@ -183,12 +183,12 @@ POSIX.1-2001, POSIX.1-2008, SVr4.
 .PP
 .I locks.txt
 and
-.I mandatory-locking.txt
+.I mandatory\-locking.txt
 in the Linux kernel source directory
 .IR Documentation/filesystems
 (on older kernels, these files are directly under the
 .I Documentation
 directory, and
-.I mandatory-locking.txt
+.I mandatory\-locking.txt
 is called
 .IR mandatory.txt )

man3/log.3

@@ -84,10 +84,10 @@ If
 .I x
 is zero,
 then a pole error occurs, and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 .PP
 If

man3/log1p.3

@@ -89,10 +89,10 @@ If
 .I x
 is \-1, a pole error occurs,
 and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 .PP
 If

man3/logb.3

@@ -98,10 +98,10 @@ a NaN is returned.
 If
 .I x
 is zero, then a pole error occurs, and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 .PP
 If

man3/nan.3

@@ -41,7 +41,7 @@ If the implementation does not support
 quiet NaNs, these functions return zero.
 .PP
 The call
-.I nan("char-sequence")
+.I nan("char\-sequence")
 is equivalent to:
 .PP
 .in +4n

man3/pthread_join.3

@@ -134,7 +134,7 @@ and when enough zombie threads have accumulated,
 it will no longer be possible to create new threads (or processes).
 .PP
 There is no pthreads analog of
-.IR "waitpid(-1,\ &status,\ 0)" ,
+.IR "waitpid(\-1,\ &status,\ 0)" ,
 that is, "join with any terminated thread".
 If you believe you need this functionality,
 you probably need to rethink your application design.

man3/setlocale.3

@@ -147,9 +147,9 @@ is an ISO 639 language code,
 is an ISO 3166 country code, and
 .I codeset
 is a character set or encoding identifier like
-.B "ISO-8859-1"
+.B "ISO\-8859\-1"
 or
-.BR "UTF-8" .
+.BR "UTF\-8" .
 For a list of all supported locales, try "locale \-a" (see
 .BR locale (1)).
 .PP

man3/y0.3

@@ -132,10 +132,10 @@ If
 is negative,
 a domain error occurs,
 and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 (POSIX.1-2001 also allows a NaN return for this case.)
 .PP
@@ -144,10 +144,10 @@ If
 is 0.0,
 a pole error occurs,
 and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 .PP
 If the result underflows,
@@ -157,10 +157,10 @@ and the functions return 0.0
 If the result overflows,
 a range error occurs,
 and the functions return
-.RB - HUGE_VAL ,
-.RB - HUGE_VALF ,
+.RB \- HUGE_VAL ,
+.RB \- HUGE_VALF ,
 or
-.RB - HUGE_VALL ,
+.RB \- HUGE_VALL ,
 respectively.
 (POSIX.1-2001 also allows a 0.0 return for this case.)
 .SH ERRORS

man5/elf.5

@@ -1290,7 +1290,7 @@ This section is of type
 .BR SHT_NOTE .
 No attribute types are used.
 .TP
-.IR .note.ABI-tag
+.IR .note.ABI\-tag
 This section is used to declare the expected run-time ABI of the ELF image.
 It may include the operating system name and its run-time versions.
 This section is of type
@@ -1298,7 +1298,7 @@ This section is of type
 The only attribute used is
 .BR SHF_ALLOC .
 .TP
-.IR .note.gnu.build-id
+.IR .note.gnu.build\-id
 This section is used to hold an ID that uniquely identifies
 the contents of the ELF image.
 Different files with the same build ID should contain the same executable
@@ -1311,7 +1311,7 @@ This section is of type
 The only attribute used is
 .BR SHF_ALLOC .
 .TP
-.IR .note.GNU-stack
+.IR .note.GNU\-stack
 This section is used in Linux object files for declaring stack attributes.
 This section is of type
 .BR SHT_PROGBITS .

man5/locale.5

@@ -494,11 +494,11 @@ The following keywords are allowed:
 followed by the number representing used collation levels.
 This keyword is recognized but ignored by glibc.
 .TP
-.I collating-element
+.I collating\-element
 followed by the definition of a collating-element symbol
 representing a multicharacter collating element.
 .TP
-.I collating-symbol
+.I collating\-symbol
 followed by the definition of a collating symbol
 that can be used in collation order statements.
 .TP
@@ -514,22 +514,22 @@ to be evaluated in an
 .I endif
 construct.
 .TP
-.I reorder-after
+.I reorder\-after
 followed by a redefinition of a collation rule.
 .TP
-.I reorder-end
+.I reorder\-end
 marks the end of the redefinition of a collation rule.
 .TP
-.I reorder-sections-after
+.I reorde\r-sections\-after
 followed by a script name to reorder listed scripts after.
 .TP
-.I reorder-sections-end
+.I reorder\-sections\-end
 marks the end of the reordering of sections.
 .TP
 .I script
 followed by a declaration of a script.
 .TP
-.I symbol-equivalence
+.I symbol\-equivalence
 followed by a collating-symbol to be equivalent to another defined
 collating-symbol.
 .PP

man5/proc.5

@@ -4390,20 +4390,20 @@ This directory contains the files and subdirectories for kernel variables
 related to filesystems.
 .TP
 .IR /proc/sys/fs/aio\-max\-nr " and " /proc/sys/fs/aio\-nr " (since Linux 2.6.4)"
-.I aio-nr
+.I aio\-nr
 is the running total of the number of events specified by
 .BR io_setup (2)
 calls for all currently active AIO contexts.
 If
-.I aio-nr
+.I aio\-nr
 reaches
-.IR aio-max-nr ,
+.IR aio\-max\-nr ,
 then
 .BR io_setup (2)
 will fail with the error
 .BR EAGAIN .
 Raising
-.I aio-max-nr
+.I aio\-max\-nr
 does not result in the preallocation or resizing
 of any kernel data structures.
 .TP

man5/sysfs.5

@@ -205,7 +205,7 @@ information about the kernel's memory management subsystem.
 This subdirectory contains one subdirectory for each of the
 huge page sizes that the system supports.
 The subdirectory name indicates the huge page size (e.g.,
-.IR hugepages-2048kB ).
+.IR hugepages\-2048kB ).
 Within each of these subdirectories is a set of files
 that can be used to view and (in some cases) change settings
 associated with that huge page size.

man7/attributes.7

@@ -881,4 +881,4 @@ and none of the named conditions hold,
 then the function can be regarded as safe.
 .SH SEE ALSO
 .BR pthreads (7),
-.BR signal-safety (7)
+.BR signal\-safety (7)

man7/bootparam.7

@@ -407,7 +407,7 @@ The other values are usually
 used for common peripherals like IDE hard disks, floppies, serial
 ports, and so on.
 .PP
-.I scsi-id
+.I scsi\-id
 -- the ID that the host adapter uses to identify itself on the
 SCSI bus.
 Only some host adapters allow you to change this value, as

man7/ddp.7

@@ -126,17 +126,17 @@ interfaces to configure some global AppleTalk parameters.
 The parameters can be accessed by reading or writing files in the directory
 .IR /proc/sys/net/atalk/ .
 .TP
-.I aarp-expiry-time
+.I aarp\-expiry\-time
 The time interval (in seconds) before an AARP cache entry expires.
 .TP
-.I aarp-resolve-time
+.I aarp\-resolve\-time
 The time interval (in seconds) before an AARP cache entry is resolved.
 .TP
-.I aarp-retransmit-limit
+.I aarp\-retransmit\-limit
 The number of retransmissions of an AARP query before the node is declared
 dead.
 .TP
-.I aarp-tick-time
+.I aarp\-tick\-time
 The timer rate (in seconds) for the timer driving AARP.
 .PP
 The default values match the specification and should never need to be

man7/environ.7

@@ -121,13 +121,13 @@ The terminal type for which output is to be prepared.
 .B PAGER
 The user's preferred utility to display text files.
 Any string acceptable as a command_string operand to the
-.I sh -c
+.I sh\ \-c
 command shall be valid.
 .TP
 .BR EDITOR / VISUAL
 The user's preferred utility to edit text files.
 Any string acceptable as a command_string operand to the
-.I sh -c
+.I sh\ \-c
 command shall be valid.
 .\" .TP
 .\" .B BROWSER

man7/locale.7

@@ -353,13 +353,13 @@ any available locale archives are not used (see
 The individual compiled locale data files are searched for under
 subdirectories which depend on the currently used locale.
 For example, when
-.I en_GB.UTF-8
+.I en_GB.UTF\-8
 is used for a category, the following subdirectories are searched for,
 in this order:
-.IR en_GB.UTF-8 ,
+.IR en_GB.UTF\-8 ,
 .IR en_GB.utf8 ,
 .IR en_GB ,
-.IR en.UTF-8 ,
+.IR en.UTF\-8 ,
 .IR en.utf8 ,
 and
 .IR en .

man7/math_error.7

@@ -240,7 +240,7 @@ and POSIX.1.
 .PP
 The
 .BR gcc (1)
-.I "\-fno-math-errno"
+.I "\-fno\-math\-errno"
 option causes the executable to employ implementations of some
 mathematical functions that are faster than the standard
 implementations, but do not set
@@ -248,9 +248,9 @@ implementations, but do not set
 on error.
 (The
 .BR gcc (1)
-.I "\-ffast-math"
+.I "\-ffast\-math"
 option also enables
-.IR "\-fno-math-errno" .)
+.IR "\-fno\-math\-errno" .)
 An error can still be tested for using
 .BR fetestexcept (3).
 .SH SEE ALSO

man7/mount_namespaces.7

@@ -1072,7 +1072,7 @@ the goal is commonly to provide full isolation of the mount points
 in the new namespace,
 .BR unshare (1)
 (since
-.IR util-linux
+.IR util\-linux
 version 2.27) in turn reverses the step performed by
 .BR systemd (1),
 by making all mount points private in the new namespace.

man7/namespaces.7

@@ -354,7 +354,7 @@ fail with the error
 For the initial user namespace,
 the default value in each of these files is half the limit on the number
 of threads that may be created
-.RI ( /proc/sys/kernel/threads-max ).
+.RI ( /proc/sys/kernel/threads\-max ).
 In all descendant user namespaces, the default value in each file is
 .BR MAXINT .
 .IP *

man7/numa.7

@@ -178,7 +178,7 @@ package is available at
 The package is also included in some Linux distributions.
 Some distributions include the development library and header
 in the separate
-.I numactl-devel
+.I numactl\-devel
 package.
 .SH SEE ALSO
 .BR get_mempolicy (2),

man7/sched.7

@@ -913,7 +913,7 @@ $ \fBecho 10 > /proc/self/autogroup\fP
 Since kernel version 2.6.18, Linux is gradually
 becoming equipped with real-time capabilities,
 most of which are derived from the former
-.I realtime-preempt
+.I realtime\-preempt
 patch set.
 Until the patches have been completely merged into the
 mainline kernel,

man7/uri.7

@@ -702,7 +702,7 @@ tools) and invokes the right tool for any URI.
 .BR lynx (1),
 .BR man2html (1),
 .BR mailaddr (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)
 .PP
 .UR http://www.ietf.org\:/rfc\:/rfc2255.txt
 IETF RFC\ 2255

man8/ld.so.8

@@ -122,7 +122,7 @@ in the arguments to the
 .B ld.so
 command line options
 .BR \-\-audit ,
-.BR \-\-library-path ,
+.BR \-\-library\-path ,
 and
 .B \-\-preload
 (see below), and

man8/ldconfig.8

@@ -60,7 +60,7 @@ are used for 64-bit libraries).
 The cache is used by the run-time linker,
 .I ld.so
 or
-.IR ld-linux.so .
+.IR ld\-linux.so .
 .B ldconfig
 checks the header and filenames of the libraries it encounters when
 determining which versions should have their links updated.
@@ -99,7 +99,7 @@ Note that
 will only look at files that are named
 .I lib*.so*
 (for regular shared objects) or
-.I ld-*.so*
+.I ld\-*.so*
 (for the dynamic loader itself).
 Other files will be ignored.
 Also,