This is an automated email from the ASF dual-hosted git repository.

ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-compress.git


The following commit(s) were added to refs/heads/master by this push:
     new 5378394  Standardize on American English spelling of 'behavior'.
5378394 is described below

commit 53783948460ec0db588b5cbf1b60d8f3569a048c
Author: Gary Gregory <garydgreg...@gmail.com>
AuthorDate: Mon Mar 30 11:09:28 2020 -0400

    Standardize on American English spelling of 'behavior'.
---
 .../commons/compress/archivers/zip/X5455_ExtendedTimestamp.java       | 4 ++--
 .../org/apache/commons/compress/compressors/bzip2/BZip2Utils.java     | 2 +-
 src/site/xdoc/conventions.xml                                         | 2 +-
 src/site/xdoc/security-reports.xml                                    | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git 
a/src/main/java/org/apache/commons/compress/archivers/zip/X5455_ExtendedTimestamp.java
 
b/src/main/java/org/apache/commons/compress/archivers/zip/X5455_ExtendedTimestamp.java
index acec5b0..bfc0b0d 100644
--- 
a/src/main/java/org/apache/commons/compress/archivers/zip/X5455_ExtendedTimestamp.java
+++ 
b/src/main/java/org/apache/commons/compress/archivers/zip/X5455_ExtendedTimestamp.java
@@ -30,7 +30,7 @@ import java.util.zip.ZipException;
  * integers representing seconds since UNIX epoch (Jan 1st, 1970, UTC).
  * This field improves on zip's default timestamp granularity, since it
  * allows one to store additional timestamps, and, in addition, the timestamps
- * are stored using per-second granularity (zip's default behaviour can only 
store
+ * are stored using per-second granularity (zip's default behavior can only 
store
  * timestamps to the nearest <em>even</em> second).
  * </p><p>
  * Unfortunately, 32 (signed) bits can only store dates up to the year 2037,
@@ -46,7 +46,7 @@ import java.util.zip.ZipException;
  * most recent time file/directory was opened
  * (e.g., read from disk).  Many people disable
  * their operating systems from updating this value
- * using the NOATIME mount option to optimize disk behaviour,
+ * using the NOATIME mount option to optimize disk behavior,
  * and thus it's not always reliable.  In those cases
  * it's always equal to modifyTime.
  * </li>
diff --git 
a/src/main/java/org/apache/commons/compress/compressors/bzip2/BZip2Utils.java 
b/src/main/java/org/apache/commons/compress/compressors/bzip2/BZip2Utils.java
index 981d0fc..68c94d4 100644
--- 
a/src/main/java/org/apache/commons/compress/compressors/bzip2/BZip2Utils.java
+++ 
b/src/main/java/org/apache/commons/compress/compressors/bzip2/BZip2Utils.java
@@ -79,7 +79,7 @@ public abstract class BZip2Utils {
     /**
      * Maps the given file name to the name that the file should have after
      * compression with bzip2. Currently this method simply appends the suffix
-     * ".bz2" to the file name based on the standard behaviour of the "bzip2"
+     * ".bz2" to the file name based on the standard behavior of the "bzip2"
      * program, but a future version may implement a more complex mapping if
      * a new widely used naming pattern emerges.
      *
diff --git a/src/site/xdoc/conventions.xml b/src/site/xdoc/conventions.xml
index f1a93b7..59ec3c5 100644
--- a/src/site/xdoc/conventions.xml
+++ b/src/site/xdoc/conventions.xml
@@ -30,7 +30,7 @@
       <section name="Multithreading">
             <p>
             Commons Compress does not aim to be threadsafe at the moment. But 
the developers
-            agreed to document multithreading behaviour in the javadocs.
+            agreed to document multithreading behavior in the javadocs.
             </p>
             <p>
             We use some of the annotations from 
diff --git a/src/site/xdoc/security-reports.xml 
b/src/site/xdoc/security-reports.xml
index 9d37109..1ae3550 100644
--- a/src/site/xdoc/security-reports.xml
+++ b/src/site/xdoc/security-reports.xml
@@ -50,7 +50,7 @@
         list</a>.</p>
 
         <p>If you have encountered an unlisted security vulnerability
-        or other unexpected behaviour that has security impact, or if
+        or other unexpected behavior that has security impact, or if
         the descriptions here are incomplete, please report them
         privately to the Apache Security Team. Thank you.</p>
 

Reply via email to