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

garydgregory pushed a commit to branch 1.x
in repository https://gitbox.apache.org/repos/asf/commons-fileupload.git


The following commit(s) were added to refs/heads/1.x by this push:
     new 89a9290a Normalize spelling
89a9290a is described below

commit 89a9290a608e755f432240bcd8008521fba863d6
Author: Gary Gregory <[email protected]>
AuthorDate: Sat Jul 4 19:21:50 2026 -0400

    Normalize spelling
---
 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 7bd56fa2..62f99760 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 ae2cebbc..f1525638 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>
 
@@ -96,7 +96,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 768861a3..d1e2e7ec 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