diff --git a/images/openshift-telco-core-rds-metallb-service-separation.png b/images/openshift-telco-core-rds-metallb-service-separation.png
index cc7aa2bc38a8..34f9d78b928a 100644
Binary files a/images/openshift-telco-core-rds-metallb-service-separation.png and b/images/openshift-telco-core-rds-metallb-service-separation.png differ
diff --git a/modules/telco-core-red-hat-advanced-cluster-management.adoc b/modules/telco-core-red-hat-advanced-cluster-management.adoc
index e304a1a5de54..31126047bc62 100644
--- a/modules/telco-core-red-hat-advanced-cluster-management.adoc
+++ b/modules/telco-core-red-hat-advanced-cluster-management.adoc
@@ -7,7 +7,7 @@
 = Red Hat Advanced Cluster Management
 
 New in this release::
-* No reference design updates in this release
+* Image-based installation for {sno} clusters is the recommended install methodology.
 
 Description::
 +
diff --git a/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc b/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
index 7b5e571f1686..d378fc1aea02 100644
--- a/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
+++ b/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
@@ -65,7 +65,7 @@ $ query=avg_over_time(pod:container_cpu_usage:sum{namespace="openshift-kube-apis
 ----
 ====
 . Application logs are not collected by the platform log collector
-. Aggregate traffic on the primary CNI is less than 8 MBps
+. Aggregate traffic on the primary CNI is less than 8 Mbps
 
 Hub cluster management characteristics::
 +
diff --git a/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc b/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc
index 0c2f438e0aaf..c568002395ee 100644
--- a/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc
+++ b/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc
@@ -20,6 +20,10 @@ You manage cluster configuration and upgrades declaratively by applying `Policy`
 * Zero touch provisioning (ZTP) of clusters using the MCE component in {rh-rhacm}.
 * Configuration, upgrades, and cluster status through the {rh-rhacm} policy controller.
 * During managed cluster installation, {rh-rhacm} can apply labels to individual nodes as configured through the `ClusterInstance` CR.
+
+The recommended method for {sno} cluster installation is the image-based installer method available in MCE using the `ClusterInstance` CR for cluster definition.
+
+The recommended method for {sno} cluster upgrade is the image-based upgrade method.
 --
 
 Limits and requirements::