From a823926443b5dacabe7de11df3492e8117012b28 Mon Sep 17 00:00:00 2001 From: Gary Gregory Date: Wed, 14 Aug 2024 07:45:12 -0400 Subject: [PATCH] Normalize spelling --- src/site/xdoc/guide.xml | 8 ++++---- src/site/xdoc/index.xml | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/site/xdoc/guide.xml b/src/site/xdoc/guide.xml index 9d5943d..469ef75 100644 --- a/src/site/xdoc/guide.xml +++ b/src/site/xdoc/guide.xml @@ -126,7 +126,7 @@ and will report any configuration problems that prevent that system being used.

When no particular logging library is specified, then JCL will silently ignore any logging library -that it finds but cannot initialise and continue to look for other alternatives. This is a deliberate +that it finds but cannot initialize and continue to look for other alternatives. This is a deliberate design decision; no application should fail to run because a "guessed" logging library cannot be used. To ensure an exception is reported when a particular logging library cannot be used, use one of the available JCL configuration mechanisms to force that library to be selected (ie disable @@ -215,11 +215,11 @@ Configuration of the behavior of the JCL ultimately depends upon the logging toolkit being used. Please consult the documentation for the chosen logging system.

-JCL is NOT responsible for initialisation, configuration, or shutdown of the underlying logging library. -In many cases logging libraries will automatically initialise/configure themselves when first used, and +JCL is NOT responsible for initialization, configuration, or shutdown of the underlying logging library. +In many cases logging libraries will automatically initialize/configure themselves when first used, and need no explicit shutdown process. In these situations an application can simply use JCL and not depend directly on the API of the underlying logging system in any way. However if the logging library being used -requires special initialisation, configuration, or shutdown, then some logging-library-specific code will +requires special initialization, configuration, or shutdown, then some logging-library-specific code will be required in the application. JCL simply forwards logging method calls to the correct underlying implementation. When writing library code this issue is of course not relevant as the calling application is responsible for handling such issues. diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml index ab10ec5..c9a0295 100644 --- a/src/site/xdoc/index.xml +++ b/src/site/xdoc/index.xml @@ -45,10 +45,10 @@ While logging-implementation independence is not as important for applications as it is for libraries, using commons-logging does allow the application to change to a different logging implementation without recompiling code.

-Note that commons-logging does not attempt to initialise or terminate the underlying +Note that commons-logging does not attempt to initialize or terminate the underlying logging implementation that is used at runtime; that is the responsibility of the application. However many popular logging implementations do automatically -initialise themselves; in this case an application may be able to avoid +initialize themselves; in this case an application may be able to avoid containing any code that is specific to the logging implementation used.