Release changelog for version 2.21.1

src/site/_release-notes/_2.21.1.adoc

@@ -20,29 +20,15 @@
 
 Release date:: 2023-10-20
 
-This release primarily focuses on enhancements to our OSGi and JPMS support and contains several bug fixes.
-It will be the first release built and signed by the CI using the https://keyserver.ubuntu.com/pks/lookup?search=077E8893A6DCC33DD4A4D5B256E73BA9A0B592D0&op=index[ASF Logging Services Release Manager GPG key], which is shared in https://www.apache.org/dist/logging/KEYS[KEYS].
+This patch release contains only the fix of a `log4j-jcl` bug that prevents it from connecting with `commons-logging`.
 
-The Log4j 2.21.0 API, as well as the other artifacts, maintains binary compatibility with the previous release.
+The Log4j 2.21.1 API, as well as the other artifacts, maintains binary compatibility with the previous release.
 
-Apache Log4j 2.21.0 requires Java 8 to run.
+Apache Log4j 2.21.1 requires Java 8 to run.
 The build requires JDK 11 and generates reproducible binaries.
 
 For complete information on Apache Log4j 2, including instructions on how to submit bug reports, patches, get support, or suggestions for improvement, see http://logging.apache.org/log4j/2.x/[the Apache Log4j 2 website].
 
-=== OSGi changes
-
-All the published artifacts are OSGi bundles or fragments.
-
-This release introduces a change in the bundle symbolic names to allow them to function as JPMS module name: all hyphens `-` present in the bundle names of previous releases were replaced by dots `.`.
-
-=== JPMS changes
-
-All the published artifacts have been migrated from automatic modules to named JPMS modules.
-All packages marked as private in the Javadoc are not exported.
-
-The module name of four bridges (`log4j-slf4j-impl`, `log4j-slf4j2-impl`, `log4j-to-jul` and `log4j-to-slf4j`) have been changed to adhere to the same convention as the OSGi bundle names.
-
 
 === Fixed