Changes.old, clone.2, execve.2, fcntl.2, futex.2, getitimer.2, getpriority.2, mmap.2, mount.2, mprotect.2, sched_setscheduler.2, select_tut.2, setuid.2, sigaltstack.2, vfork.2, div.3, fenv.3, fmod.3, memchr.3, pthread_attr_setstackaddr.3, pthread_attr_setstacksize.3, pthread_getattr_np.3, queue.3, scanf.3, trunc.3, st.4, proc.5, services.5, utmp.5, bootparam.7, capabilities.7, feature_test_macros.7, futex.7, glob.7, man.7, netlink.7, unicode.7: Switch to American usage: "-wards" ==> "-ward"

American English uses "afterward" in preference to "afterwards",
and so on

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

Changes.old

@@ -1530,7 +1530,7 @@ readv.2
 
 remap_file_pages.2
     mtk
-        Added text to note that start and size are both rounded downwards.
+        Added text to note that start and size are both rounded downward.
 
 sched_setparam.2
     mtk
@@ -19123,35 +19123,35 @@ Various pages
     Michael Kerrisk
         s/non-/non/
             The tendency in English, as prescribed in style guides like
-            Chicago MoS, is towards removing hyphens after prefixes
+            Chicago MoS, is toward removing hyphens after prefixes
             like "non-" etc.
 
 Various pages
     Michael Kerrisk
         Global fix: s/re-/re/
             The tendency in English, as prescribed in style guides like
-            Chicago MoS, is towards removing hyphens after prefixes
+            Chicago MoS, is toward removing hyphens after prefixes
             like "re-" etc.
 
 Various pages
     Michael Kerrisk
         Global fix: s/multi-/multi/
             The tendency in English, as prescribed in style guides like
-            Chicago MoS, is towards removing hyphens after prefixes
+            Chicago MoS, is toward removing hyphens after prefixes
             like "multi-" etc.
 
 Various pages
     Michael Kerrisk
         Global fix: s/pre-/pre/
             The tendency in English, as prescribed in style guides like
-            Chicago MoS, is towards removing hyphens after prefixes
+            Chicago MoS, is toward removing hyphens after prefixes
             like "pre-" etc.
 
 Various pages
     Michael Kerrisk
         Global fix: s/sub-/sub/
             The tendency in English, as prescribed in style guides like
-            Chicago MoS, is towards removing hyphens after prefixes
+            Chicago MoS, is toward removing hyphens after prefixes
             like "sub-" etc.
 
 stime.2

man2/clone.2

@@ -67,7 +67,7 @@ system call, hereinafter referred to as
 .BR sys_clone .
 A description of
 .B sys_clone
-is given towards the end of this page.
+is given toward the end of this page.
 
 Unlike
 .BR fork (2),
@@ -127,7 +127,7 @@ The calling process must therefore
 set up memory space for the child stack and pass a pointer to this
 space to
 .BR clone ().
-Stacks grow downwards on all processors that run Linux
+Stacks grow downward on all processors that run Linux
 (except the HP PA processors), so
 .I child_stack
 usually points to the topmost address of the memory space set up for

man2/execve.2

@@ -471,7 +471,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 onward
 an interpreter script can have multiple arguments,
 and white spaces in
 .I optional-arg

man2/fcntl.2

@@ -567,7 +567,7 @@ depending on the value given to
 .IP
 The above behavior was accidentally dropped in Linux 2.6.12,
 and won't be restored.
-From Linux 2.6.32 onwards, use
+From Linux 2.6.32 onward, use
 .BR F_SETOWN_EX
 to target
 .B SIGIO
@@ -762,7 +762,7 @@ in Linux as part of the GNU C Library (Glibc).
 .B F_SETLEASE
 and
 .B F_GETLEASE
-(Linux 2.4 onwards) are used (respectively) to establish a new lease,
+(Linux 2.4 onward) are used (respectively) to establish a new lease,
 and retrieve the current lease, on the open file description
 referred to by the file descriptor
 .IR fd .
@@ -913,7 +913,7 @@ that has been accessed by another process.
 .SS "File and directory change notification (dnotify)"
 .TP
 .BR F_NOTIFY " (\fIlong\fP)"
-(Linux 2.4 onwards)
+(Linux 2.4 onward)
 Provide notification when the directory referred to by
 .I fd
 or any of the files that it contains is changed.

man2/futex.2

@@ -136,7 +136,7 @@ returns.
 
 Because it was inherently racy,
 .B FUTEX_FD
-has been removed from Linux 2.6.26 onwards.
+has been removed from Linux 2.6.26 onward.
 .TP
 .BR FUTEX_REQUEUE " (since Linux 2.5.70)"
 This operation was introduced in order to avoid a "thundering herd" effect

man2/getitimer.2

@@ -104,7 +104,7 @@ and
 are significant in determining the duration of a timer.
 .LP
 Timers will never expire before the requested time,
-but may expire some (short) time afterwards, which depends
+but may expire some (short) time afterward, which depends
 on the system timer resolution and on the system load; see
 .BR time (7).
 (But see BUGS below.)
@@ -206,7 +206,7 @@ value is specified that is outside of the range 0 to 999999.
 However, in kernels up to and including 2.6.21,
 Linux does not give an error, but instead silently
 adjusts the corresponding seconds value for the timer.
-From kernel 2.6.22 onwards,
+From kernel 2.6.22 onward,
 this nonconformance has been repaired:
 an improper
 .I tv_usec

man2/getpriority.2

@@ -109,7 +109,7 @@ can legitimately return the value \-1, it is necessary
 to clear the external variable
 .I errno
 prior to the
-call, then check it afterwards to determine
+call, then check it afterward to determine
 if \-1 is an error or a legitimate value.
 The
 .BR setpriority ()

man2/mmap.2

@@ -224,7 +224,7 @@ the use of this option is discouraged.
 .B MAP_GROWSDOWN
 Used for stacks.
 Indicates to the kernel virtual memory system that the mapping
-should extend downwards in memory.
+should extend downward in memory.
 .TP
 .BR MAP_HUGETLB " (since Linux 2.6.32)"
 Allocate the mapping using "huge pages."

man2/mount.2

@@ -101,7 +101,7 @@ and in \fI<sys/mount.h>\fP for glibc2) in the low order 16 bits:
 .\" 2.6.25 Added MS_I_VERSION, which needs to be documented.
 .\"
 .TP
-.BR MS_BIND " (Linux 2.4 onwards)"
+.BR MS_BIND " (Linux 2.4 onward)"
 .\" since 2.4.0-test9
 Perform a bind mount, making a file or a directory subtree visible at
 another point within a file system.
@@ -259,10 +259,10 @@ flag to
 .BR open (2)
 was specified for all file opens to this file system).
 .PP
-From Linux 2.4 onwards, the
+From Linux 2.4 onward, the
 .BR MS_NODEV ", " MS_NOEXEC ", and " MS_NOSUID
 flags are settable on a per-mount-point basis.
-From kernel 2.6.16 onwards,
+From kernel 2.6.16 onward,
 .B MS_NOATIME
 and
 .B MS_NODIRATIME

man2/mprotect.2

@@ -143,7 +143,7 @@ has been set.
 .\" sigaction.2 refers to this example
 .PP
 The program below allocates four pages of memory, makes the third
-of these pages read-only, and then executes a loop that walks upwards
+of these pages read-only, and then executes a loop that walks upward
 through the allocated region modifying bytes.
 
 An example of what we might see when running the program is the

man2/sched_setscheduler.2

@@ -455,7 +455,7 @@ was not possible up to kernel version 2.6.17.
 .SS Real-time features in the mainline Linux kernel
 .\" FIXME . Probably this text will need some minor tweaking
 .\" by about the time of 2.6.30; ask Carsten Emde about this then.
-From kernel version 2.6.18 onwards, however, Linux is gradually
+From kernel version 2.6.18 onward, however, Linux is gradually
 becoming equipped with real-time capabilities,
 most of which are derived from the former
 .I realtime-preempt

man2/select_tut.2

@@ -527,7 +527,7 @@ when monitoring large numbers of file descriptors.
 .SH EXAMPLE
 Here is an example that better demonstrates the true utility of
 .BR select ().
-The listing below is a TCP forwarding program that forwards
+The listing below is a TCP forwarding program that forward
 from one TCP port to another.
 .PP
 .nf
@@ -796,7 +796,7 @@ main(int argc, char *argv[])
 }
 .fi
 .PP
-The above program properly forwards most kinds of TCP connections
+The above program properly forward most kinds of TCP connections
 including OOB signal data transmitted by \fBtelnet\fP servers.
 It handles the tricky problem of having data flow in both directions
 simultaneously.

man2/setuid.2

@@ -61,7 +61,7 @@ privileges.
 .PP
 Thus, a set-user-ID-root program wishing to temporarily drop root
 privileges, assume the identity of an unprivileged user, and then regain
-root privileges afterwards cannot use
+root privileges afterward cannot use
 .BR setuid ().
 You can accomplish this with
 .BR seteuid (2).

man2/sigaltstack.2

@@ -178,7 +178,7 @@ In these circumstances the only way to catch this signal is
 on an alternate signal stack.
 .P
 On most hardware architectures supported by Linux, stacks grow
-downwards.
+downward.
 .BR sigaltstack ()
 automatically takes account
 of the direction of stack growth.
@@ -204,7 +204,7 @@ inherits a copy of its parent's alternate signal stack settings.
 supersedes the older
 .BR sigstack ()
 call.
-For backwards compatibility, glibc also provides
+For backward compatibility, glibc also provides
 .BR sigstack ().
 All new applications should be written using
 .BR sigaltstack ().

man2/vfork.2

@@ -127,7 +127,7 @@ and to create a unique task structure for the child.
 However, in the bad old days a
 .BR fork (2)
 would require making a complete copy of the caller's data space,
-often needlessly, since usually immediately afterwards an
+often needlessly, since usually immediately afterward an
 .BR exec (3)
 is done.
 Thus, for greater efficiency, BSD introduced the

man3/div.3

@@ -71,7 +71,7 @@ function computes the value
 returns the quotient and remainder in a structure
 named \fIdiv_t\fP that contains
 two integer members (in unspecified order) named \fIquot\fP and \fIrem\fP.
-The quotient is rounded towards zero.
+The quotient is rounded toward zero.
 The result satisfies \fIquot\fP*\fIdenominator\fP+\fIrem\fP = \fInumerator\fP.
 .LP
 The

man3/fenv.3

@@ -156,9 +156,9 @@ The rounding mode determines how the result of floating-point operations
 is treated when the result cannot be exactly represented in the significand.
 Various rounding modes may be provided:
 round to nearest (the default),
-round up (towards positive infinity),
-round down (towards negative infinity), and
-round towards zero.
+round up (toward positive infinity),
+round down (toward negative infinity), and
+round toward zero.
 
 Each of the macros
 .BR FE_TONEAREST ,
@@ -189,13 +189,13 @@ This identifier has one of the following values:
 .IP \-1
 The rounding mode is not determinable.
 .IP 0
-Rounding is towards 0.
+Rounding is toward 0.
 .IP 1
-Rounding is towards nearest number.
+Rounding is toward nearest number.
 .IP 2
-Rounding is towards positive infinity.
+Rounding is toward positive infinity.
 .IP 3
-Rounding is towards negative infinity.
+Rounding is toward negative infinity.
 .PP
 Other values represent machine-dependent, nonstandard rounding modes.
 .PP

man3/fmod.3

@@ -68,7 +68,7 @@ The
 function computes the floating-point remainder of dividing \fIx\fP by
 \fIy\fP.
 The return value is \fIx\fP \- \fIn\fP * \fIy\fP, where \fIn\fP
-is the quotient of \fIx\fP / \fIy\fP, rounded towards zero to an integer.
+is the quotient of \fIx\fP / \fIy\fP, rounded toward zero to an integer.
 .SH "RETURN VALUE"
 On success, these
 functions return the value \fIx\fP\ \-\ \fIn\fP*\fIy\fP,

man3/memchr.3

@@ -62,8 +62,8 @@ The
 function is like the
 .BR memchr ()
 function,
-except that it searches backwards from the end of the \fIn\fP bytes
-pointed to by \fIs\fP instead of forwards from the beginning.
+except that it searches backward from the end of the \fIn\fP bytes
+pointed to by \fIs\fP instead of forward from the beginning.
 
 The
 .BR rawmemchr ()

man3/pthread_attr_setstackaddr.3

@@ -84,12 +84,12 @@ POSIX.1-2008 removes the specification of these functions.
 .I Do not use these functions!
 They cannot be portably used, since they provide no way of specifying
 the direction of growth or the range of the stack.
-For example, on architectures with a stack that grows downwards,
+For example, on architectures with a stack that grows downward,
 .I stackaddr
 specifies the next address past the
 .I highest
 address of the allocated stack area.
-However, on architectures with a stack that grows upwards,
+However, on architectures with a stack that grows upward,
 .I stackaddr
 specifies the
 .I lowest

man3/pthread_attr_setstacksize.3

@@ -100,7 +100,7 @@ if the specified
 is not a multiple of
 .BR STACK_ALIGN
 (16 bytes on most architectures), it may be rounded
-.IR downwards ,
+.IR downward ,
 in violation of POSIX.1-2001, which says that the allocated stack will
 be at least
 .I stacksize

man3/pthread_getattr_np.3

@@ -54,7 +54,7 @@ the stack size,
 which the implementation may align to a suitable boundary.
 .IP *
 and the guard size,
-which the implementation may round upwards to a multiple of the page size,
+which the implementation may round upward to a multiple of the page size,
 or ignore (i.e., treat as 0),
 if the application is allocating its own stack.
 .PP

man3/queue.3

@@ -131,7 +131,7 @@ Entries can be added at the end of a list.
 .IP *
 Entries can be added before another entry.
 .IP *
-They may be traversed backwards, from tail to head.
+They may be traversed backward, from tail to head.
 .PD
 .RE
 .PP

man3/scanf.3

@@ -222,7 +222,7 @@ Reading of characters stops either when this maximum is reached or
 when a nonmatching character is found, whichever happens first.
 Most conversions discard initial white space characters (the exceptions
 are noted below),
-and these discarded characters don't count towards the maximum field width.
+and these discarded characters don't count toward the maximum field width.
 String input conversions store a null terminator (\(aq\\0\(aq)
 to mark the end of the input;
 the maximum field width does not include this terminator.
@@ -389,7 +389,7 @@ the next pointer must be a pointer to
 .B D
 Equivalent to
 .IR ld ;
-this exists only for backwards compatibility.
+this exists only for backward compatibility.
 (Note: thus only in libc4.
 In libc5 and glibc the
 .B %D

man3/trunc.3

@@ -22,7 +22,7 @@
 .\"
 .TH TRUNC 3  2010-09-20 "" "Linux Programmer's Manual"
 .SH NAME
-trunc, truncf, truncl \- round to integer, towards zero
+trunc, truncf, truncl \- round to integer, toward zero
 .SH SYNOPSIS
 .nf
 .B #include <math.h>

man4/st.4

@@ -567,7 +567,7 @@ make sure that a tape is written according to the correct specification.
 .BR MT_ST_CAN_BSR " (Default: false)"
 When read-ahead is used, the tape must sometimes be spaced backward to the
 correct position when the device is closed and the SCSI command to
-space backwards over records is used for this purpose.
+space backward over records is used for this purpose.
 Some older
 drives can't process this command reliably and this option can be used
 to instruct the driver not to use the command.

man5/proc.5

@@ -752,7 +752,7 @@ Virtual memory size in bytes.
 \fIrss\fP %ld
 Resident Set Size: number of pages the process has in real memory.
 This is just the pages which
-count towards text, data, or stack space.
+count toward text, data, or stack space.
 This does not include pages
 which have not been demand-loaded in, or which are swapped out.
 .TP
@@ -1690,11 +1690,11 @@ Number of forks since boot.
 .TP
 \fIprocs_running 6\fP
 Number of processes in runnable state.
-(Linux 2.5.45 onwards.)
+(Linux 2.5.45 onward.)
 .TP
 \fIprocs_blocked 2\fP
 Number of processes blocked waiting for I/O to complete.
-(Linux 2.5.45 onwards.)
+(Linux 2.5.45 onward.)
 .RE
 .TP
 .I /proc/swaps
@@ -2113,7 +2113,7 @@ a single message written on a System V message queue.
 .I /proc/sys/kernel/msgmni
 This file defines the system-wide limit on the number of
 message queue identifiers.
-(This file is only present in Linux 2.4 onwards.)
+(This file is only present in Linux 2.4 onward.)
 .TP
 .I /proc/sys/kernel/msgmnb
 This file defines a system-wide parameter used to initialize the
@@ -2289,7 +2289,7 @@ This value defaults to
 .BR SHMMAX .
 .TP
 .I /proc/sys/kernel/shmmni
-(available in Linux 2.4 and onwards)
+(available in Linux 2.4 and onward)
 This file
 specifies the system-wide maximum number of System V shared memory
 segments that can be created.

man5/services.5

@@ -152,7 +152,7 @@ However, this behavior should not be relied on.)
 
 .\" The following is not true as at glibc 2.8 (a line with a comma is
 .\" ignored by getservent()); it's not clear if/when it was ever true.
-.\"   As a backwards compatibility feature, the slash (/) between the
+.\"   As a backward compatibility feature, the slash (/) between the
 .\"   .I port
 .\"   number and
 .\"   .I protocol

man5/utmp.5

@@ -119,7 +119,7 @@ struct utmp {
     char __unused[20];            /* Reserved for future use */
 };
 
-/* Backwards compatibility hacks */
+/* Backward compatibility hacks */
 #define ut_name ut_user
 #ifndef _NO_UT_TIME
 #define ut_time ut_tv.tv_sec

man7/bootparam.7

@@ -419,7 +419,7 @@ These days it is possible to compile the kernel to use initrd.
 When this feature is enabled, the boot process will load the kernel
 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,
+then /linuxrc is executed; afterward the "real" root file system is mounted,
 and the initrd file system is moved over to /initrd; finally
 the usual boot sequence (e.g., invocation of /sbin/init) is performed.
 

man7/capabilities.7

@@ -656,7 +656,7 @@ The system-wide capability bounding set feature was added
 to Linux starting with kernel version 2.2.11.
 .\"
 .PP
-.B "Capability bounding set from Linux 2.6.25 onwards"
+.B "Capability bounding set from Linux 2.6.25 onward"
 .PP
 From Linux 2.6.25, the
 .I "capability bounding set"

man7/feature_test_macros.7

@@ -205,7 +205,7 @@ earlier glibc 2.1.x versions recognized an equivalent macro named
 .B _ISOC9X_SOURCE
 (because the C99 standard had not then been finalized).
 Although the use of the latter macro is obsolete, glibc continues
-to recognize it for backwards compatibility.
+to recognize it for backward compatibility.
 .TP
 .B _LARGEFILE64_SOURCE
 Expose definitions for the alternative API specified by the

man7/futex.7

@@ -54,7 +54,7 @@ system call.
 .PP
 To "up" a futex, execute the proper assembler instructions that
 will cause the host CPU to atomically increment the integer.
-Afterwards, check if it has in fact changed from 0 to 1, in which case
+Afterward, check if it has in fact changed from 0 to 1, in which case
 there were no waiters and the operation is done.
 This is the noncontended case which is fast and should be common.
 .PP
@@ -90,7 +90,7 @@ The same holds for asynchronous futex waiting.
 .PP
 Initial futex support was merged in Linux 2.5.7
 but with different semantics from those described above.
-Current semantics are available from Linux 2.5.40 onwards.
+Current semantics are available from Linux 2.5.40 onward.
 .SH "NOTES"
 .PP
 To reiterate, bare futexes are not intended as an easy to use

man7/glob.7

@@ -29,7 +29,7 @@ glob \- Globbing pathnames
 Long ago, in Unix V6, there was a program
 .I /etc/glob
 that would expand wildcard patterns.
-Soon afterwards this became a shell built-in.
+Soon afterward this became a shell built-in.
 
 These days there is also a library routine
 .BR glob (3)

man7/man.7

@@ -272,7 +272,7 @@ with
 as the text of the link.
 The
 .I trailer
-will be printed immediately afterwards.
+will be printed immediately afterward.
 When generating HTML this should translate into the HTML command
 \fB<A HREF="\fP\fIurl\fP\fB">\fIlink\fP\fB</A>\fP\fItrailer\fP.
 .\" The following is a kludge to get a paragraph into the listing.

man7/netlink.7

@@ -23,7 +23,7 @@ processes and an internal kernel API for kernel modules.
 The internal kernel interface is not documented in this manual page.
 There is also an obsolete netlink interface
 via netlink character devices; this interface is not documented here
-and is only provided for backwards compatibility.
+and is only provided for backward compatibility.
 
 Netlink is a datagram-oriented service.
 Both

man7/unicode.7

@@ -104,9 +104,9 @@ form (only for BMP characters), whereas
 is the representation of each character by a 4-byte word.
 In addition, there exist two encoding forms
 .B UTF-8
-for backwards compatibility with ASCII processing software and
+for backward compatibility with ASCII processing software and
 .B UTF-16
-for the backwards compatible handling of non-BMP characters up to
+for the backward compatible handling of non-BMP characters up to
 0x10ffff by UCS-2 software.
 .PP
 The UCS characters 0x0000 to 0x007f are identical to those of the