svn commit: r48481 - head/en_US.ISO8859-1/books/porters-handbook/porting-dads

[Jason Helfman]

Author: jgh
Date: Sun Mar 27 19:05:31 2016
New Revision: 48481
URL: https://svnweb.freebsd.org/changeset/doc/48481

Log:
  - stick to American English spelling of behavior
  
  Reported by:	wblock

Modified:
  head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml

Modified: head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Sun Mar 27 18:41:27 2016	(r48480)
+++ head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Sun Mar 27 19:05:31 2016	(r48481)
@@ -656,16 +656,16 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
       cheap in performance-critical applications.  In general, try
       hard to avoid syscalls if possible.</para>
 
-    <para>Do not rely on &linux;-specific socket behaviour.  In
+    <para>Do not rely on &linux;-specific socket behavior.  In
       particular, default socket buffer sizes are different (call
       &man.setsockopt.2; with <literal>SO_SNDBUF</literal> and
       <literal>SO_RCVBUF</literal>, and while &linux;'s &man.send.2;
       blocks when the socket buffer is full, &os;'s will fail and
       set <literal>ENOBUFS</literal> in errno.</para>
 
-    <para>If relying on non-standard behaviour is required,
+    <para>If relying on non-standard behavior is required,
       encapsulate it properly into a generic <acronym>API</acronym>,
-      do a check for the behaviour in the configure stage, and stop
+      do a check for the behavior in the configure stage, and stop
       if it is missing.</para>
 
     <para>Check the