diff --git a/modules/ossm-upgrade-22-23-changes.adoc b/modules/ossm-upgrade-22-23-changes.adoc
new file mode 100644
index 000000000000..4f0fc056910f
--- /dev/null
+++ b/modules/ossm-upgrade-22-23-changes.adoc
@@ -0,0 +1,10 @@
+// Module included in the following assemblies:
+// * service_mesh/v2x/upgrading-ossm.adoc
+
+:_content-type: CONCEPT
+[id="ossm-upgrade-22-23-changes_{context}"]
+= Upgrade changes from version 2.2 to version 2.3
+
+Upgrading the {SMProductShortName} control plane from version 2.2 to 2.3 introduces the following behavioral changes:
+
+* This release requires use of the `WasmPlugin` API. Support for the `ServiceMeshExtension` API, which was deprecated in 2.2, has now been removed. If you attempt to upgrade while using the `ServiceMeshExtension` API, then the upgrade fails.
diff --git a/service_mesh/v2x/upgrading-ossm.adoc b/service_mesh/v2x/upgrading-ossm.adoc
index aa2be2370f27..c37e2a340f66 100644
--- a/service_mesh/v2x/upgrading-ossm.adoc
+++ b/service_mesh/v2x/upgrading-ossm.adoc
@@ -34,10 +34,11 @@ When you upgrade the service mesh control plane, all Operator managed resources,
 
 Although you can deploy multiple versions of the control plane in the same cluster, {SMProductName} does not support canary upgrades of the service mesh. That is, you can have different SCMP resources with different values for `spec.version`, but they cannot be managing the same mesh.
 
-include::modules/ossm-upgrade-21-22-changes.adoc[leveloffset=+2]
-
 For more information about migrating your extensions, refer to xref:../../service_mesh/v2x/ossm-extensions.adoc#ossm-extensions-migration-overview_ossm-extensions[Migrating from ServiceMeshExtension to WasmPlugin resources].
 
+include::modules/ossm-upgrade-22-23-changes.adoc[leveloffset=+2]
+
+include::modules/ossm-upgrade-21-22-changes.adoc[leveloffset=+2]
 
 include::modules/ossm-upgrade-20-21-changes.adoc[leveloffset=+2]