set operator managementState to Unmanaged for all manually steps

Author: mburke5678

modules/efk-logging-curator-yaml.adoc

@@ -7,6 +7,10 @@
 
 You can configure Elasticsearch Curator to delete indices.
 
+.Prerequisite
+
+Set cluster logging to the unmanaged state. In managed state, the Cluster Logging Operator reverts changes made to the `logging-curator` configuration map.
+
 .Procedure
 
 To delete indices:

modules/efk-logging-fluentd-collector.adoc

@@ -27,8 +27,10 @@ endif::[]
 
 .Prerequisite
 
-If needed, get the name of the Cluster Logging Custom Resource from the `openshift-logging` project:
+* Set cluster logging to the unmanaged state. In managed state, the Cluster Logging Operator reverts changes made to the `logging-curator` configuration map.
 
+* If needed, get the name of the Cluster Logging Custom Resource from the `openshift-logging` project:
++
 ----
 $ oc get ClusterLogging
 NAME       AGE

modules/efk-logging-kibana-exposing.adoc

@@ -16,7 +16,9 @@ You cannot modify the default Kibana route.
 
 .Prerequisites
 
-Cluster logging and Elasticsearch must be installed.
+* Cluster logging and Elasticsearch must be installed.
+
+* Set cluster logging to the unmanaged state. In managed state, the Cluster Logging Operator reverts changes made to the `logging-curator` configuration map.
 
 .Procedure 
 

modules/efk-logging-kibana-scaling.adoc

@@ -9,14 +9,16 @@ You can scale the Kibana deployment for redundancy.
 
 .Prerequisite
 
-If needed, get the name of the Cluster Logging Custom Resource from the `openshift-logging` project:
+* If needed, get the name of the Cluster Logging Custom Resource from the `openshift-logging` project:
 
 ----
 $ oc get ClusterLogging
 NAME       AGE
 instance   112m
 ----
 
+* Set cluster logging to the unmanaged state. In managed state, the Cluster Logging Operator reverts changes made to the `logging-curator` configuration map.
+
 .Procedure
 
 Edit or create the Cluster Logging Custom Resource (CR) from the `openshift-logging` project: