diff --git a/installing/installing-logging.adoc b/installing/installing-logging.adoc
index 73524a4837b3..558959c07b73 100644
--- a/installing/installing-logging.adoc
+++ b/installing/installing-logging.adoc
@@ -19,7 +19,8 @@ You can use either the {ocp-product-title} web console or the {ocp-product-title
 
 [IMPORTANT]
 ====
-You must configure the {clo} after the {loki-op}.
+* You must configure the {clo} after the {loki-op}.
+* You must install the {clo} and the {loki-op} with the same major and minor version.
 ====
 
 
diff --git a/upgrading/upgrading-to-logging-60.adoc b/upgrading/upgrading-to-logging-60.adoc
index 0afefd70b8ef..8ceee605221b 100644
--- a/upgrading/upgrading-to-logging-60.adoc
+++ b/upgrading/upgrading-to-logging-60.adoc
@@ -69,7 +69,8 @@ The only managed log storage solution available in this release is a LokiStack,
 
 [IMPORTANT]
 ====
-To continue using an existing Red{nbsp}Hat-managed Elasticsearch or Kibana deployment provided by the `elasticsearch-operator`, remove the owner references from the `Elasticsearch` resource named `elasticsearch`, and  the `Kibana` resource named `kibana` in the `openshift-logging` namespace before removing the `ClusterLogging` resource named `instance` in the same namespace.
+* You must install the {clo} and the {loki-op} with the same major and minor version.
+* To continue using an existing Red{nbsp}Hat-managed Elasticsearch or Kibana deployment provided by the `elasticsearch-operator`, remove the owner references from the `Elasticsearch` resource named `elasticsearch`, and  the `Kibana` resource named `kibana` in the `openshift-logging` namespace before removing the `ClusterLogging` resource named `instance` in the same namespace.
 ====
 
 To upgrade Loki storage, follow these steps: