[Bug-mcron] mcron: typos in manual

[Ralf Wildenhues]

Hello Dale,

I was hinted to your post on the proofreaders list (it's been a while
;-)

Here's a patch to fix some typos, and change some en_UK spellings to
en_US (mostly behaviour -> behavior), against CVS sources of mcron.

Cheers,
Ralf

        * mcron.texinfo.in: Fix some typos.

Index: mcron.texinfo.in
===================================================================
RCS file: /sources/mcron/mcron/mcron.texinfo.in,v
retrieving revision 1.5
diff -u -r1.5 mcron.texinfo.in
--- mcron.texinfo.in    16 Apr 2006 22:10:44 -0000      1.5
+++ mcron.texinfo.in    7 Aug 2006 20:09:06 -0000
@@ -100,7 +100,7 @@
 * Invoking mcron::               
 * Invoking cron or crond::       
 * Invoking crontab::
-* Behaviour on laptops::
+* Behavior on laptops::
 * Exit codes::                  
 
 Guile modules
@@ -132,10 +132,10 @@
 are written in scheme, allowing at the same time simple command
 execution instructions and very much more flexible ones to be composed
 than the original Vixie format.  This has several useful advantages
-over the original idea.  (Changes to user crontabs are signalled
+over the original idea.  (Changes to user crontabs are signaled
 directly to mcron by the crontab program; cron must still scan the
 /etc/crontab file once every minute, although use of this file is
-highly discouraged and this behaviour can be turned off).
+highly discouraged and this behavior can be turned off).
 
 @cindex advantages of mcron
 @itemize @bullet
@@ -144,7 +144,7 @@
 run jobs once an hour, or even just once a day.
 @item
 Can easily allow for finer time-points to be specified,
-i.e. seconds.  In principle this could be extended to microseconds, but
+i.e., seconds.  In principle this could be extended to microseconds, but
 this is not implemented.
 @item
 Times can be more or less regular.  For example, a job that runs
@@ -323,7 +323,7 @@
 @cindex list time specification
 If the first argument to the @code{job} function is a list, it is
 taken to be program code made up of the functions @code{(next-second
-. args)}, @code{(next-minute...)}, etc, where the optional arguments
+. args)}, @code{(next-minute...)}, etc., where the optional arguments
 can be supplied with the @code{(range)} function above (these
 functions are analogous to the ones above except that they implicitly
 assume the current time; it is supplied by the mcron core when the
@@ -459,7 +459,7 @@
 o'clock appointment), and then finds the next one o'clock schedule.
 
 The following simple command is the correct way to specify this
-behaviour.
+behavior.
 
 @example
 (job '(next-hour '(1 2)) "my-program")
@@ -511,7 +511,7 @@
 @cindex vixie compatibility
 @cindex compatibility, vixie
 @emph{NOTE} that this section is definitive.  If there is a difference in
-behaviour between the mcron program and this part of the manual, then
+behavior between the mcron program and this part of the manual, then
 there is a bug in the program.  This section is also copied verbatim
 from Paul Vixie's documentation for his cron program, and his
 copyright notice is duly reproduced below.
@@ -526,7 +526,7 @@
 effect.  However, if it appears on its own, the effect is to say
 ``don't run on any particular day of the month, only take the week-day
 specification into account.'' Mcron has been coded to mimic this
-behaviour as a special case (unmodified mcron logic implies that this
+behavior as a special case (unmodified mcron logic implies that this
 date specification would cause jobs to run on the last day of the
 previous month).
 
@@ -541,7 +541,7 @@
 @cindex environment variables, shell
 @cindex /etc/passwd
 3.  Somewhere it says that cron sets the SHELL environment variable to
-/bin/sh, and elsewhere it implies that the default behaviour is for
+/bin/sh, and elsewhere it implies that the default behavior is for
 the user's default shell to be used to execute commands.  Mcron sets
 the variable and runs the command in the user's default shell, as
 advertised by the /etc/passwd file.
@@ -565,7 +565,7 @@
 documentation (don't take credit for my work), mark your changes (don't
 get me blamed for your possible bugs), don't alter or remove this
 notice.  May be sold if buildable source is provided to buyer.  No
-warrantee of any kind, express or implied, is included with this
+warranty of any kind, express or implied, is included with this
 software; use at your own risk, responsibility for damages (if any) to
 anyone resulting from the use of this software rests entirely with the
 user.
@@ -801,7 +801,7 @@
 * Invoking mcron::               
 * Invoking cron or crond::       
 * Invoking crontab::
-* Behaviour on laptops::
+* Behavior on laptops::
 * Exit codes::                  
 @end menu
 
@@ -890,9 +890,9 @@
 
 @node Invoking cron or crond, Invoking crontab, Invoking mcron, Invoking
 @section Invoking cron or crond
address@hidden cron, invokation
address@hidden cron, invocation
 @cindex invoking cron
address@hidden crond, invokation
address@hidden crond, invocation
 @cindex invoking crond
 @cindex @CONFIG_SPOOL_DIR@
 @cindex @CONFIG_SOCKET_FILE@
@@ -964,7 +964,7 @@
 
 @end table
 
address@hidden Invoking crontab, Behaviour on laptops, Invoking cron or crond, 
Invoking
address@hidden Invoking crontab, Behavior on laptops, Invoking cron or crond, 
Invoking
 @section Invoking crontab
 @cindex crontab, invoking
 @cindex invoking crontab
@@ -1031,11 +1031,11 @@
 @end table
 
 
address@hidden Behaviour on laptops, Exit codes, Invoking crontab, Invoking
address@hidden Behaviour on laptops
address@hidden Behavior on laptops, Exit codes, Invoking crontab, Invoking
address@hidden Behavior on laptops
 @cindex laptops
 @cindex power suspend
-While mcron has not been designed to work anachronistically, the behaviour of
+While mcron has not been designed to work anachronistically, the behavior of
 mcron when a laptop emerges from a suspended state is well defined, and the
 following description explains what happens in this situation.
 
@@ -1047,7 +1047,7 @@
 proper times.
 
 
address@hidden Exit codes,  , Behaviour on laptops, Invoking
address@hidden Exit codes,  , Behavior on laptops, Invoking
 @section Exit codes
 @cindex exit codes
 @cindex error conditions
@@ -1062,7 +1062,7 @@
 @item 1
 An attempt has been made to start cron but there is already a
 @CONFIG_PID_FILE@ file.  If there really is no other cron daemon
-running (this does not include invokations of mcron) then you should
+running (this does not include invocations of mcron) then you should
 remove this file before attempting to run cron.
 
 @item 2
@@ -1123,7 +1123,7 @@
 
 @item 15
 Crontab has been run without any arguments at all.  There is no default
-behaviour in this case.
+behavior in this case.
 
 @item 16
 Cron has been run by a user other than root.
@@ -1201,7 +1201,7 @@
 run.  @var{displayable} should be a string, and is only for the use of
 humans; it can be anything which identifies or simply gives a clue as
 to the purpose or function of this job.  @var{configuration-time} is
-the time from which the first invokation of this job should be
+the time from which the first invocation of this job should be
 computed.  Finally, @var{configuration-user} should be the passwd entry
 for the user under whose personality the job is to run.
 @end deffn
@@ -1317,7 +1317,7 @@
 @deffn{Scheme procedure} read-vixie-file name . parse-line
 
 This procedure attempts to open the named file, and if it fails will
-return silently.  Otherwise, the behaviour is identical to
+return silently.  Otherwise, the behavior is identical to
 @code{read-vixie-port} above.
 
 @end deffn