diff --git a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc
index bdae3db3..fcf223c1 100644
--- a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc
+++ b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc
@@ -14,11 +14,6 @@ The `ServiceTelemetry` object comprises the following primary configuration para
 
 You can configure each of these configuration parameters to provide different features in an {ProjectShort} deployment.
 
-[IMPORTANT]
-====
-Support for `servicetelemetry.infra.watch/v1alpha1` was removed from {ProjectShort} 1.3.
-====
-
 [id="backends_{context}"]
 [discrete]
 == The backends parameter
@@ -129,7 +124,7 @@ Use the `pvcStorageRequest` parameter to define the minimum required volume size
 
 .Procedure
 
-* List the available storage classes:
+. List the available storage classes:
 +
 [source,bash,options="nowrap"]
 ----
@@ -140,7 +135,7 @@ standard (default)   kubernetes.io/cinder       Delete          WaitForFirstCons
 standard-csi         cinder.csi.openstack.org   Delete          WaitForFirstConsumer   true                   20h
 ----
 
-* Configure the `ServiceTelemetry` object:
+. Configure the `ServiceTelemetry` object:
 +
 [source,yaml]
 ----
diff --git a/doc-Service-Telemetry-Framework/modules/proc_checking-for-an-expired-amq-interconnect-ca-certificate.adoc b/doc-Service-Telemetry-Framework/modules/proc_checking-for-an-expired-amq-interconnect-ca-certificate.adoc
index c11bd787..f8e9c1ed 100644
--- a/doc-Service-Telemetry-Framework/modules/proc_checking-for-an-expired-amq-interconnect-ca-certificate.adoc
+++ b/doc-Service-Telemetry-Framework/modules/proc_checking-for-an-expired-amq-interconnect-ca-certificate.adoc
@@ -2,7 +2,7 @@
 = Checking for an expired {MessageBus} CA certificate
 
 [role="_abstract"]
-When the CA certificate expires the {MessageBus} connections will remain up, but will be unable to reconnect if they are interrupted. Eventually you will find that some or all of the connections from your {Openstack} ({OpenStackShort}) Routers have failed, showing errors on both sides, and the expiry (or "Not After") field in your CA certificate will be in the past.
+When the CA certificate expires, the {MessageBus} connections remain up, but cannot reconnect if they are interrupted. Eventually, some or all of the connections from your {Openstack} ({OpenStackShort}) dispatch routers fail, showing errors on both sides, and the expiry or *Not After* field in your CA certificate is in the past.
 
 .Procedure
 
@@ -14,7 +14,7 @@ When the CA certificate expires the {MessageBus} connections will remain up, but
 $ oc project service-telemetry
 ----
 
-. Check that some or all Router connections have failed:
+. Verify that some or all dispatch router connections have failed:
 +
 [source,bash,options="nowrap"]
 ----
@@ -32,7 +32,8 @@ $ oc logs -l application=default-interconnect | tail
 ----
 
 . Log into your {OpenStackShort} undercloud.
-. Check for this error in the {OpenStackShort}-hosted {MessageBus} logs of a node where the connection has failed:
+
+. Check for this error in the {OpenStackShort}-hosted {MessageBus} logs of a node with a failed connection:
 +
 [source,bash,options="nowrap"]
 ----
diff --git a/doc-Service-Telemetry-Framework/modules/proc_updating-the-amq-interconnect-ca-certificate.adoc b/doc-Service-Telemetry-Framework/modules/proc_updating-the-amq-interconnect-ca-certificate.adoc
index 2ee8529a..22cb96c5 100644
--- a/doc-Service-Telemetry-Framework/modules/proc_updating-the-amq-interconnect-ca-certificate.adoc
+++ b/doc-Service-Telemetry-Framework/modules/proc_updating-the-amq-interconnect-ca-certificate.adoc
@@ -2,7 +2,7 @@
 = Updating the {MessageBus} CA certificate
 
 [role="_abstract"]
-To update the {MessageBus} certificate, you will need to export it from {OpenShift} and copy it to your {OpenStack} ({OpenStackShort}) nodes.
+To update the {MessageBus} certificate, you must export it from {OpenShift} and copy it to your {OpenStack} ({OpenStackShort}) nodes.
 
 .Procedure
 
@@ -21,13 +21,14 @@ $ oc project service-telemetry
 $ oc get secret/default-interconnect-selfsigned -o jsonpath='{.data.ca\.crt}' | base64 -d > STFCA.pem
 ----
 
-. Copy STFCA.pem to your {OpenStackShort} undercloud.
+. Copy `STFCA.pem` to your {OpenStackShort} undercloud.
 . Log into your {OpenStackShort} undercloud.
-. Edit the stf-connectors.yaml file to contain the new caCertFileContent (For more information, see xref:configuring-the-stf-connection-for-the-overcloud_assembly-completing-the-stf-configuration[])
+. Edit the `stf-connectors.yaml` file to contain the new caCertFileContent. For more information, see xref:configuring-the-stf-connection-for-the-overcloud_assembly-completing-the-stf-configuration[].
++
 [NOTE]
 You do not need to perform an overcloud deploy after performing the steps below. We edit the stf-connectors.yaml file only to make sure that future deployments will not overwrite the new CA certificate.
 
-. Copy the STFCA.pem file to each {OpenStackShort} overcloud node:
+. Copy the `STFCA.pem` file to each {OpenStackShort} overcloud node:
 +
 [source,bash,options="nowrap"]
 ----