diff --git a/jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations.adoc b/jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations.adoc
index f71bdce91b1..43e070094a2 100644
--- a/jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations.adoc
+++ b/jetty-documentation/src/main/asciidoc/administration/annotations/using-annotations.adoc
@@ -119,6 +119,13 @@ By default Jetty will call them in the following order:
 
 As is the case with annotation scanning, the link:#using-extra-classpath-method[extraClasspath] is fully considered for `ServletContainerInitializer` callbacks. `ServletContainerInitializer` derived from a classes directory on the `extraClasspath` and jars from an `extraClasspath` for the webapp are called in step 2 and 3, respectively.
 
+____
+[NOTE]
+As of Jetty-9.4.4, unless the `web.xml` is version 3.0 or greater, only `ServletContainerInitializers` that are on the container classpath will be discovered.
+Users wishing to use `ServletContainerInitializers` from within the webapp with older versions of `web.xml` must either upgrade their `web.xml` version, or call `WebAppContext.setConfigurationDiscovered(true)` either programmatically or in xml.
+Upgrading the `web.xml` version is preferable.
+____
+
 ===== Controlling the order of ServletContainerInitializer invocation
 
 If you need `ServletContainerInitializer` classes called in a specific order that is different from that outlined above, you can use the link:#context_attributes[context attribute] `org.eclipse.jetty.containerInitializerOrder`.
diff --git a/jetty-documentation/src/main/asciidoc/reference/upgrading/upgrading-9.3-to-9.4.adoc b/jetty-documentation/src/main/asciidoc/reference/upgrading/upgrading-9.3-to-9.4.adoc
index 437998997fe..b06571a38f8 100644
--- a/jetty-documentation/src/main/asciidoc/reference/upgrading/upgrading-9.3-to-9.4.adoc
+++ b/jetty-documentation/src/main/asciidoc/reference/upgrading/upgrading-9.3-to-9.4.adoc
@@ -254,8 +254,11 @@ Enable the `session-store-gcloud` and `session-store-cache` modules.
 
 *Compatibility*
 
-Sessions stored into Memcached by earlier versions of jetty are incompatible with Jetty 9.4. Previous versions of jetty stored `org.eclipse.jetty.gcloud.memcached.session.SerializableSessionData` whereas Jetty 9.4 stores `org.eclipse.jetty.server.session.SessionData`.
+Sessions stored into Memcached by earlier versions of jetty are incompatible with Jetty 9.4.
+Previous versions of jetty stored `org.eclipse.jetty.gcloud.memcached.session.SerializableSessionData` whereas Jetty 9.4 stores `org.eclipse.jetty.server.session.SessionData`.
 
 ==== ServletContainerInitializers
 
-As of jetty-9.4.4, unless the web.xml is version 3.0 or greater, only ServletContainerInitializers that are on the container classpath will be discovered. Users wishing to use ServletContainerInitializers from within the webapp with older versions of web.xml must either upgrade their web.xml version, or call WebAppContext.setConfigurationDiscovered(true) either programmatically or in xml. Upgrading the web.xml version is preferable. 
+As of Jetty-9.4.4, unless the `web.xml` is version 3.0 or greater, only `ServletContainerInitializers` that are on the container classpath will be discovered.
+Users wishing to use `ServletContainerInitializers` from within the webapp with older versions of `web.xml` must either upgrade their `web.xml` version, or call `WebAppContext.setConfigurationDiscovered(true)` either programmatically or in xml.
+Upgrading the `web.xml` version is preferable.