eventfd.2, set_mempolicy.2, timerfd_create.2, fwide.3, resolver.3, spufs.7, symlink.7, udplite.7, unicode.7: Replace uses of "i.e.," in main text with "that is" or similar

Usual man-pages style is to use "i.e." only within
parenthetical expressions.

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

man2/eventfd.2

@@ -86,8 +86,8 @@ 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,
-i.e., the native byte order for integers on the host machine.
+is in host byte order\(emthat is,
+the native byte order for integers on the host machine.
 .IP
 The semantics of
 .BR read (2)

man2/set_mempolicy.2

@@ -156,8 +156,8 @@ The
 .B MPOL_DEFAULT
 mode specifies that any nondefault process memory policy be removed,
 so that the memory policy "falls back" to the system default policy.
-The system default policy is "local allocation"--
-i.e., allocate memory on the node of the CPU that triggered the allocation.
+The system default policy is "local allocation"\(emthat is,
+allocate memory on the node of the CPU that triggered the allocation.
 .I nodemask
 must be specified as NULL.
 If the "local node" contains no free memory, the system will

man2/timerfd_create.2

@@ -220,8 +220,8 @@ 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,
-i.e., the native byte order for integers on the host machine.)
+(The returned value is in host byte order\(emthat is,
+the native byte order for integers on the host machine.)
 .IP
 If no timer expirations have occurred at the time of the
 .BR read (2),

man3/fwide.3

@@ -49,8 +49,8 @@ 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,
-i.e., if char I/O is permitted but wide-character I/O is disallowed.
+It returns a negative value if \fIstream\fP is byte oriented\(emthat 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
 I/O operation might change the orientation (to byte oriented if it is a char

man3/resolver.3

@@ -222,7 +222,7 @@ by the domain name server, not by
 If set,
 .BR res_search ()
 will append the default domain name to
-single component names, i.e., those that do not contain a dot.
+single component names\(emthat is, those that do not contain a dot.
 [Enabled by default].
 .TP
 .B RES_STAYOPEN

man7/spufs.7

@@ -303,7 +303,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, i.e., how many words can be read from
+queue of each mailbox\(emthat is, how many words can be read from
 .IR mbox " or " ibox
 or how many words can be written to
 .I wbox

man7/symlink.7

@@ -262,7 +262,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, i.e., the
+is not doing a tree walk\(emthat is,
 .I \-R
 option is not specified),
 the

man7/udplite.7

@@ -52,8 +52,8 @@ If this option is not set, the only difference to UDP is
 in using a different IP protocol identifier (IANA number 136).
 
 The UDP-Lite implementation is a full extension of
-.BR udp (7),
-i.e., it shares the same API and API behaviour, and in addition
+.BR udp (7)\(emthat
+is, it shares the same API and API behaviour, and in addition
 offers two socket options to control the checksum coverage.
 .SS Address format
 UDP-Litev4 uses the

man7/unicode.7

@@ -36,8 +36,9 @@ defines the
 .BR "Universal Character Set (UCS)" .
 UCS contains all characters of all other character set standards.
 It also guarantees
-.BR "round-trip compatibility" ,
-i.e., conversion tables can be built such that no information is lost
+.BR "round-trip compatibility";
+in other words,
+conversion tables can be built such that no information is lost
 when a string is converted from any other encoding to UCS and back.
 
 UCS contains the characters required to represent practically all