This is an automated email from the ASF dual-hosted git repository.
garydgregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-digester.git
The following commit(s) were added to refs/heads/master by this push:
new 0cb7ba35 Normalize spelling
0cb7ba35 is described below
commit 0cb7ba358ad3bd0b8a6b4059cc46d20f03a3d720
Author: Gary Gregory <[email protected]>
AuthorDate: Sat Jul 4 18:09:29 2026 -0400
Normalize spelling
---
commons-digester3-examples/api/document-markup/readme.txt | 2 +-
src/site/fml/guide/faq.fml | 2 +-
src/site/xdoc/guide/core.xml | 6 +++---
src/site/xdoc/guide/plugins.xml | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/commons-digester3-examples/api/document-markup/readme.txt
b/commons-digester3-examples/api/document-markup/readme.txt
index 54970be9..d01cfd71 100644
--- a/commons-digester3-examples/api/document-markup/readme.txt
+++ b/commons-digester3-examples/api/document-markup/readme.txt
@@ -49,7 +49,7 @@ run the example directly.
The primary use of the Digester is to process XML configuration files.
Such files do not typically interleave text and child elements in the
-style encountered with document markup. The standard Digester behaviour is
+style encountered with document markup. The standard Digester behavior is
therefore to accumulate all text within an XML element's body (of which there
is
expected to be only one "segment") and present it to a Rule or user method
as a single string.
diff --git a/src/site/fml/guide/faq.fml b/src/site/fml/guide/faq.fml
index 5a41edcf..a7e3a924 100644
--- a/src/site/fml/guide/faq.fml
+++ b/src/site/fml/guide/faq.fml
@@ -66,7 +66,7 @@ based processors).
</p>
<p>
This means that the errors reported by the validation of the schema will
appear in the
-Digester logs but the processing will continue. To change this behaviour, call
+Digester logs but the processing will continue. To change this behavior, call
<code>digester.setErrorHandler</code> with a more suitable implementation.
</p></answer>
</faq>
diff --git a/src/site/xdoc/guide/core.xml b/src/site/xdoc/guide/core.xml
index ef8e97c5..53759852 100644
--- a/src/site/xdoc/guide/core.xml
+++ b/src/site/xdoc/guide/core.xml
@@ -275,7 +275,7 @@ such arrangements are called <em>element matching
patterns</em>.</p>
<p>The Digester can be configured to use different pattern-matching algorithms
via the Digester.setRules method. However for the vast majority of cases, the
-default matching algorithm works fine. The default pattern matching behaviour
+default matching algorithm works fine. The default pattern matching behavior
is described below.</p>
<p>A very simple element matching pattern is a simple string like "a". This
@@ -329,7 +329,7 @@ reverse order. In other words - the order is first in, last
out.</p>
<p>Note that wildcard patterns are ignored if an explicit match can be found
(and when multiple wildcard patterns match, only the longest, ie most
explicit, pattern is considered a match). The result is that rules can be
-added for "an <a> tag anywhere", but then for that behaviour to be
+added for "an <a> tag anywhere", but then for that behavior to be
explicitly overridden for specific cases, eg "but not an <a> that is a
direct child of an <x>". Therefore if you have rules A and B registered
for
pattern "*/a" then want to add an additional rule C for pattern "x/a" only,
@@ -941,7 +941,7 @@ following as part of your Digester initialization:</p>
is an advanced <code>Rules</code> implementation which does not build on the
default pattern matching rules.
It uses a pluggable <a
href="../apidocs/org/apache/commons/digester3/RegexMatcher.html">RegexMatcher</a>
implementation to test
if a path matches the pattern for a Rule. All matching rules are returned
-(note that this behaviour differs from longest matching rule of the default
+(note that this behavior differs from longest matching rule of the default
pattern matching rules). See the Java Docs for more details.
</p>
<p>
diff --git a/src/site/xdoc/guide/plugins.xml b/src/site/xdoc/guide/plugins.xml
index 6c34cf6c..c19d2e12 100644
--- a/src/site/xdoc/guide/plugins.xml
+++ b/src/site/xdoc/guide/plugins.xml
@@ -235,7 +235,7 @@ pattern should not include any wildcard characters.</p>
earlier ones.</p>
<p>
In situations where a user <i>might</i> want to specify a custom class,
-but will often want "default" behaviour, a PluginCreateRule can specify
+but will often want "default" behavior, a PluginCreateRule can specify
a default class. If the user then omits the "plugin-id" attribute on
the matching XML element, an instance of the default class will be
created.</p>
@@ -294,7 +294,7 @@ rules are.</p>
<p>
The RuleFinder list is carefully ordered; classes which look at the
user-provided data in the declaration come first, and classes which look in
-"well-known places" come later so that users can override default behaviour by
+"well-known places" come later so that users can override default behavior by
providing the appropriate tags on the plugin declaration.</p>
<p>
See the javadoc on the different Finder classes for information on what
