edit typo

Author: mburke5678

modules/efk-logging-deploy-subscription.adoc

@@ -133,11 +133,11 @@ spec:
 ----
 <1> The name of the Cluster Logging Custom Resource.
 <2> The cluster logging management state. In most cases, if you change the default cluster logging defaults, you will need to set this to `Unmanaged`. 
-However, an unmanaged deployment does not receive updates until the cluster logging is placed back into a managed state. See *Changing cluster logging management state*.
-<3> Settings for configuring Elasticsearch. Using the CR, you can configure shard replication policy and persistent storage. See *Configuring Elasticsearch*.
-<4> Settings for configuring Kibana. Using the CR, you can scale Kibana for redundancy and configure the CPU and memory for your Kibana nodes. See *Configuring Kibana*.
-<5> Settings for configuring Curator. Using the CR, you can set the Curator schedule. See *Configuring Curator*.
-<6> Settings for configuring Fluentd. Using the CR, you can configure Fluentd CPU and memory limits. See *Configuring Fluentd*.
+However, an unmanaged deployment does not receive updates until the cluster logging is placed back into a managed state. For more information, see *Changing cluster logging management state*.
+<3> Settings for configuring Elasticsearch. Using the CR, you can configure shard replication policy and persistent storage. For more information, see *Configuring Elasticsearch*.
+<4> Settings for configuring Kibana. Using the CR, you can scale Kibana for redundancy and configure the CPU and memory for your Kibana nodes. For more information, see *Configuring Kibana*.
+<5> Settings for configuring Curator. Using the CR, you can set the Curator schedule. For more information, see *Configuring Curator*.
+<6> Settings for configuring Fluentd. Using the CR, you can configure Fluentd CPU and memory limits. For more information, see *Configuring Fluentd*.
 +
 [NOTE]
 ====