Change "e.g. " to "e.g., ", or in some cases, "for example, ".

Change "i.e. " to i.e.., ", or in some cases, "that is, ".

man1/ldd.1

@@ -25,7 +25,8 @@ Print the version number of
 .BR ldd .
 .TP
 .B \-v\ \-\-verbose
-Print all information, including e.g. symbol versioning information.
+Print all information, including, for example,
+symbol versioning information.
 .TP
 .B \-u\ \-\-unused
 Print unused direct dependencies.

man2/brk.2

@@ -84,10 +84,10 @@ Various systems use various types for the parameter of
 .BR sbrk ().
 Common are \fIint\fP, \fIssize_t\fP, \fIptrdiff_t\fP, \fIintptr_t\fP.
 .\" One sees
-.\" \fIint\fP (e.g. XPGv4, DU 4.0, HP-UX 11, FreeBSD 4.0, OpenBSD 3.2),
+.\" \fIint\fP (e.g., XPGv4, DU 4.0, HP-UX 11, FreeBSD 4.0, OpenBSD 3.2),
 .\" \fIssize_t\fP (OSF1 2.0, Irix 5.3, 6.5),
 .\" \fIptrdiff_t\fP (libc4, libc5, ulibc, glibc 2.0, 2.1),
-.\" \fIintptr_t\fP (e.g. XPGv5, AIX, SunOS 5.8, 5.9, FreeBSD 4.7, NetBSD 1.6,
+.\" \fIintptr_t\fP (e.g., XPGv5, AIX, SunOS 5.8, 5.9, FreeBSD 4.7, NetBSD 1.6,
 .\" Tru64 5.1, glibc2.2).
 .SS Linux Notes
 The return value described above for

man2/execve.2

@@ -408,7 +408,7 @@ Some systems
 use the first white space to terminate 
 .IR optional-arg .
 On some systems,
-.\" e.g. FreeBSD before 6.0, but not FreeBSD 6.0 onwards
+.\" e.g., FreeBSD before 6.0, but not FreeBSD 6.0 onwards
 an interpreter script can have multiple arguments,
 and white spaces in
 .I optional-arg
@@ -424,7 +424,7 @@ as pointers to lists containing a single NULL pointer.
 .BR "Do not take advantage of this misfeature!"
 It is non-standard and non-portable:
 on most other Unix systems doing this will result in an error.
-.\" e.g. EFAULT on Solaris 8 and FreeBSD 6.1; but
+.\" e.g., EFAULT on Solaris 8 and FreeBSD 6.1; but
 .\" HP-UX 11 is like Linux -- mtk, Apr 2007
 .\" FIXME .
 .\" Bug filed 30 Apr 2007: http://bugzilla.kernel.org/show_bug.cgi?id=8408

man2/fcntl.2

@@ -833,7 +833,7 @@ For
 .BR F_GETLK " and " F_SETLK ,
 the command was interrupted by a signal before the lock was checked or
 acquired.
-Most likely when locking a remote file (e.g. locking over
+Most likely when locking a remote file (e.g., locking over
 NFS), but can sometimes happen locally.
 .TP
 .B EINVAL
@@ -853,7 +853,7 @@ the process already has the maximum number of file descriptors open.
 .TP
 .B ENOLCK
 Too many segment locks open, lock table is full, or a remote locking
-protocol failed (e.g. locking over NFS).
+protocol failed (e.g., locking over NFS).
 .TP
 .B EPERM
 Attempted to clear the
@@ -894,7 +894,7 @@ This is supported by Linux since Linux 2.4.21 and 2.5.49.
 
 Several systems have more fields in
 .I "struct flock"
-such as e.g.
+such as, for example,
 .IR l_sysid .
 .\" e.g., Solaris 8 documents this field in fcntl(2), and Irix 6.5
 .\" documents it in fcntl(5).  mtk, May 2007

man2/getxattr.2

@@ -47,7 +47,7 @@ Extended attributes are
 .I value
 pairs associated with inodes (files, directories, symbolic links, etc).
 They are extensions to the normal attributes which are associated
-with all inodes in the system (i.e. the
+with all inodes in the system (i.e., the
 .BR stat (2)
 data).
 A complete overview of extended attributes concepts can be found in

man2/init_module.2

@@ -55,7 +55,7 @@ All of the pointer fields, with the exception of
 and
 .IR refs ,
 are expected to point within the module body and be
-initialized as appropriate for kernel space, i.e., relocated with
+initialized as appropriate for kernel space, that is, relocated with
 the rest of the module.
 .PP
 This system call requires privilege.

man2/intro.2

@@ -98,7 +98,8 @@ create one, especially for C++ users.
 System calls are not required to return only positive or negative error
 codes.
 You need to read the source to be sure how it will return errors.
-Usually, it is the negative of a standard error code, e.g., \-\fBEPERM\fP.
+Usually, it is the negative of a standard error code,
+for example, \-\fBEPERM\fP.
 The _syscall() macros will return the result \fIr\fP of the system call
 when \fIr\fP is non-negative, but will return \-1 and set the variable
 .I errno

man2/ioctl.2

@@ -48,7 +48,7 @@ The
 .BR ioctl ()
 function manipulates the underlying device parameters of special files.
 In particular, many operating characteristics of character special files
-(e.g. terminals) may be controlled with
+(e.g., terminals) may be controlled with
 .BR ioctl ()
 requests.
 The argument

man2/listxattr.2

@@ -44,7 +44,7 @@ listxattr, llistxattr, flistxattr \- list extended attribute names
 Extended attributes are name:value
 pairs associated with inodes (files, directories, symbolic links, etc).
 They are extensions to the normal attributes which are associated
-with all inodes in the system (i.e. the
+with all inodes in the system (i.e., the
 .BR stat (2)
 data).
 A complete overview of extended attributes concepts can be found in

man2/mlock.2

@@ -258,7 +258,7 @@ The memory lock on an address range is automatically removed
 if the address range is unmapped via
 .BR munmap (2).
 
-Memory locks do not stack, i.e., pages which have been locked several times
+Memory locks do not stack, that is, pages which have been locked several times
 by calls to
 .BR mlock ()
 or

man2/mount.2

@@ -142,7 +142,7 @@ Do not update access times for directories on this file system.
 .B MS_NOEXEC
 Do not allow programs to be executed from this file system.
 .\" (Possibly useful for a file system that contains non-Linux executables.
-.\" Often used as a security feature, e.g. to make sure that restricted
+.\" Often used as a security feature, e.g., to make sure that restricted
 .\" users cannot execute files uploaded using ftp or so.)
 .TP
 .B MS_NOSUID

man2/open.2

@@ -147,7 +147,7 @@ of the process.
 The group ownership (group ID) is set either to
 the effective group ID of the process or to the group ID of the
 parent directory (depending on filesystem type and mount options,
-and the mode of the parent directory, see, e.g., the mount options
+and the mode of the parent directory, see, for example, the mount options
 .I bsdgroups
 and
 .I sysvgroups
@@ -159,7 +159,7 @@ Try to minimize cache effects of the I/O to and from this file.
 In general this will degrade performance, but it is useful in
 special situations, such as when applications do their own caching.
 File I/O is done directly to/from user space buffers.
-The I/O is synchronous, i.e., at the completion of a
+The I/O is synchronous, that is, at the completion of a
 .BR read (2)
 or
 .BR write (2),
@@ -548,7 +548,7 @@ instead.
 On NFS file systems with UID mapping enabled,
 .BR open ()
 may
-return a file descriptor but e.g.
+return a file descriptor but, for example,
 .BR read (2)
 requests are denied
 with \fBEACCES\fP.

man2/pivot_root.2

@@ -22,7 +22,7 @@ of the current process.
 The typical use of
 .BR pivot_root ()
 is during system startup, when the
-system mounts a temporary root file system (e.g. an \fBinitrd\fP), then
+system mounts a temporary root file system (e.g., an \fBinitrd\fP), then
 mounts the real root file system, and eventually turns the latter into
 the current root of all relevant processes or threads.
 
@@ -70,7 +70,7 @@ They must be directories.
 \fInew_root\fP and \fIput_old\fP must not be on the same file system as
 the current root.
 .IP \- 3
-\fIput_old\fP must be underneath \fInew_root\fP, i.e. adding a non-zero
+\fIput_old\fP must be underneath \fInew_root\fP, that is, adding a non-zero
 number of \fI/..\fP to the string pointed to by \fIput_old\fP must yield
 the same directory as \fInew_root\fP.
 .IP \- 3
@@ -80,7 +80,7 @@ See also
 .BR pivot_root (8)
 for additional usage examples.
 
-If the current root is not a mount point (e.g. after
+If the current root is not a mount point (e.g., after
 .BR chroot (2)
 or
 .BR pivot_root (),

man2/removexattr.2

@@ -43,7 +43,7 @@ Extended attributes are
 .IR name :\c
 value pairs associated with inodes (files, directories, symbolic links, etc).
 They are extensions to the normal attributes which are associated
-with all inodes in the system (i.e. the
+with all inodes in the system (i.e., the
 .BR stat (2)
 data).
 A complete overview of extended attributes concepts can be found in

man2/rename.2

@@ -178,7 +178,7 @@ exists but is not a directory.
 .TP
 .BR ENOTEMPTY " or " EEXIST
 .IR newpath
-is a non-empty directory, i.e., contains entries other than "." and "..".
+is a non-empty directory, that is, contains entries other than "." and "..".
 .TP
 .BR EPERM " or " EACCES
 The directory containing

man2/semctl.2

@@ -252,7 +252,7 @@ The system call returns the value of
 this semaphore to increase) for the
 .IR semnum \-th
 semaphore of the set
-(i.e. the number of processes waiting for an increase of
+(i.e., the number of processes waiting for an increase of
 .B semval
 for the
 .IR semnum \-th

man2/send.2

@@ -156,7 +156,7 @@ of zero or more of the following flags.
 Tell the link layer that forward progress happened: you got a successful
 reply from the other side.
 If the link layer doesn't get this
-it will regularly reprobe the neighbor (e.g. via a unicast ARP).
+it will regularly reprobe the neighbor (e.g., via a unicast ARP).
 Only valid on
 .B SOCK_DGRAM
 and
@@ -215,7 +215,7 @@ error is still returned.
 .B MSG_OOB
 Sends
 .I out-of-band
-data on sockets that support this notion (e.g. of type
+data on sockets that support this notion (e.g., of type
 .BR SOCK_STREAM );
 the underlying protocol must also support
 .I out-of-band

man2/setxattr.2

@@ -47,7 +47,7 @@ Extended attributes are
 .I value
 pairs associated with inodes (files, directories, symbolic links, etc).
 They are extensions to the normal attributes which are associated
-with all inodes in the system (i.e. the
+with all inodes in the system (i.e., the
 .BR stat (2)
 data).
 A complete overview of extended attributes concepts can be found in

man2/stat.2

@@ -145,7 +145,7 @@ field.
 
 The field
 .I st_atime
-is changed by file accesses, e.g. by
+is changed by file accesses, for example, by
 .BR execve (2),
 .BR mknod (2),
 .BR pipe (2),
@@ -160,7 +160,7 @@ may or may not update
 
 The field
 .I st_mtime
-is changed by file modifications, e.g. by
+is changed by file modifications, for example, by
 .BR mknod (2),
 .BR truncate (2),
 .BR utime (2)
@@ -284,7 +284,7 @@ A component of the path
 does not exist, or the path is an empty string.
 .TP
 .B ENOMEM
-Out of memory (i.e. kernel memory).
+Out of memory (i.e., kernel memory).
 .TP
 .B ENOTDIR
 A component of the path is not a directory.

man2/syscalls.2

@@ -319,7 +319,7 @@ On many platforms, including i386, socket calls are all multiplexed
 through socketcall() and System V IPC calls through ipc().
 
 On newer platforms that only have 64-bit file access and 32-bit uids
-(e.g. alpha, ia64, s390x) there are no *64 or *32 calls.
+(e.g., alpha, ia64, s390x) there are no *64 or *32 calls.
 Where the *64
 and *32 calls exist, the other versions are obsolete.
 

man3/btree.3

@@ -87,7 +87,8 @@ any of the following values:
 .RS
 .TP
 R_DUP
-Permit duplicate keys in the tree, i.e. permit insertion if the key to be
+Permit duplicate keys in the tree, that is,
+permit insertion if the key to be
 inserted already exists in the tree.
 The default behavior, as described in
 .BR dbopen (3),
@@ -136,7 +137,7 @@ Not currently implemented.
 minkeypage
 The minimum number of keys which will be stored on any single page.
 This value is used to determine which keys will be stored on overflow
-pages, i.e. if a key or data item is longer than the pagesize divided
+pages, that is, if a key or data item is longer than the pagesize divided
 by the minkeypage value, it will be stored on overflow pages instead
 of in the page itself.
 If

man3/ctime.3

@@ -211,7 +211,7 @@ the specified contents of the structure members \fItm_wday\fP and \fItm_yday\fP
 and recomputes them from the other information in the broken-down time
 structure.
 If structure members are outside their legal interval, they will be
-normalized (so that, e.g., 40 October is changed into 9 November).
+normalized (so that, for example, 40 October is changed into 9 November).
 Calling
 .BR mktime ()
 also sets the external variable \fItzname\fP with

man3/dbopen.3

@@ -290,7 +290,8 @@ or
 .I sync
 routines.
 Modifications to the database during a sequential scan will be reflected
-in the scan, i.e. records inserted behind the cursor will not be returned
+in the scan, that is, 
+records inserted behind the cursor will not be returned
 while records inserted in front of the cursor will be returned.
 .IP
 The flag value

man3/drand48_r.3

@@ -66,7 +66,7 @@ Instead of modifying the global random generator state, they use
 the supplied data
 .IR buffer .
 
-Before the first use, this struct must be initialized, e.g.
+Before the first use, this struct must be initialized, for example,
 by filling it with zeroes, or by calling one of the functions
 .BR srand48_r (),
 .BR seed48_r (),

man3/ether_aton.3

@@ -95,7 +95,7 @@ hostname; '#' introduces a comment) and returns an address
 and hostname pair, or non-zero if it cannot be parsed.
 The buffer pointed to by
 .I hostname
-must be sufficiently long, e.g., have the same length as
+must be sufficiently long, for example, have the same length as
 .IR line .
 .PP
 The functions

man3/fclose.3

@@ -93,7 +93,7 @@ Note that
 only flushes the user space buffers provided by the
 C library.
 To ensure that the data is physically stored
-on disk the kernel buffers must be flushed too, e.g. with
+on disk the kernel buffers must be flushed too, for example, with
 .BR sync (2)
 or
 .BR fsync (2).

man3/fenv.3

@@ -95,7 +95,7 @@ Each of the macros
 is defined when the implementation supports handling
 of the corresponding exception, and if so then
 defines the corresponding bit(s), so that one can call
-exception handling functions e.g. using the integer argument
+exception handling functions, for example, using the integer argument
 .BR FE_OVERFLOW | FE_UNDERFLOW .
 Other exceptions may be supported.
 The macro
@@ -185,7 +185,7 @@ The
 function restores the floating point environment from
 the object
 .RI * envp .
-This object must be known to be valid, e.g., the result of a call to
+This object must be known to be valid, for example, the result of a call to
 .BR fegetenv ()
 or
 .BR feholdexcept ()
@@ -224,7 +224,7 @@ It is only defined if
 .B _GNU_SOURCE
 is defined.
 The C99 standard does not define a way to set individual bits in the
-floating point mask, e.g. to trap on specific flags.
+floating point mask, for example, to trap on specific flags.
 glibc 2.2 supports the functions
 .BR feenableexcept ()
 and

man3/fflush.3

@@ -91,7 +91,7 @@ Note that
 .BR fflush ()
 only flushes the user space buffers provided by the C library.
 To ensure that the data is physically stored on disk
-the kernel buffers must be flushed too, e.g. with
+the kernel buffers must be flushed too, for example, with
 .BR sync (2)
 or
 .BR fsync (2).

man3/ffs.3

@@ -51,7 +51,7 @@ The
 function returns the position of the first
 (least significant) bit set in the word \fIi\fP.
 The least significant bit is position 1 and the
-most significant position e.g. 32 or 64.
+most significant position is, for example, 32 or 64.
 .BR
 The functions
 .BR ffsll ()

man3/fts.3

@@ -174,7 +174,7 @@ A directory being visited in post-order.
 The contents of the
 .Fa FTSENT
 structure will be unchanged from when
-it was returned in pre-order, i.e. with the
+it was returned in pre-order, that is, with the
 .Fa fts_info
 field set to
 .Dv FTS_D .
@@ -274,7 +274,7 @@ It is initialized to
 A pointer to the
 .Fa FTSENT
 structure referencing the file in the hierarchy
-immediately above the current file, i.e. the directory of which this
+immediately above the current file, that is, the directory of which this
 file is a member.
 A parent structure for the initial entry point is provided as well,
 however, only the
@@ -569,7 +569,7 @@ has not yet been called for a hierarchy,
 .Fn fts_children
 will return a pointer to the files in the logical directory specified to
 .Fn fts_open ,
-i.e. the arguments specified to
+that is, the arguments specified to
 .Fn fts_open .
 Otherwise, if the
 .Fa FTSENT

man3/fwide.3

@@ -26,7 +26,7 @@ When \fImode\fP is zero, the
 function determines the current
 orientation of \fIstream\fP.
 It returns a value > 0 if \fIstream\fP is
-wide-character oriented, i.e. if wide-character I/O is permitted but char
+wide-character oriented, that is, if wide-character I/O is permitted but char
 I/O is disallowed.
 It returns a value < 0 if \fIstream\fP is byte oriented,
 i.e. if char I/O is permitted but wide-character I/O is disallowed.

man3/gethostbyname.3

@@ -310,9 +310,9 @@ line by line.
 On many systems a routine of this name reads
 from the file
 .IR /etc/hosts .
-.\" e.g. Linux, FreeBSD, Unixware, HP-UX
+.\" e.g., Linux, FreeBSD, Unixware, HP-UX
 It may be available only when the library was built without DNS support.
-.\" e.g. FreeBSD, AIX
+.\" e.g., FreeBSD, AIX
 The glibc version will ignore ipv6 entries.
 This function is not reentrant,
 and glibc adds a reentrant version

man3/grantpt.3

@@ -19,7 +19,7 @@ function changes the mode and owner of the slave pseudo-terminal device
 (pty) corresponding to the master pty referred to by
 .IR fd .
 The user ID of the slave is set to the real UID of the calling process.
-The group ID is set to an unspecified value (e.g. tty).
+The group ID is set to an unspecified value (e.g., tty).
 The mode of the slave is set to 0620 (crw\-\-w\-\-\-\-).
 .PP
 The behavior of

man3/iconv.3

@@ -51,8 +51,8 @@ In this case
 it sets \fIerrno\fP to \fBEILSEQ\fP and returns (size_t)(\-1). \fI*inbuf\fP
 is left pointing to the beginning of the invalid multibyte sequence.
 .PP
-2. The input byte sequence has been entirely converted, i.e. \fI*inbytesleft\fP
-has gone down to 0.
+2. The input byte sequence has been entirely converted,
+that is, \fI*inbytesleft\fP has gone down to 0.
 In this case
 .BR iconv ()
 returns the number of

man3/insque.3

@@ -58,7 +58,7 @@ doubly-linked list.
 .SH "CONFORMING TO"
 POSIX.1-2001
 .SH "NOTES"
-Traditionally (e.g. SunOS, Linux libc 4,5) the parameters of these
+Traditionally (e.g., SunOS, Linux libc 4,5) the parameters of these
 functions were of type \fIstruct qelem *\fP, where the struct
 is defined as
 

man3/isalpha.3

@@ -132,7 +132,7 @@ and vertical tab
 checks for an uppercase letter.
 .TP
 .BR isxdigit ()
-checks for a hexadecimal digits, i.e. one of
+checks for a hexadecimal digits, that is, one of
 .br
 .BR "0 1 2 3 4 5 6 7 8 9 a b c d e f A B C D E F" .
 .SH "RETURN VALUE"

man3/posix_memalign.3

@@ -132,7 +132,7 @@ Libc4,5 and glibc declare it in <malloc.h> and perhaps also in <stdlib.h>
 for glibc, if _XOPEN_SOURCE_EXTENDED is defined, or, equivalently,
 _XOPEN_SOURCE is defined to a value not less than 500).
 .SH NOTES
-On many systems there are alignment restrictions, e.g. on buffers
+On many systems there are alignment restrictions, for example, on buffers
 used for direct block device I/O.
 POSIX specifies the
 .I "pathconf(path,_PC_REC_XFER_ALIGN)"
@@ -162,7 +162,7 @@ or
 .BR free (3)
 a pointer gotten from
 .BR malloc (3),
-while e.g.
+while, for example,
 .BR memalign ()
 would call
 .BR malloc (3)

man3/printf.3

@@ -825,7 +825,7 @@ The glibc implementation of the functions
 .BR snprintf ()
 and
 .BR vsnprintf ()
-conforms to the C99 standard, i.e., behaves as described above,
+conforms to the C99 standard, that is, behaves as described above,
 since glibc version 2.1.
 Until glibc 2.0.6 they would return \-1
 when the output was truncated.
@@ -886,7 +886,7 @@ but provides a libbsd that contains an
 .BR snprintf ()
 equivalent to
 .BR sprintf (),
-i.e., one that ignores the
+that is, one that ignores the
 .I size
 argument.
 Thus, the use of

man3/recno.3

@@ -175,7 +175,7 @@ field of the key should be the size of that type.
 .PP
 Because there can be no meta-data associated with the underlying
 recno access method files, any changes made to the default values
-(e.g. fixed record length or byte separator value) must be explicitly
+(e.g., fixed record length or byte separator value) must be explicitly
 specified each time the file is opened.
 .PP
 In the interface specified by

man3/scanf.3

@@ -575,7 +575,7 @@ specifiers defined by ANSI C do not make sense
 While they may have a well-defined behavior on Linux, this need not
 to be so on other architectures.
 Therefore it usually is better to use
-modifiers that are not defined by ANSI C at all, i.e. use
+modifiers that are not defined by ANSI C at all, that is, use
 .B q
 instead of
 .B L

man3/setlocale.3

@@ -170,9 +170,9 @@ Linux (that is, GNU libc) supports the portable locales
 In the good old days there used to be support for
 the European Latin-1
 .B """ISO-8859-1"""
-locale (e.g. in libc-4.5.21 and libc-4.6.27), and the Russian
+locale (e.g., in libc-4.5.21 and libc-4.6.27), and the Russian
 .B """KOI-8"""
-(more precisely, "koi-8r") locale (e.g. in libc-4.6.27),
+(more precisely, "koi-8r") locale (e.g., in libc-4.6.27),
 so that having an environment variable LC_CTYPE=ISO-8859-1
 sufficed to make
 .BR isprint (3)

man3/stdarg.3

@@ -81,7 +81,7 @@ and must be called first.
 .PP
 The parameter
 .I last
-is the name of the last parameter before the variable argument list, i.e.,
+is the name of the last parameter before the variable argument list, that is,
 the last parameter of which the calling function knows the type.
 .PP
 Because the address of this parameter may be used in the

man3/strfmon.3

@@ -59,7 +59,7 @@ The ( flag indicates that negative amounts should be enclosed between
 parentheses.
 The + flag indicates that signs should be handled
 in the default way, that is, amounts are preceded by the locale's
-sign indication, e.g., nothing for positive, "\-" for negative.
+sign indication, for example, nothing for positive, "\-" for negative.
 .TP
 .BR !
 Omit the currency symbol.

man3/strftime.3

@@ -103,7 +103,7 @@ ISO week number belongs to the previous or next year,
 that year is used instead. (TZ)
 .TP
 .B %g
-Like %G, but without century, i.e., with a 2-digit year (00-99). (TZ)
+Like %G, but without century, that is, with a 2-digit year (00-99). (TZ)
 .TP
 .B %h
 Equivalent to %b. (SU)
@@ -155,7 +155,7 @@ The time in 24-hour notation (%H:%M). (SU)
 For a version including the seconds, see %T below.
 .TP
 .B %s
-The number of seconds since the Epoch, i.e., since 1970-01-01
+The number of seconds since the Epoch, that is, since 1970-01-01
 00:00:00 UTC. (TZ)
 .TP
 .B %S

man3/strptime.3

@@ -345,7 +345,7 @@ as a synonym for %I, and %P is accepted as a synonym for %p.
 Finally
 .TP
 .B %s
-The number of seconds since the epoch, i.e., since 1970-01-01 00:00:00 UTC.
+The number of seconds since the epoch, that is, since 1970-01-01 00:00:00 UTC.
 Leap seconds are not counted unless leap second support is available.
 .LP
 The GNU libc implementation does not require whitespace between

man3/termios.3

@@ -249,7 +249,7 @@ and
 for getting at it.
 Some systems use bits selected by CBAUD in
 .IR c_cflag ,
-other systems use separate fields, e.g.
+other systems use separate fields, for example,
 .I sg_ispeed
 and
 .IR sg_ospeed .)

man3/wcpncpy.3

@@ -47,7 +47,7 @@ The programmer must ensure that there is room for at least \fIn\fP wide
 characters at \fIdest\fP.
 .SH "RETURN VALUE"
 .BR wcpncpy ()
-returns a pointer to the last wide character written, i.e.
+returns a pointer to the last wide character written, that is,
 \fIdest + n \- 1\fP.
 .SH "CONFORMING TO"
 This function is a GNU extension.

man3/wcrtomb.3

@@ -33,7 +33,7 @@ at the beginning of the character
 array pointed to by \fIs\fP.
 It updates the shift state \fI*ps\fP, and
 returns the length of said multibyte representation,
-i.e. the number of bytes
+that is, the number of bytes
 written at \fIs\fP.
 .PP
 A different case is when \fIs\fP is not NULL but \fIwc\fP is L'\\0'.
@@ -45,10 +45,10 @@ the character array pointed to by
 \fIs\fP the shift sequence needed to
 bring \fI*ps\fP back to the initial state,
 followed by a '\\0' byte.
-It updates the shift state \fI*ps\fP (i.e. brings
+It updates the shift state \fI*ps\fP (i.e., brings
 it into the initial state),
 and returns the length of the shift sequence plus
-one, i.e. the number of bytes written at \fIs\fP.
+one, that is, the number of bytes written at \fIs\fP.
 .PP
 A third case is when \fIs\fP is NULL.
 In this case \fIwc\fP is ignored,

man3/wcstok.3

@@ -33,7 +33,7 @@ defined as a substring not containing any wide-characters from \fIdelim\fP.
 .PP
 The search starts at \fIwcs\fP, if \fIwcs\fP is not NULL,
 or at \fI*ptr\fP, if \fIwcs\fP is NULL.
-First, any delimiter wide-characters are skipped, i.e. the
+First, any delimiter wide-characters are skipped, that is, the
 pointer is advanced beyond any wide-characters which occur in \fIdelim\fP.
 If the end of the wide-character string is now
 reached,

man3/wctomb.3

@@ -31,7 +31,7 @@ It updates the shift state, which
 is stored in a static anonymous variable
 only known to the wctomb function,
 and returns the length of said multibyte representation,
-i.e. the number of
+that is, the number of
 bytes written at \fIs\fP.
 .PP
 The programmer must ensure that there is

man3/wprintf.3

@@ -191,7 +191,7 @@ of the form \\unnnn does not solve this problem.)
 Therefore, in
 internationalized programs, the \fIformat\fP string should consist of ASCII
 wide characters only, or should be constructed at run time in an
-internationalized way (e.g. using
+internationalized way (e.g., using
 .BR gettext (3)
 or
 .BR iconv (3),

man4/console_codes.4

@@ -66,7 +66,7 @@ or
 .BR reset (1).
 .SH "LINUX CONSOLE CONTROLS"
 This section describes all the control characters and escape sequences
-that invoke special functions (i.e. anything other than writing a
+that invoke special functions (i.e., anything other than writing a
 glyph at the current cursor location) on the Linux console.
 .SS "Control characters"
 A character is a control character if (before transformation
@@ -532,9 +532,9 @@ It also recognizes ESC % and provides a more complete UTF-8
 implementation than Linux console.
 .\"
 .SS CSI Sequences
-Old versions of \fIxterm\fP, e.g., from X11R5,
+Old versions of \fIxterm\fP, for example, from X11R5,
 interpret the blink SGR as a bold SGR.
-Later versions which implemented ANSI colors, e.g.,
+Later versions which implemented ANSI colors, for example,
 XFree86 3.1.2A in 1995, improved this by allowing
 the blink attribute to be displayed as a color.
 Modern versions of xterm implement blink SGR as blinking text

man4/initrd.4

@@ -40,7 +40,7 @@ The special file
 is a read-only block device.
 Device
 .I /dev/initrd
-is a RAM disk that is initialized (e.g. loaded) by the boot loader before
+is a RAM disk that is initialized (e.g., loaded) by the boot loader before
 the kernel is started.
 The kernel then can use the block device
 .IR /dev/initrd "'s "
@@ -54,7 +54,7 @@ of
 In the second phase, additional drivers or other modules
 are loaded from the initial root device's contents.
 After loading the additional modules, a new root file system
-(i.e. the normal root file system) is mounted from a
+(i.e., the normal root file system) is mounted from a
 different device.
 .\"
 .\"
@@ -274,7 +274,7 @@ A possible system installation scenario is as follows:
 2. The executable
 .IR /linuxrc
 determines what is needed to (1) mount the normal root file-system
-(i.e. device type, device drivers, file system) and (2) the
+(i.e., device type, device drivers, file system) and (2) the
 distribution media (e.g. CD-ROM, network, tape, ...).
 This can be
 done by asking the user, by auto-probing, or by using a hybrid
@@ -424,7 +424,7 @@ The behavior may change in future versions of the Linux kernel.
 .\"
 .\"
 .\"
-.SH AUTHOR
+.SH AUTHORS
 The kernel code for device
 .BR initrd
 was written by Werner Almesberger <almesber@lrc.epfl.ch> and

man4/lp.4

@@ -34,8 +34,8 @@ The minor numbers
 correspond to the printer port base addresses 0x03bc, 0x0378 and 0x0278.
 Usually they have mode 220 and are owned by root and group lp.
 You can use printer ports either with polling or with interrupts.
-Interrupts are recommended when high traffic is expected, e.g.\& for laser
-printers.
+Interrupts are recommended when high traffic is expected, for example,
+for laser printers.
 For usual dot matrix printers polling will usually be enough.
 The default is polling.
 .SH DESCRIPTION

man4/rtc.4

@@ -81,7 +81,7 @@ or directly with the ioctl requests listed below.
 Besides tracking the date and time, many RTCs can also generate
 interrupts
 .IP *
-on every clock update (i.e. once per second);
+on every clock update (i.e., once per second);
 .IP *
 at periodic intervals with a frequency that can be set to
 any power-of-2 multiple in the range 2 Hz to 8192 Hz;
@@ -310,7 +310,7 @@ An RTC's Epoch has nothing to do with the POSIX Epoch which is only
 used for the system clock.
 
 If the year according to the RTC's Epoch and the year register is
-less than 1970 it is assumed to be 100 years later, i.e. between 2000
+less than 1970 it is assumed to be 100 years later, that is, between 2000
 and 2069.
 
 Some RTCs support "wildcard" values in alarm fields, to support

man4/sk98lin.4

@@ -503,7 +503,7 @@ is enabled on a network adapter card.
 This parameter is ignored if no moderation is applied.
 
 Note that the duration of the moderation interval is to be chosen with care.
-At first glance, selecting a very long duration (e.g. only 100 interrupts per
+At first glance, selecting a very long duration (e.g., only 100 interrupts per
 second) seems to be meaningful, but the increase of packet-processing delay
 is tremendous.
 On the other hand, selecting a very short moderation time might
@@ -549,7 +549,7 @@ for all network traffic or not.
 In this mode, RLMT monitors the network path between the two
 ports of an adapter by regularly exchanging packets between them.
 This mode requires a network configuration in which the
-two ports are able to "see" each other (i.e. there
+two ports are able to "see" each other (i.e., there
 must not be any router between the ports).
 
 .br

man4/tty_ioctl.4

@@ -82,7 +82,7 @@ Only root can do this.
 Window sizes are kept in the kernel, but not used by the kernel
 (except in the case of virtual consoles, where the kernel will
 update the window size when the size of the virtual console changes,
-e.g. by loading a new font).
+for example, by loading a new font).
 .TP
 .BI "TIOCGWINSZ	struct winsize *" argp
 Get window size.

man5/hosts.equiv.5

@@ -6,7 +6,7 @@
 \fBr\fP command access to your system
 .SH DESCRIPTION
 The \fBhosts.equiv\fP file allows or denies hosts and users to use
-the \fBr\fP-commands (e.g. \fBrlogin\fP, \fBrsh\fP or \fBrcp\fP) without
+the \fBr\fP-commands (e.g., \fBrlogin\fP, \fBrsh\fP or \fBrcp\fP) without
 supplying a password.
 .PP
 The file uses the following format:
@@ -58,7 +58,7 @@ character which means "any host" when the word
 .I promiscuous
 is added to the auth component line in your PAM file for
 the particular service
-.RB "(e.g. " rlogin ).
+.RB "(e.g., " rlogin ).
 .SH "SEE ALSO"
 .BR rhosts (5),
 .BR rlogind (8),

man5/proc.5

@@ -89,8 +89,8 @@ The last entry contains two zeros.
 .I /proc/[number]/cmdline
 This holds the complete command line for the process, unless the whole
 process has been swapped out or the process is a zombie.
-In either of these latter cases, there is nothing in this file: i.e. a
-read on this file will return 0 characters.
+In either of these latter cases, there is nothing in this file:
+that is, a read on this file will return 0 characters.
 The command line arguments appear in this file as a set of
 null-separated strings, with a further null byte after the last string.
 .TP
@@ -1390,7 +1390,7 @@ The default value in this file "/sbin/hotplug".
 .IR /proc/sys/kernel/domainname " and " /proc/sys/kernel/hostname
 can be used to set the NIS/YP domainname and the
 hostname of your box in exactly the same way as the commands
-domainname and hostname, i.e.:
+domainname and hostname, that is:
 .br
 
 .br

man5/resolv.conf.5

@@ -191,7 +191,7 @@ amended on a per-process basis by setting the environment variable
 as explained above under \fBoptions\fP.
 .LP
 The keyword and value must appear on a single line, and the keyword
-(e.g. \fBnameserver\fP) must start the line.
+(e.g., \fBnameserver\fP) must start the line.
 The value follows the keyword, separated by white space.
 .SH FILES
 .IR /etc/resolv.conf ,

man5/utmp.5

@@ -193,7 +193,7 @@ and some versions of
 Neither of these programs creates the file, so if it is
 removed, record-keeping is turned off.
 .PP
-Note that on \fIbiarch\fP platforms, i.e. systems which can run both
+Note that on \fIbiarch\fP platforms, that is, systems which can run both
 32-bit and 64-bit applications (x86-64, ppc64, s390x, etc.),
 \fIut_tv\fP is the same size in 32-bit mode as in 64-bit mode.
 The same goes for \fIut_session\fP and \fIut_time\fP if they are present.
@@ -246,7 +246,8 @@ many programs which assume BSD semantics and which do not modify utmp.
 Linux uses the BSD conventions for line contents, as documented above.
 .PP
 System V only uses the type field to mark them and logs informative messages
-such as e.g.\& \fB"new time"\fP in the line field. \fBUT_UNKNOWN\fP seems
+such as \fB"new time"\fP in the line field.
+\fBUT_UNKNOWN\fP seems
 to be a Linux invention.
 System V has no \fIut_host\fP or \fIut_addr_v6\fP fields.
 .PP

man7/arp.7

@@ -256,7 +256,7 @@ There is no way to signal positive feedback from user space.
 This means connection oriented protocols implemented in user space
 will generate excessive ARP traffic, because ndisc will regularly
 reprobe the MAC address.
-The same problem applies for some kernel protocols (e.g. NFS over UDP).
+The same problem applies for some kernel protocols (e.g., NFS over UDP).
 
 This man page mashes IPv4 specific and shared between IPv4 and IPv6
 functionality together.

man7/bootparam.7

@@ -197,7 +197,7 @@ as `readonly' so that filesystem consistency check programs (fsck)
 can do their work on a quiescent file system.
 No processes can
 write to files on the filesystem in question until it is `remounted'
-as read/write capable, e.g., by `mount \-w \-n \-o remount /'.
+as read/write capable, for example, by `mount \-w \-n \-o remount /'.
 (See also
 .BR mount (8).)
 
@@ -383,7 +383,7 @@ and an initial ramdisk; then the kernel converts initrd into
 a "normal" ramdisk, which is mounted read-write as root device;
 then /linuxrc is executed; afterwards the "real" root file system is mounted,
 and the initrd filesystem is moved over to /initrd; finally
-the usual boot sequence (e.g. invocation of /sbin/init) is performed.
+the usual boot sequence (e.g., invocation of /sbin/init) is performed.
 
 For a detailed description of the initrd feature, see
 .IR /usr/src/linux/Documentation/initrd.txt .
@@ -754,7 +754,7 @@ The standard disk driver can accept geometry arguments for the disks
 similar to the IDE driver.
 Note however that it only expects three
 values (C/H/S); any more or any less and it will silently ignore you.
-Also, it only accepts `hd=' as an argument, i.e. `hda='
+Also, it only accepts `hd=' as an argument, that is, `hda='
 and so on are not valid here.
 The format is as follows:
 .IP
@@ -1128,7 +1128,7 @@ You can tell the printer driver what ports to use and what ports not
 to use.
 The latter comes in handy if you don't want the printer driver
 to claim all available parallel ports, so that other drivers
-(e.g. PLIP, PPA) can use them instead.
+(e.g., PLIP, PPA) can use them instead.
 
 The format of the argument is multiple port names.
 For example,

man7/epoll.7

@@ -383,7 +383,7 @@ Its interface should be finalized in Linux kernel 2.5.66.
 .SH CONFORMING TO
 The epoll API is Linux specific.
 Some other systems provide similar
-mechanisms, e.g., FreeBSD has
+mechanisms, for example, FreeBSD has
 .IR kqueue ,
 and Solaris has
 .IR /dev/poll .

man7/feature_test_macros.7

@@ -194,7 +194,7 @@ unless they are also explicitly defined.
 is not otherwise defined,
 then it is always defined with the value 200112
 (199506 in glibc versions before 2.4),
-unless the compiler is invoked in one of its standard modes, e.g., the
+unless the compiler is invoked in one of its standard modes, for example, the
 .I -std=c99
 flag.)
 Multiple macros can be defined; the results are additive.

man7/glob.7

@@ -127,7 +127,7 @@ Note that wildcard patterns are not regular expressions,
 although they are a bit similar.
 First of all, they match
 filenames, rather than text, and secondly, the conventions
-are not the same: e.g., in a regular expression `*' means zero or
+are not the same: for example, in a regular expression `*' means zero or
 more copies of the preceding thing.
 
 Now that regular expressions have bracket expressions where

man7/hier.7

@@ -410,7 +410,7 @@ device lock files is
 where
 .I <device>
 is the device's name in the filesystem.
-The format used is that of HDU UUCP lock files, i.e. lock files
+The format used is that of HDU UUCP lock files, that is, lock files
 contain a PID as a 10-byte ASCII decimal number, followed by a newline
 character.
 .TP

man7/ip.7

@@ -544,7 +544,7 @@ When it is connected to a specific peer with
 .BR connect (2)
 the currently known path MTU can be retrieved conveniently using the
 .B IP_MTU
-socket option (e.g. after a
+socket option (e.g., after a
 .B EMSGSIZE
 error occurred).
 It may change over time.

man7/mailaddr.7

@@ -72,7 +72,7 @@ The real-name part ("Eric Allman") can either be placed before
 <>, or in () at the end.
 (Strictly speaking the two aren't the same,
 but the difference is beyond the scope of this page.)
-The name may have to be quoted using "", e.g. if it contains ".":
+The name may have to be quoted using "", for example, if it contains ".":
 .PP
 	"Eric P. Allman" <eric@monet.berkeley.edu>
 .SS Abbreviation.

man7/mdoc.samples.7

@@ -556,14 +556,14 @@ for sections 2, 3, 4, and 5.
 .\" LOC	UNIX Local Manual
 .It Li \&.Os operating_system release#
 The name of the operating system
-should be the common acronym, e.g.
+should be the common acronym, for example,
 .Tn BSD
 or
 .Tn FreeBSD
 or
 .Tn ATT .
 The release should be the standard release
-nomenclature for the system specified, e.g. 4.3, 4.3+Tahoe, V.3,
+nomenclature for the system specified, for example, 4.3, 4.3+Tahoe, V.3,
 V.4.
 Unrecognized arguments are displayed as given in the page footer.
 For instance, a typical footer might be:

man7/netlink.7

@@ -167,7 +167,7 @@ struct nlmsgerr {
 .in -0.25i
 
 A netlink family usually specifies more message types, see the
-appropriate manual pages for that, e.g.
+appropriate manual pages for that, for example,
 .BR rtnetlink (7)
 for
 .BR NETLINK_ROUTE .

man7/packet.7

@@ -153,7 +153,7 @@ These types make only sense for receiving.
 .B sll_addr
 and
 .B sll_halen
-contain the physical layer (e.g. IEEE 802.3) address and its length.
+contain the physical layer (e.g., IEEE 802.3) address and its length.
 The exact interpretation depends on the device.
 
 When you send packets it is enough to specify
@@ -349,7 +349,7 @@ is the IEEE 802.3 protocol type as defined in
 .I <sys/if_ether.h>
 and
 .B spkt_device
-is the device name as a null terminated string, e.g. eth0.
+is the device name as a null terminated string, for example, eth0.
 
 This structure is obsolete and should not be used in new code.
 .SH BUGS

man7/posixoptions.7

@@ -379,7 +379,7 @@ is present.
 This option describes support for process creation in a context where
 it is difficult or impossible to use
 .IR fork (),
-e.g. because no MMU is present.
+for example, because no MMU is present.
 If _POSIX_SPAWN is in effect, then the include file
 .I <spawn.h>
 and the functions

man7/raw.7

@@ -85,7 +85,7 @@ protocols or protocols with no user interface (like ICMP).
 
 When a packet is received, it is passed to any raw sockets which have
 been bound to its protocol before it is passed to other protocol handlers
-(e.g. kernel protocol modules).
+(e.g., kernel protocol modules).
 .SS Address Format
 Raw sockets use the standard
 .I sockaddr_in

man7/regex.7

@@ -104,9 +104,9 @@ it matches any single character
 If two characters in the list are separated by `\-', this is shorthand
 for the full \fIrange\fR of characters between those two (inclusive) in the
 collating sequence,
-e.g. `[0\-9]' in ASCII matches any decimal digit.
+for example, `[0\-9]' in ASCII matches any decimal digit.
 It is illegal\*(dg for two ranges to share an
-endpoint, e.g. `a-c-e'.
+endpoint, for example, `a-c-e'.
 Ranges are very collating-sequence-dependent,
 and portable programs should avoid relying on them.
 .PP
@@ -128,7 +128,7 @@ sequence of characters of that collating element.
 The sequence is a single element of the bracket expression's list.
 A bracket expression containing a multi-character collating element
 can thus match more than one character,
-e.g. if the collating sequence includes a `ch' collating element,
+for example, if the collating sequence includes a `ch' collating element,
 then the RE `[[.ch.]]*c' matches the first five characters
 of `chchcc'.
 .PP
@@ -209,9 +209,9 @@ alphabet.
 When an alphabetic that exists in multiple cases appears as an
 ordinary character outside a bracket expression, it is effectively
 transformed into a bracket expression containing both cases,
-e.g. `x' becomes `[xX]'.
+for example, `x' becomes `[xX]'.
 When it appears inside a bracket expression, all case counterparts
-of it are added to the bracket expression, so that (e.g.) `[x]'
+of it are added to the bracket expression, so that, for example, `[x]'
 becomes `[xX]' and `[^x]' becomes `[^xX]'.
 .PP
 No particular limit is imposed on the length of REs\*(dg.
@@ -240,7 +240,7 @@ matches the same sequence of characters
 matched by the \fId\fRth parenthesized subexpression
 (numbering subexpressions by the positions of their opening parentheses,
 left to right),
-so that (e.g.) `\e([bc]\e)\e1' matches `bb' or `cc' but not `bc'.
+so that, for example, `\e([bc]\e)\e1' matches `bb' or `cc' but not `bc'.
 .SH BUGS
 Having two kinds of REs is a botch.
 .PP

man7/rtnetlink.7

@@ -322,7 +322,7 @@ RTA_CACHEINFO::
 .TP
 .BR RTM_NEWNEIGH ", " RTM_DELNEIGH  ", " RTM_GETNEIGH
 Add, remove or receive information about a neighbor table
-entry (e.g. an ARP entry).
+entry (e.g., an ARP entry).
 The message contains an
 .B ndmsg
 structure.

man7/socket.7

@@ -524,7 +524,7 @@ See
 .BR fcntl (2)
 for more information.
 .PP
-Under some circumstances (e.g. multiple processes accessing a
+Under some circumstances (e.g., multiple processes accessing a
 single socket), the condition that caused the
 .B SIGIO
 may have already disappeared when the process reacts to the signal.

man7/suffixes.7

@@ -203,7 +203,7 @@ Suffix	File type
  .ph	Perl header file
  .php	PHP program file
  .php3	PHP3 program file
- .pid	File to store daemon PID (e.g. crond.pid)
+ .pid	File to store daemon PID (e.g., crond.pid)
  .pl	TeX property list file or Perl library file
  .pm	Perl module
  .png	Portable Network Graphics file
@@ -270,7 +270,7 @@ Suffix	File type
  .zip	\fBzip\fP(1) archive
  .zoo	\fBzoo\fP(1) archive
  ~	Emacs or \fBpatch\fP(1) backup file
- rc	startup (`run control') file, e.g. \fI.newsrc\fP
+ rc	startup (`run control') file, e.g., \fI.newsrc\fP
 .TE
 .SH "CONFORMING TO"
 General UNIX conventions.

man7/uri.7

@@ -271,7 +271,8 @@ is a correct format for referring to
 a local file.
 However, older standards did not permit this format,
 and some programs don't recognize this as a URI.
-A more portable syntax is to use an empty string as the server name, e.g.,
+A more portable syntax is to use an empty string as the server name,
+for example,
 <file:///etc/passwd>; this form does the same thing
 and is easily recognized by pattern matchers and older programs as a URI.
 Note that if you really mean to say "start from the current location," don't

man7/utf-8.7

@@ -85,7 +85,7 @@ All
 characters > 0x7f are encoded as a multi-byte sequence
 consisting only of bytes in the range 0x80 to 0xfd, so no ASCII
 byte can appear as part of another character and there are no
-problems with e.g. '\\0' or '/'.
+problems with, for example,  '\\0' or '/'.
 .TP
 *
 The lexicographic sorting order of
@@ -271,7 +271,7 @@ The
 .BR Unicode " and " UCS
 standards require that producers of
 .B UTF-8
-shall use the shortest form possible, e.g., producing a two-byte
+shall use the shortest form possible, for example, producing a two-byte
 sequence with first byte 0xc0 is non-conforming.
 .B Unicode 3.1
 has added the requirement that conforming programs must not accept