Fix typos throughout codebase.

* NEWS:
* doc/ref/api-control.texi:
* doc/ref/api-data.texi:
* doc/ref/api-debug.texi:
* doc/ref/api-deprecated.texi:
* doc/ref/api-evaluation.texi:
* doc/ref/api-foreign.texi:
* doc/ref/api-i18n.texi:
* doc/ref/api-io.texi:
* doc/ref/api-languages.texi:
* doc/ref/api-macros.texi:
* doc/ref/api-memory.texi:
* doc/ref/api-modules.texi:
* doc/ref/api-options.texi:
* doc/ref/api-peg.texi:
* doc/ref/api-procedures.texi:
* doc/ref/api-scheduling.texi:
* doc/ref/api-undocumented.texi:
* doc/ref/api-utility.texi:
* doc/ref/expect.texi:
* doc/ref/goops.texi:
* doc/ref/misc-modules.texi:
* doc/ref/posix.texi:
* doc/ref/repl-modules.texi:
* doc/ref/scheme-ideas.texi:
* doc/ref/scheme-scripts.texi:
* doc/ref/srfi-modules.texi:
* gc-benchmarks/larceny/dynamic.sch:
* gc-benchmarks/larceny/twobit-input-long.sch:
* gc-benchmarks/larceny/twobit.sch:
* libguile/gc.h:
* libguile/ioext.c:
* libguile/list.c:
* libguile/options.c:
* libguile/posix.c:
* libguile/threads.c:
* module/ice-9/boot-9.scm:
* module/ice-9/optargs.scm:
* module/ice-9/ports.scm:
* module/ice-9/pretty-print.scm:
* module/ice-9/psyntax.scm:
* module/language/elisp/parser.scm:
* module/language/tree-il/compile-bytecode.scm:
* module/srfi/srfi-37.scm:
* module/srfi/srfi-43.scm:
* module/statprof.scm:
* module/texinfo/reflection.scm:
* test-suite/tests/eval.test:
* test-suite/tests/fluids.test:
Fix typos.

Signed-off-by: Ludovic Courtès <ludo@gnu.org>

libguile/gc.h

@@ -194,7 +194,7 @@ scm_double_cell (scm_t_bits car, scm_t_bits cbr,
      advantage of strict C aliasing rules which say that it's OK to
      interchange the initialization above and the one below when the
      pointer types appear to differ sufficiently.  We don't want that,
-     of course.  GCC allows this behaviour to be disabled with the
+     of course.  GCC allows this behavior to be disabled with the
      -fno-strict-aliasing option, but would also need to be supplied
      by Guile users.  Instead, the following statements prevent the
      reordering.
@@ -227,7 +227,7 @@ scm_words (scm_t_bits car, uint32_t n_words)
      advantage of strict C aliasing rules which say that it's OK to
      interchange the initialization above and the one below when the
      pointer types appear to differ sufficiently.  We don't want that,
-     of course.  GCC allows this behaviour to be disabled with the
+     of course.  GCC allows this behavior to be disabled with the
      -fno-strict-aliasing option, but would also need to be supplied
      by Guile users.  Instead, the following statements prevent the
      reordering.

libguile/ioext.c

@@ -77,7 +77,7 @@ SCM_DEFINE (scm_redirect_port, "redirect-port", 2, 0, 0,
 	    "After the redirection the two ports will share a file position\n"
 	    "and file status flags.\n\n"
 	    "The return value is unspecified.\n\n"
-	    "Unexpected behaviour can result if both ports are subsequently used\n"
+	    "Unexpected behavior can result if both ports are subsequently used\n"
 	    "and the original and/or duplicate ports are buffered.\n\n"
 	    "This procedure does not have any side effects on other ports or\n"
 	    "revealed counts.")

libguile/list.c

@@ -308,7 +308,7 @@ SCM_DEFINE (scm_append_x, "append!", 0, 0, 1,
 
 SCM_DEFINE (scm_last_pair, "last-pair", 1, 0, 0, 
            (SCM lst),
-	    "Return the last pair in @var{lst}, signalling an error if\n"
+	    "Return the last pair in @var{lst}, signaling an error if\n"
 	    "@var{lst} is circular.")
 #define FUNC_NAME s_scm_last_pair
 {

libguile/options.c

@@ -55,7 +55,7 @@
  * Some definitions:
  *
  * Run time options in Guile are arranged in groups.  Each group
- * affects a certain aspect of the behaviour of the library.
+ * affects a certain aspect of the behavior of the library.
  *
  * An "options interface procedure" manages one group of options.  It
  * can be used to check or set options, or to get documentation for

libguile/posix.c

@@ -389,7 +389,7 @@ SCM_DEFINE (scm_setgroups, "setgroups", 1, 0, 0,
 SCM_DEFINE (scm_getpwuid, "getpw", 0, 1, 0,
             (SCM user),
 	    "Look up an entry in the user database.  @var{user} can be an\n"
-	    "integer, a string, or omitted, giving the behaviour of\n"
+	    "integer, a string, or omitted, giving the behavior of\n"
 	    "@code{getpwuid}, @code{getpwnam} or @code{getpwent}\n"
 	    "respectively.")
 #define FUNC_NAME s_scm_getpwuid
@@ -459,7 +459,7 @@ SCM_DEFINE (scm_setpwent, "setpw", 0, 1, 0,
 SCM_DEFINE (scm_getgrgid, "getgr", 0, 1, 0,
             (SCM name),
 	    "Look up an entry in the group database.  @var{name} can be an\n"
-	    "integer, a string, or omitted, giving the behaviour of\n"
+	    "integer, a string, or omitted, giving the behavior of\n"
 	    "@code{getgrgid}, @code{getgrnam} or @code{getgrent}\n"
 	    "respectively.")
 #define FUNC_NAME s_scm_getgrgid
@@ -725,7 +725,7 @@ SCM_DEFINE (scm_waitpid, "waitpid", 1, 1, 0,
 	    "has terminated or (optionally) stopped.  Normally it will\n"
 	    "suspend the calling process until this can be done.  If more than one\n"
 	    "child process is eligible then one will be chosen by the operating system.\n\n"
-	    "The value of @var{pid} determines the behaviour:\n\n"
+	    "The value of @var{pid} determines the behavior:\n\n"
 	    "@table @r\n"
 	    "@item @var{pid} greater than 0\n"
 	    "Request status information from the specified child process.\n"

libguile/threads.c

@@ -902,7 +902,7 @@ enum scm_mutex_kind {
   /* An unowned mutex is like a standard mutex, except that it can be
      unlocked by any thread.  A corrolary of this behavior is that a
      thread's attempt to lock a mutex that it already owns will block
-     instead of signalling an error, as it could be that some other
+     instead of signaling an error, as it could be that some other
      thread unlocks the mutex, allowing the owner thread to proceed.
      This kind of mutex is a bit strange and is here for use by
      SRFI-18.  */