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


The following commit(s) were added to refs/heads/master by this push:
     new 610117a  Normalize to US English spelling.
610117a is described below

commit 610117ab3294d562a173109eb57a1b5162cb1e48
Author: Gary Gregory <[email protected]>
AuthorDate: Mon Feb 8 14:06:20 2021 -0500

    Normalize to US English spelling.
---
 .../java/org/apache/commons/logging/impl/ServletContextCleaner.java | 2 +-
 src/test/java/org/apache/commons/logging/AltHashtableTestCase.java  | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git 
a/src/main/java/org/apache/commons/logging/impl/ServletContextCleaner.java 
b/src/main/java/org/apache/commons/logging/impl/ServletContextCleaner.java
index 56fb226..4bfe2ed 100644
--- a/src/main/java/org/apache/commons/logging/impl/ServletContextCleaner.java
+++ b/src/main/java/org/apache/commons/logging/impl/ServletContextCleaner.java
@@ -86,7 +86,7 @@ public class ServletContextCleaner implements 
ServletContextListener {
         // the LogFactory instance that is visible from the ancestor
         // classloader. However the concrete logging library it points
         // to is expected to have been loaded via the TCCL, so the
-        // underlying logging lib is only initialised/configured once.
+        // underlying logging lib is only initialized/configured once.
         // These references from ancestor LogFactory classes down to
         // TCCL classloaders are held via weak references and so should
         // be released but there are circumstances where they may not.
diff --git a/src/test/java/org/apache/commons/logging/AltHashtableTestCase.java 
b/src/test/java/org/apache/commons/logging/AltHashtableTestCase.java
index b314992..9dad136 100644
--- a/src/test/java/org/apache/commons/logging/AltHashtableTestCase.java
+++ b/src/test/java/org/apache/commons/logging/AltHashtableTestCase.java
@@ -49,7 +49,7 @@ public class AltHashtableTestCase extends TestCase {
      * <p>
      * This does make the assumption that whatever JVM we are running in
      * doesn't initialise classes until they are actually referenced (ie the
-     * LogFactory class hasn't been initialised before this method is called).
+     * LogFactory class hasn't been initialized before this method is called).
      * This is true of all JVMs I know of; and if it isn't then this test will
      * fail and someone will tell us.
      */
@@ -67,10 +67,10 @@ public class AltHashtableTestCase extends TestCase {
      */
     public void testType() {
         // Here, the reference to the LogFactory class should cause the
-        // class to be loaded and initialised. It will see the property
+        // class to be loaded and initialized. It will see the property
         // set and use the AltHashtable class. If other tests in this
         // class have already been run within the same classloader then
-        // LogFactory will already have been initialised, but that
+        // LogFactory will already have been initialized, but that
         // doesn't change the effectiveness of this test.
         assertTrue(LogFactory.factories instanceof AltHashtable);
     }

Reply via email to