OBSDOCS-2437: Implement Upgrading guide feedback

Author: theashiot

modules/deleting-red-hat-log-visualization.adoc renamed to modules/deleting-the-logging-view-plugin.adoc

@@ -2,10 +2,10 @@
 :_template-generated: 2025-06-03
 :_mod-docs-content-type: PROCEDURE
 
-[id="deleting-red-hat-log-visualization_{context}"]
-= Deleting Red{nbsp}Hat log visualization
+[id="deleting-the-logging-view-plugin_{context}"]
+= Deleting the logging view plugin
 
-When updating from Logging 5 to Logging 6, delete Red{nbsp}Hat Log Visualization before installing the UIPlugin.
+When updating from Logging 5 to Logging 6, delete the logging view plugin before installing the UIPlugin.
 
 .Prerequisites
 * You have administrator permissions.

modules/migrating-storage-from-elasticsearch-to-lokistack.adoc

@@ -13,7 +13,7 @@ You can migrate your existing Red{nbsp}Hat managed Elasticsearch to LokiStack.
 
 .Procedure
 
-. Temporarily set the state of the `ClusterLogging` resource as `Unmanaged`
+. Temporarily set the state of the `ClusterLogging` resource as `Unmanaged`.
 +
 [source,terminal]
 ----
@@ -29,9 +29,9 @@ The following command ensures that the `ClusterLogging` resource no longer owns
 $ oc -n openshift-logging patch elasticsearch/elasticsearch -p '{"metadata":{"ownerReferences": []}}' --type=merge
 ----
 
-. Remove `ClusterLogging` `ownerReferences` from the `Kibana` resource
+. Remove `ClusterLogging` `ownerReferences` from the `Kibana` resource.
 +
-The following command ensures that *ClusterLogging* no longer owns the *Kibana* resource. Updates to the *ClusterLogging* resource's `visualization` field will no longer affect the *Kibana* resource.
+The following command ensures that `ClusterLogging` no longer owns the `Kibana` resource. Updates to the `ClusterLogging` resource's `visualization` field will no longer affect the `Kibana` resource.
 +
 [source,terminal]
 ----

upgrading/docinfo.xml

@@ -1,9 +1,9 @@
 <title>Upgrading logging</title>
 <productname>{product-title}</productname>
 <productnumber>{product-version}</productnumber>
-<subtitle>Upgrading older versions and upgrade paths</subtitle>
+<subtitle>Upgrading logging 5 to 6</subtitle>
 <abstract>
-    <para>This document includes information about how to upgrade older versiosn of logging, and what upgrade paths are supported.</para>
+    <para>This document includes information about how to upgrade logging 5 to logging 6.</para>
 </abstract>
 <authorgroup>
     <orgname>Red Hat OpenShift Documentation Team</orgname>

upgrading/upgrading-to-logging-60.adoc

@@ -14,20 +14,20 @@ Logging 6 is a significant upgrade from earlier releases, achieving several long
 
 Introduction of distinct Operators to manage logging components::
 
-* {clo} manages both collections and forwarding.
+* {clo} manages both collection and forwarding.
 * {loki-op} manages storage.
 * {coo-first} manages visualization.
 
 Removal of support for managed log storage and visualization based on Elastic products::
 
-* Elasticsearch has been replaced with Loki.
-* Kibana has been replaced with the UIplugin provided by {coo-short}.
+* Elasticsearch is replaced with Loki.
+* Kibana is replaced with the UIplugin provided by {coo-short}.
 
 Removal of the Fluentd log collector implementation::
 Vector is now the supported collection service.
 
 API change for log collection and forwarding::
-* The API log collection has been changed from `logging.openshift.io` to `observability.openshift.io`.
+* The API for log collection is changed from `logging.openshift.io` to `observability.openshift.io`.
 * `ClusterLogForwarder` and `ClusterLogging` have been combined under the `ClusterLogForwarder` resource in the new API.
 
 [id="steps-for-upgrading-logging-5-to-6_{context}"]
@@ -56,9 +56,10 @@ include::modules/migrating-storage-from-elasticsearch-to-lokistack.adoc[leveloff
 [id="migrating-logging-visualization_{context}"]
 == Migrating logging visualization
 
-The OpenShift console UI plugin for log visualization has been moved to the {coo-full} from the Cluster Logging Operator.
+The OpenShift console UI plugin for log visualization is moved to the {coo-full} from the Cluster Logging Operator.
+
+include::modules/deleting-the-logging-view-plugin.adoc[leveloffset=+2]
 
-include::modules/deleting-red-hat-log-visualization.adoc[leveloffset=+2]
 include::modules/installing-the-logging-ui-plug-in-gui.adoc[leveloffset=+2]
 
 [id="log-storage_{context}"]