American spelling!

This commit is contained in:
Michael Kerrisk 2007-06-08 10:04:51 +00:00
parent 55f7ee2a7f
commit 755b5e1786
1 changed files with 26 additions and 26 deletions

View File

@ -106,7 +106,7 @@ getrusage.2
This page is new(ish) -- it was created by splitting
getrlimit.2.
Repaired note on SIGCHLD behaviour to note that the
Repaired note on SIGCHLD behavior to note that the
POSIX non-conformance has been fixed in 2.6.9.
kill.2
@ -160,7 +160,7 @@ semget.2
mtk
Substantial language and formatting clean-ups.
Added notes on /proc files.
Rewrote BUGS note about semget()'s failure to initialise
Rewrote BUGS note about semget()'s failure to initialize
semaphore values.
semop.2
@ -230,7 +230,7 @@ times.2
boot_time + 2^32 / HZ - 300
Repaired note on SIGCHLD behaviour to note that the
Repaired note on SIGCHLD behavior to note that the
POSIX non-conformance has been fixed in 2.6.9.
Some formatting fixes.
@ -247,7 +247,7 @@ wait.2
Added waitid(2).
Added WCONTINUED and WIFCONTINUED (new in 2.6.10).
Added text on SA_NOCLDSTOP.
Updated discussion of SA_NOCLDWAIT to reflect 2.6 behaviour.
Updated discussion of SA_NOCLDWAIT to reflect 2.6 behavior.
Much other text rewritten.
wait4.2
@ -471,7 +471,7 @@ system.3
Changed name of argument from 'string' to 'command' (like POSIX).
Noted that glibc does nowadays explicitly check for the existence
of the shell if 'command' is NULL, rather than the older behaviour
of the shell if 'command' is NULL, rather than the older behavior
of assuming the shell exists and always returning 1 if
'command' is NULL.
@ -533,7 +533,7 @@ Changes to individual pages
clone.2
mtk
Noted the PID caching behaviour of NPTL's getpid()
Noted the PID caching behavior of NPTL's getpid()
wrapper under BUGS.
Added futex(2), set_thread_area(2), set_tid_address(2),
@ -606,7 +606,7 @@ sigqueue.2
times.2
mtk
Added notes on non-standard behaviour: Linux allows 'buf' to
Added notes on non-standard behavior: Linux allows 'buf' to
be NULL, but POSIX.1 doesn't specify this and it's non-portable.
uselib.2
@ -736,7 +736,7 @@ sched_setaffinity.2
shmctl.2
mtk
Noted aberrant Linux behaviour with respect to new attaches to a
Noted aberrant Linux behavior with respect to new attaches to a
segment that has already been marked for deletion.
Noted changes in permissions required for SHM_LOCK/SHM_UNLOCK.
@ -1634,7 +1634,7 @@ strnlen.3
initrd.4
Norbert Buchmuller / mtk
Added text noting that the use or real-root-dev for changing
the root device is obsolete, in favour of pivot root.
the root device is obsolete, in favor of pivot root.
(However, the page still needs to be rewritten to actually
describe the pivot_root method...)
As per Debian bug 323621.
@ -2009,7 +2009,7 @@ Global changes
Typographical or grammatical errors have been corrected in several
places.
Function and page cross references that were italicised were made bold
Function and page cross references that were italicized were made bold
(which is how the majority of function and page cross references
were already done).
@ -2216,7 +2216,7 @@ sigpause.3
Moved here from Section 2.
Some minor wording fixes; clarified System V origins of
X/Open flavour of this function.
X/Open flavor of this function.
sigset.3
mtk
@ -2480,7 +2480,7 @@ resolver.3
strerror.3
mtk / Stefan Puiu
Rewrote and extended the discussion of the two flavours of
Rewrote and extended the discussion of the two flavors of
strerror_r(), and added some additional information on
strerror().
Justin Pryzby
@ -2559,7 +2559,7 @@ HOWTOHELP
bind.2
Stefan Puiu / mtk
Remove text under EINVAL error: "This may change in the future:
see linux/unix/sock.c for details." This behaviour has been
see linux/unix/sock.c for details." This behavior has been
unchanged for a long time, and seems unlikely to change.
Add EADDRINUSE to errors.
@ -3439,7 +3439,7 @@ capabilities.7
pthreads.7
mtk
Kernel 2.6.16 eliminated buggy behaviour with respect to
Kernel 2.6.16 eliminated buggy behavior with respect to
the alternate signal stack.
@ -3851,7 +3851,7 @@ getitimer.2
Updated discussion of maximum timer value to reflect the fact
that the default jiffy is now 4 milliseconds.
Added text to note that current incorrect behaviour of
Added text to note that current incorrect behavior of
normalising tv_usec >= 1000000 will be repaired in a future
kernel; applications should be fixed now.
@ -4509,7 +4509,7 @@ readdir.3
re_comp.3
mtk
Note that these functions are obsolete in favour of regcomp(3).
Note that these functions are obsolete in favor of regcomp(3).
Justin Pryzby
Add SEE ALSO referring to regcomp.3
@ -4857,7 +4857,7 @@ openat.2
nanosleep.2
mtk
Noted buggy behaviour in Linux 2.4 and earlier when
Noted buggy behavior in Linux 2.4 and earlier when
nanosleep() is restarted after receiving stop+SIGCONT signals.
nice.2
@ -4917,7 +4917,7 @@ There was a major reworking of the CONFORMING TO sections
in most manual pages.
mtk
* generally try to rationalise the names used for standards.
* generally try to rationalize the names used for standards.
The preferred names are now documented as the head words
of the list in standards(7). For the future: there is
probably no need to talk about anything more than
@ -5319,9 +5319,9 @@ Changes to individual pages
brk.2
Evan Teran / mtk
Add text describing behaviour of the Linux brk() system call
Add text describing behavior of the Linux brk() system call
and point out that the glibc brk() wrapper provides different
behaviour.
behavior.
mtk
Note that sbrk() is implemented as a library function in glibc
that calls the brk() system call.
@ -5595,7 +5595,7 @@ Changes to individual pages
access.2
mtk
Since 2.6.20, access() honours the MS_NOEXEC mount flag.
Since 2.6.20, access() honors the MS_NOEXEC mount flag.
Jorge Peixoto de Morais Neto / mtk
Improve ENOENT description.
@ -5645,7 +5645,7 @@ mincore.2
mmap.2
mtk
Rewrote and reorganised various parts to be clearer.
Rewrote and reorganized various parts to be clearer.
Taken from Fedora downstream patches; thanks to Ivana Varekova
Removed text stating that mmap() never returns 0; that's
not true.
@ -5672,9 +5672,9 @@ semop.2
mtk
If sops contains multiple operations, then these are performed
in array order. All Unix systems that I know of do this,
and some Linux applications depend on this behaviour. SUSv3
and some Linux applications depend on this behavior. SUSv3
made no explicit statement here, but SUSv4 will explicitly
require this behaviour.
require this behavior.
Small rewording of explanation of "atomically".
signal.2
@ -6602,7 +6602,7 @@ fdatasync.2
mtk
Converted outdated BUGS note about fdatasync() being
equivalent to fsync() on Linux 2.2 into a NOTES note
about this historical behaviour.
about this historical behavior.
futex.2
mtk
@ -6961,7 +6961,7 @@ inotify.7
mtk
Added text describing what happens when the buffer given to
read(2) is too small to return information about the next event,
and noting the behaviour change in 2.6.21.
and noting the behavior change in 2.6.21.
man-pages.7
mtk