[OSDOCS-13264]: Clarifying that you do not need RHACM to use HCP

Author: lahinson

modules/hcp-mce-acm-relationship-intro.adoc

@@ -6,7 +6,12 @@
 [id="hcp-mce-acm-relationship-intro_{context}"]
 = Relationship between {hcp}, {mce-short}, and {rh-rhacm}
 
-You can configure {hcp} by using the {mce}. The multicluster engine is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers.
+You can configure {hcp} by using the {mce}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers.
+
+[NOTE]
+====
+The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}.
+====
 
 The {mce-short} is the cluster lifecycle Operator that provides cluster management capabilities for {product-title} and {rh-rhacm} hub clusters. The {mce-short} enhances cluster fleet management and supports {product-title} cluster lifecycle management across clouds and data centers.
 

modules/hosted-control-planes-overview.adoc

@@ -20,6 +20,11 @@
 
 The {hcp} feature is enabled by default.
 
+[NOTE]
+====
+The {mce-short} is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. However, you do not need {rh-rhacm} in order to use {hcp}.
+====
+
 [id="hosted-control-planes-architecture_{context}"]
 == Architecture of {hcp}