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-fileupload.git


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

commit f693cd097db8f592e74b6e736e9dee9cc38cf6a8
Author: Gary Gregory <garydgreg...@gmail.com>
AuthorDate: Mon Mar 30 11:21:32 2020 -0400

    Standardize on American English spelling of 'behavior'.
---
 src/site/fml/faq.fml               | 2 +-
 src/site/xdoc/security-reports.xml | 4 ++--
 src/site/xdoc/using.xml            | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index 62d2be9..3658324 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -206,7 +206,7 @@ try {
             In other words, it still declares itself as serializable, and 
deserializable to the JVM. In practice,
             however, an attempt to deserialize an instance of DiskFileItem 
will trigger an Exception. In the unlikely
             case, that your application depends on the deserialization of 
DiskFileItems, you can revert to the
-            previous behaviour by setting the system property 
"org.apache.commons.fileupload.disk.DiskFileItem.serializable"
+            previous behavior by setting the system property 
"org.apache.commons.fileupload.disk.DiskFileItem.serializable"
             to "true".
           </p>
         </answer>
diff --git a/src/site/xdoc/security-reports.xml 
b/src/site/xdoc/security-reports.xml
index 283456f..181202d 100644
--- a/src/site/xdoc/security-reports.xml
+++ b/src/site/xdoc/security-reports.xml
@@ -43,7 +43,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>
 
@@ -78,7 +78,7 @@
             In other words, it still declares itself as serializable, and 
deserializable to the JVM. In practice,
             however, an attempt to deserialize an instance of DiskFileItem 
will trigger an Exception. In the unlikely
             case, that your application depends on the deserialization of 
DiskFileItems, you can revert to the
-            previous behaviour by setting the system property 
"org.apache.commons.fileupload.disk.DiskFileItem.serializable"
+            previous behavior by setting the system property 
"org.apache.commons.fileupload.disk.DiskFileItem.serializable"
             to "true".
           </p>
         </subsection>
diff --git a/src/site/xdoc/using.xml b/src/site/xdoc/using.xml
index 8b2dfd5..8d1f0b4 100644
--- a/src/site/xdoc/using.xml
+++ b/src/site/xdoc/using.xml
@@ -337,8 +337,8 @@ byte[] data = item.get();
     <section name="Interaction with virus scanners">
       <p>
         Virus scanners running on the same system as the web container can 
cause
-        some unexpected behaviours for applications using FileUpload. This 
section
-        describes some of the behaviours that you might encounter, and provides
+        some unexpected behaviors for applications using FileUpload. This 
section
+        describes some of the behaviors that you might encounter, and provides
         some ideas for how to handle them.
       </p>
       <p>

Reply via email to