apply Keith's review comments

Signed-off-by: Atif Ali <atali@redhat.com>

Author: aali309

docs/README.md

@@ -2,7 +2,7 @@
 
 The GitOps Console plugin extends the OpenShift Container Platform web console by adding GitOps resources. The plugin is available as part of the Red Hat OpenShift GitOps Operator and provides a console UI for managing Argo CD and Argo Rollouts custom resources.
 
-After you install the Red Hat OpenShift GitOps Operator, the OpenShift web console displays a **GitOps** navigation tab in the **Administrator** perspective. The plugin is enabled by default. The GitOps navigation tab replaces the previous **Environments** tab and related pages in the **Developer** perspective.
+After you install the Red Hat OpenShift GitOps Operator, the OpenShift web console displays a **GitOps** navigation tab in the **Administrator** or **Core platform** perspective. The plugin is enabled by default. The GitOps navigation tab replaces the previous **Environments** tab and related pages in the **Developer** perspective.
 
 The GitOps navigation tab provides access to the following Argo CD and Argo Rollouts resources:
 
@@ -14,7 +14,7 @@ The GitOps navigation tab provides access to the following Argo CD and Argo Roll
 
 ## Prerequisites
 
-* You have access to OpenShift Container Platform 4.19 or later.
+* You have access to OpenShift Container Platform 4.18 or later.
 * You have installed the Red Hat OpenShift GitOps Operator.
 
 ## GitOps resources in the web console

docs/applications.md

@@ -14,7 +14,7 @@ The GitOps Console plugin provides list and details pages for Argo CD Applicatio
 
 ## Applications list page
 
-1. In the **Administrator** perspective, navigate to **GitOps** → **Applications**.
+1. In the **Administrator** or **Core platform** perspective, navigate to **GitOps** → **Applications**.
 
 2. Optional: Use the **Project** dropdown to limit the list to one project (namespace), or choose all projects to view Applications across namespaces.
 

docs/applicationsets.md

@@ -10,7 +10,7 @@ The GitOps Console plugin shows list and details pages for Argo CD ApplicationSe
 
 ## List page
 
-1. In the **Administrator** perspective, navigate to **GitOps** → **ApplicationSets**.
+1. In the **Administrator** or **Core platform** perspective, navigate to **GitOps** → **ApplicationSets**.
 
 2. Optional: Use the **Project** dropdown to limit the list to one project (namespace), or choose all projects.
 

docs/appprojects-rbac.md

@@ -10,7 +10,7 @@ The GitOps Console plugin provides list and details pages for Argo CD AppProject
 
 ## List page
 
-1. In the **Administrator** perspective, navigate to **GitOps** → **AppProjects**.
+1. In the **Administrator** or **Core platform** perspective, navigate to **GitOps** → **AppProjects**.
 
 2. Optional: Use the **Project** dropdown to limit the list to one project (namespace), or choose all projects.
 

docs/getting-started.md

@@ -6,7 +6,7 @@ Use the OpenShift web console to install GitOps, enable the Console plugin, and
 
 ## Prerequisites
 
-* You have access to an OpenShift Container Platform 4.19 or later cluster.
+* You have access to an OpenShift Container Platform 4.18 or later cluster.
 * You can log in to the web console with cluster-admin permission to install the Operator and enable the plugin.
 
 ## Install the OpenShift GitOps Operator
@@ -29,7 +29,7 @@ If **GitOps** is already in the navigation, skip this step. Otherwise follow [En
 
 ## Open the GitOps pages
 
-1. In the **Administrator** perspective, click **GitOps**.
+1. In the **Administrator** or **Core platform** perspective, click **GitOps**.
 
 2. Verify that you can open the following pages:
 

docs/image-updaters.md

@@ -13,7 +13,7 @@ The **ImageUpdaters** page is available when the ImageUpdater custom resource de
 
 ## List page
 
-1. In the **Administrator** perspective, navigate to **GitOps** → **ImageUpdaters**.
+1. In the **Administrator** or **Core platform** perspective, navigate to **GitOps** → **ImageUpdaters**.
 
 2. Optional: Use the **Project** dropdown to limit the list to one project (namespace), or choose all projects.
 

docs/rollouts.md

@@ -1,19 +1,18 @@
 # Rollouts in the GitOps Console
 
-The GitOps Console plugin provides list and details pages for Argo Rollouts in the OpenShift web console. You can search and filter Rollouts, create them from a YAML template, scale replicas, inspect revisions and pods, and open Rollouts in the Developer Topology view.
+The GitOps Console plugin provides list and details pages for Argo Rollouts in the OpenShift web console. You can search and filter Rollouts, create them from a YAML template, scale replicas, inspect revisions and pods, and open Rollouts in the Topology view.
 
-The **Rollouts** page is available when the Rollout custom resource definition is installed on the cluster.
+The **Rollouts** page is available after you install the Red Hat OpenShift GitOps Operator.
 
 ## Prerequisites
 
 * You have access to the OpenShift web console.
 * The GitOps Console plugin is enabled. See [Enable the GitOps Console plugin](admin-enable-plugin.md).
-* The Rollout CRD is installed on the cluster.
 * You can list Rollouts in the selected namespace (or across namespaces, depending on your permissions).
 
 ## List page
 
-1. In the **Administrator** perspective, navigate to **GitOps** → **Rollouts**.
+1. In the **Administrator** or **Core platform** perspective, navigate to **GitOps** → **Rollouts**.
 
 2. Optional: Use the **Project** dropdown to limit the list to one project (namespace), or choose all projects.
 
@@ -26,7 +25,7 @@ The Rollouts list page includes:
 * **Table columns**: **Name**, **Namespace**, **Status**, **Pods**, **Labels**, **Selector**, **Last Updated**, and row actions
 * **Pagination**: Browse results in pages of 10, 20, 50, or 100 items (default 50). Search and filters change which rows are included. See [Filter, search, and paginate resources](filter-resources.md).
 
-When the list has results, a **Topology view** control opens the Developer Topology graph for the current namespace (or all namespaces).
+When the list has results, a **Topology view** control opens the Topology graph for the current namespace (or all namespaces).
 
 > **NOTE**
 >
@@ -43,10 +42,16 @@ From the row kebab, you can:
 
 ## Topology integration
 
-In the **Developer** perspective, the OpenShift Console **Topology** view can show Rollout workloads when:
+Rollout topology requires OpenShift Container Platform **4.19** or later (not available in the release-4.18 plugin).
 
-* The Rollout CRD is installed
-* The cluster is OpenShift Container Platform **4.19** or later
+| Perspective | Navigation |
+| --- | --- |
+| **Core platform** | **Workloads** → **Topology** |
+| **Developer** | **Topology** |
+
+The cluster-wide perspective may be labeled **Administrator** or **Core platform** depending on your OpenShift version.
+
+See [Rollouts in Topology](topology.md#rollouts-in-topology) for the full Topology page layout.
 
 When those conditions are met:
 
@@ -58,7 +63,7 @@ Use the **Topology view** control on the Rollouts list, Details tab, or Pods tab
 
 ![Topology view control on the Rollouts list](assets/pics/rollouts-topology-view-control.png)
 
-From Details or Pods, the Rollout is selected in the graph. For more detail, see [Rollouts in Developer Topology](topology.md#rollouts-in-developer-topology).
+From Details or Pods, the Rollout is selected in the graph. For more detail, see [Rollouts in Topology](topology.md#rollouts-in-topology).
 
 ## Rollout details page
 
@@ -78,7 +83,7 @@ Section title: **Rollout details**.
 
 **Summary (left)**
 
-* **Name**, with a **Topology view** control that opens the Developer Topology graph for this Rollout
+* **Name**, with a **Topology view** control that opens the Topology graph for this Rollout
 * **Namespace**
 * **Labels**, with **Edit**
 * **Annotations**
@@ -142,5 +147,5 @@ The **Events** tab shows Kubernetes events for the Rollout object, using the sta
 ## Related information
 
 * [Filter, search, and paginate resources](filter-resources.md)
-* [Rollouts in Developer Topology](topology.md#rollouts-in-developer-topology)
+* [Rollouts in Topology](topology.md#rollouts-in-topology)
 * [Troubleshooting](troubleshooting.md)

docs/topology.md

@@ -3,7 +3,7 @@
 The GitOps Console plugin provides two kinds of graphical experience:
 
 * **Graph view** — In-plugin graphs on Application **Resources** and ApplicationSet **Applications** tabs
-* **Topology** — The OpenShift **Developer** perspective Topology page for Rollout workloads, opened with the **Topology view** control
+* **Topology** — Rollout workloads on the console **Topology** page (path depends on OpenShift version; see [Rollouts in Topology](#rollouts-in-topology))
 
 ## Application resource graph
 
@@ -116,14 +116,20 @@ The `template.metadata.labels` values must match the `rollingSync.steps` selecto
 
 This step-based flow is separate from **sync waves** on an Application's managed resources (the **Sync Wave** column on an Application **Resources** tab). Progressive sync controls the order in which Applications sync; sync waves control the order of resources within a single Application sync.
 
-## Rollouts in Developer Topology
+## Rollouts in Topology
 
-In the **Developer** perspective, open **Topology** to see Rollout workloads in **graph** or **list** view.
+Rollout topology integration requires OpenShift Container Platform **4.19** or later (not available in the release-4.18 plugin).
 
-Rollout topology integration requires:
+Open Topology using the path that matches your console layout:
 
-* The Rollout CRD installed on the cluster
-* OpenShift Container Platform **4.19** or later
+| Perspective | Navigation |
+| --- | --- |
+| **Core platform** | **Workloads** → **Topology** |
+| **Developer** | **Topology** |
+
+The cluster-wide perspective may be labeled **Administrator** or **Core platform** depending on your OpenShift version.
+
+From GitOps **Rollouts** pages, the **Topology view** control opens the same graph without using the navigation paths above.
 
 When available, the Topology page includes the following, from top to bottom:
 

docs/troubleshooting.md

@@ -3,18 +3,18 @@
 ## Prerequisites
 
 * You have access to the OpenShift web console.
-* You have access to an OpenShift Container Platform 4.19 or later cluster.
+* You have access to an OpenShift Container Platform 4.18 or later cluster.
 * The GitOps Console plugin is enabled. See [Enable the GitOps Console plugin](admin-enable-plugin.md).
 
 ## Common issues
 
 **GitOps is missing from the navigation**
 
-The plugin is disabled, the cluster is older than OpenShift 4.19, or the plugin pods are not running. See [Enable the GitOps Console plugin](admin-enable-plugin.md). Refresh the browser after you enable the plugin.
+The plugin is disabled, the cluster is older than OpenShift 4.18, or the plugin pods are not running. See [Enable the GitOps Console plugin](admin-enable-plugin.md). Refresh the browser after you enable the plugin.
 
 **ImageUpdaters or Rollouts are missing**
 
-Those list pages appear only when the matching CRDs are installed. Rollouts in the Developer **Topology** view also require OpenShift 4.19 or later. See [Rollouts in Developer Topology](topology.md#rollouts-in-developer-topology).
+Those list pages appear when the Red Hat OpenShift GitOps Operator is installed (it installs the Rollout and ImageUpdater CRDs). Rollouts in the **Topology** view require OpenShift 4.19 or later and are not available in the release-4.18 plugin. See [Rollouts in Topology](topology.md#rollouts-in-topology).
 
 **Empty lists or disabled actions**