mirror of https://github.com/mkerrisk/man-pages
uselib.2, getfsent.3, regex.3, nsswitch.conf.5, inotify.7, man-pages.7, symlink.7: Replace uses of "e.g." in main text with "for example" or similar
Usual man-pages style is to use "e.g." only within parenthetical expressions. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
449dd4e2ab
commit
10850212d0
|
@ -71,8 +71,8 @@ The system limit on the total number of open files has been reached.
|
|||
.B ENOEXEC
|
||||
The file specified by
|
||||
.I library
|
||||
is not an executable of known type,
|
||||
e.g., does not have the correct magic numbers.
|
||||
is not an executable of a known type;
|
||||
for example, it does not have the correct magic numbers.
|
||||
.SH CONFORMING TO
|
||||
.BR uselib ()
|
||||
is Linux-specific, and should not be used in programs
|
||||
|
|
|
@ -114,8 +114,8 @@ Upon failure or end-of-file, these functions return NULL and 0, respectively.
|
|||
.\" function appeared in 4.0BSD; the other four functions appeared in 4.3BSD.
|
||||
.SH CONFORMING TO
|
||||
These functions are not in POSIX.1-2001.
|
||||
Several operating systems have them,
|
||||
e.g., *BSD, SunOS, Digital UNIX, AIX (which also has a
|
||||
Several operating systems have them, for example,
|
||||
*BSD, SunOS, Digital UNIX, AIX (which also has a
|
||||
.BR getfstype ()).
|
||||
HP-UX has functions of the same names,
|
||||
that however use a
|
||||
|
|
|
@ -289,7 +289,7 @@ Trailing backslash.
|
|||
Un-matched parenthesis group operators.
|
||||
.TP
|
||||
.B REG_ERANGE
|
||||
Invalid use of the range operator, e.g., the ending point of the range
|
||||
Invalid use of the range operator; for example, the ending point of the range
|
||||
occurs prior to the starting point.
|
||||
.TP
|
||||
.B REG_ESIZE
|
||||
|
|
|
@ -142,12 +142,12 @@ nis [NOTFOUND=return] files
|
|||
The first column is the database name.
|
||||
The remaining columns specify:
|
||||
.IP * 3
|
||||
One or more service specifications e.g., "files", "db", or "nis".
|
||||
One or more service specifications, for example, "files", "db", or "nis".
|
||||
The order of the services on the line determines the order in which
|
||||
those services will be queried, in turn, until a result is found.
|
||||
.IP *
|
||||
Optional actions to perform if a particular result is obtained
|
||||
from the preceding service, e.g., "[NOTFOUND=return]".
|
||||
from the preceding service, for example, "[NOTFOUND=return]".
|
||||
.LP
|
||||
The service specifications supported on your system depend on the
|
||||
presence of shared libraries, and are therefore extensible.
|
||||
|
|
|
@ -191,8 +191,8 @@ field returned by
|
|||
File was accessed (read) (*).
|
||||
.TP
|
||||
.B IN_ATTRIB
|
||||
Metadata changed, e.g., permissions, timestamps, extended attributes,
|
||||
link count (since Linux 2.6.25), UID, GID, etc. (*).
|
||||
Metadata changed\(emfor example, permissions, timestamps, extended attributes,
|
||||
link count (since Linux 2.6.25), UID, or GID. (*).
|
||||
.TP
|
||||
.B IN_CLOSE_WRITE
|
||||
File opened for writing was closed (*).
|
||||
|
|
|
@ -500,8 +500,8 @@ in italic format, for example,
|
|||
.IR "man 7 man-pages" .
|
||||
In this case, it may be worth using nonbreaking spaces
|
||||
("\e\ ") at suitable places in the command.
|
||||
Command options should be written in italics, e.g.,
|
||||
.IR \-l .
|
||||
Command options should be written in italics (e.g.,
|
||||
.IR \-l ).
|
||||
.PP
|
||||
Expressions, if not written on a separate indented line, should
|
||||
be specified in italics.
|
||||
|
|
|
@ -220,7 +220,7 @@ would display the contents of the file
|
|||
.IR afile .
|
||||
|
||||
It is important to realize that this rule includes commands which may
|
||||
optionally traverse file trees, e.g., the command
|
||||
optionally traverse file trees; for example, the command
|
||||
.I "chown file"
|
||||
is included in this rule, while the command
|
||||
.IR "chown\ \-R file" ,
|
||||
|
@ -228,11 +228,11 @@ which performs a tree traversal, is not.
|
|||
(The latter is described in the third area, below.)
|
||||
|
||||
If it is explicitly intended that the command operate on the symbolic
|
||||
link instead of following the symbolic link, e.g., it is desired that
|
||||
link instead of following the symbolic link\(emfor 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, the
|
||||
is, whether it is a symbolic link or not\(emthe
|
||||
.I \-h
|
||||
option should be used.
|
||||
In the above example,
|
||||
|
|
Loading…
Reference in New Issue