diff --git a/modules/nw-rfhe-introduction.adoc b/modules/nw-rfhe-introduction.adoc
index b2a793dd4f..74fff0c362 100644
--- a/modules/nw-rfhe-introduction.adoc
+++ b/modules/nw-rfhe-introduction.adoc
@@ -6,7 +6,7 @@
 [id="nw-rfhe-introduction_{context}"]
 = How bare-metal events work
 
-The {redfish-operator} enables applications running on bare-metal clusters to respond quickly to Redfish hardware changes and failures such as breaches of temperature thresholds, fan failure, disk loss, power outages, and memory failure. These hardware events are delivered over a reliable low-latency transport channel based on Advanced Message Queuing Protocol (AMQP). The latency of the messaging service is between 10 to 20 milliseconds.
+The {redfish-operator} enables applications running on bare-metal clusters to respond quickly to Redfish hardware changes and failures such as breaches of temperature thresholds, fan failure, disk loss, power outages, and memory failure. These hardware events are delivered using an HTTP transport or AMQP mechanism. The latency of the messaging service is between 10 to 20 milliseconds.
 
 The {redfish-operator} provides a publish-subscribe service for the hardware events. Applications can use a REST API to subscribe to the events. The {redfish-operator} supports hardware that complies with Redfish OpenAPI v1.8 or later.
 
diff --git a/modules/ptp-reference-deployment-and-service-crs.adoc b/modules/ptp-reference-deployment-and-service-crs.adoc
index 5205794ba9..095ace9190 100644
--- a/modules/ptp-reference-deployment-and-service-crs.adoc
+++ b/modules/ptp-reference-deployment-and-service-crs.adoc
@@ -8,13 +8,7 @@
 
 Use the following example `cloud-event-proxy` deployment and subscriber service CRs as a reference when deploying your PTP events consumer application.
 
-[NOTE]
-====
-Use HTTP transport instead of AMQP for PTP and bare-metal events where possible.
-AMQ Interconnect is EOL from 30 June 2024.
-Extended life cycle support (ELS) for AMQ Interconnect ends 30 November 2030.
-For more information see, link:https://access.redhat.com/support/policy/updates/jboss_notes#p_Interconnect[Red Hat AMQ Interconnect support status].
-====
+include::snippets/ptp-amq-interconnect-eol.adoc[]
 
 .Reference cloud-event-proxy deployment with HTTP transport
 [source,yaml]
diff --git a/modules/ztp-creating-hwevents-amqp.adoc b/modules/ztp-creating-hwevents-amqp.adoc
index bdcad43091..34e5fcccb7 100644
--- a/modules/ztp-creating-hwevents-amqp.adoc
+++ b/modules/ztp-creating-hwevents-amqp.adoc
@@ -8,6 +8,8 @@
 
 You can configure bare-metal events that use AMQP transport on managed clusters that you deploy with the {ztp-first} pipeline.
 
+include::snippets/ptp-amq-interconnect-eol.adoc[]
+
 .Prerequisites
 
 * You have installed the OpenShift CLI (`oc`).
diff --git a/snippets/ptp-amq-interconnect-eol.adoc b/snippets/ptp-amq-interconnect-eol.adoc
index 1fb64d2869..d2810115bf 100644
--- a/snippets/ptp-amq-interconnect-eol.adoc
+++ b/snippets/ptp-amq-interconnect-eol.adoc
@@ -1,5 +1,6 @@
 [NOTE]
 ====
+HTTP transport is the default transport for PTP and bare-metal events.
 Use HTTP transport instead of AMQP for PTP and bare-metal events where possible.
 AMQ Interconnect is EOL from 30 June 2024.
 Extended life cycle support (ELS) for AMQ Interconnect ends 29 November 2029.