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 8b5918e Typo
8b5918e is described below
commit 8b5918e552efc075f5bb517f78227a63fe5e8044
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Nov 7 15:17:41 2025 -0500
Typo
---
CONTRIBUTING.md | 2 +-
src/site/xdoc/guide.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4e5f72a..e702622 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -69,7 +69,7 @@ Making Changes
+ Respect the original code style:
+ Only use spaces for indentation; you can check for unnecessary whitespace
with `git diff` before committing.
+ Create minimal diffs - disable _On Save_ actions like _Reformat Source
Code_ or _Organize Imports_. If you feel the source code should be reformatted
create a separate PR for this change first.
-+ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible but is
a best-practice.
++ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible but is
a best practice.
Unit tests are typically in the `src/test/java` directory.
+ Run a successful build using the default [Maven](https://maven.apache.org/)
goal with `mvn`; that's `mvn` on the command line by itself.
+ Write a pull request description that is detailed enough to understand what
the pull request does, how, and why.
diff --git a/src/site/xdoc/guide.xml b/src/site/xdoc/guide.xml
index 732b51b..eda8f3c 100644
--- a/src/site/xdoc/guide.xml
+++ b/src/site/xdoc/guide.xml
@@ -392,7 +392,7 @@ The general principles are fairly clear.Enterprise
practices are a bit more invo
and it is not always as clear as to why they are important.
</p>
<p>
-Enterprise best-practice principles apply to middleware components
+Enterprise best practice principles apply to middleware components
and tooling that is expected to execute in an "Enterprise" level
environment.
These issues relate to Logging as Internationalization,
