Americanise^H^ze (s/behaviour/behavior/g).

svn path=/head/; revision=13198

en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml

@@ -20,7 +20,7 @@
       A device driver is the software component of the operating
       system that controls a specific device.  There are also
       so-called pseudo-devices where a device driver emulates the
-      behaviour of a device in software without any particular
+      behavior of a device in software without any particular
       underlying hardware.  Device drivers can be compiled into the
       system statically or loaded on demand through the dynamic kernel
       linker facility `kld'.</para>

en_US.ISO8859-1/books/developers-handbook/driverbasics/chapter.sgml

@@ -20,7 +20,7 @@
       A device driver is the software component of the operating
       system that controls a specific device.  There are also
       so-called pseudo-devices where a device driver emulates the
-      behaviour of a device in software without any particular
+      behavior of a device in software without any particular
       underlying hardware.  Device drivers can be compiled into the
       system statically or loaded on demand through the dynamic kernel
       linker facility `kld'.</para>

en_US.ISO8859-1/books/faq/book.sgml

@@ -3525,7 +3525,7 @@ quit</programlisting>
                 set various timings, mostly the defaults will be
                 sufficient, but sometimes, setting the wait states on RAM
                 too low, or setting the <quote>RAM Speed: Turbo</quote> option, or
-                similar in the BIOS will cause strange behaviour. A
+                similar in the BIOS will cause strange behavior. A
                 possible idea is to set to BIOS defaults, but it might be
                 worth noting down your settings first!</para>
             </listitem>
@@ -3974,7 +3974,7 @@ quit</programlisting>
             cards and internal modems) not working even though they worked
             under FreeBSD 3.x.</para>
 
-          <para>The reasons for this behaviour are explained by the following
+          <para>The reasons for this behavior are explained by the following
             e-mail, posted to the freebsd-questions mailing list by Peter
             Wemm, in answer to a question about an internal modem that was
             no longer found after an upgrade to FreeBSD 4.x (the comments

en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml

@@ -320,7 +320,7 @@ PRI_LANG?=	en_US.ISO8859-1
        
 	<para>The <literal>.if defined(DOC)</literal> line is an example of
 	  a <application>make</application> conditional which, like in
-	  other programs, defines behaviour if some condition is true or
+	  other programs, defines behavior if some condition is true or
 	  if it is false.  <literal>defined</literal> is a function which
 	  returns whether the variable given is defined or not.</para>
 

en_US.ISO8859-1/books/handbook/config/chapter.sgml

@@ -921,7 +921,7 @@ kern.maxfiles: 2088 -> 5000</screen>
     	  back to disk.  (Meta-data updates are updates to
 	  non-content data like inodes or directories.)</para>
 	
-	<para>Historically, the default behaviour was to write out
+	<para>Historically, the default behavior was to write out
 	  meta-data updates synchronously.  If a directory had been
 	  changed, the system waited until the change was actually
 	  written to disk.  The file data buffers (file contents) were

en_US.ISO8859-1/books/porters-handbook/book.sgml

@@ -718,7 +718,7 @@ lib/X11/oneko/mouse.xpm
 
 	    <listitem>
 	      <para>Changes in the packing list or the install-time
-		behaviour of the package (e.g. change to a script
+		behavior of the package (e.g. change to a script
 		which generates initial data for the package, like ssh
 		host keys).</para>
 	    </listitem>
@@ -1081,7 +1081,7 @@ MASTER_SITE_SUBDIR=   applications</programlisting>
         <para>Many ports depend on other ports.  There are five variables that
           you can use to ensure that all the required bits will be on the
           user's machine.  There are also some pre-supported dependency
-          variables for common cases, plus a few more to control the behaviour
+          variables for common cases, plus a few more to control the behavior
           of dependencies.</para>
 
         <sect2>
@@ -1264,7 +1264,7 @@ MASTER_SITE_SUBDIR=   applications</programlisting>
             will always descend to the JPEG port and extract it.</para>
 
           <para>Do not use <makevar>DEPENDS</makevar> unless there is no other
-            way the behaviour you want can be accomplished.  It will cause the
+            way the behavior you want can be accomplished.  It will cause the
             other port to always be built (and installed, by default), and the
             dependency will go into the packages as well.  If this is really
             what you need, you should probably write it as