Merge pull request #103572 from gwynnemonahan/OSDOCS-17459

OSDOCS-17459 [NETOBSERV] Module short descriptions for understanding-network-observability-operator.adoc

Author: ShaunaDiaz

modules/network-observability-architecture.adoc

@@ -6,6 +6,9 @@
 [id="network-observability-architecture_{context}"]
 = Network Observablity Operator architecture
 
+[role="_abstract"]
+Review the Network Observability Operator architecture, detailing how the `FlowCollector` resource manages the `eBPF agent`, which collects and enriches flows, sending the data to Loki for storage or Prometheus for metrics.
+
 The Network Observability Operator provides the `FlowCollector` API, which is instantiated at installation and configured to reconcile the `eBPF agent`, the `flowlogs-pipeline`, and the `netobserv-plugin` components. Only a single `FlowCollector` per cluster is supported.
 
 The `eBPF agent` runs on each cluster node with some privileges to collect network flows. The `flowlogs-pipeline` receives the network flows data and enriches the data with Kubernetes identifiers. If you choose to use Loki, the `flowlogs-pipeline` sends flow logs data to Loki for storing and indexing. The `netobserv-plugin`, which is a dynamic {product-title} web console plugin, queries Loki to fetch network flows data. Cluster-admins can view the data in the web console.

modules/nw-network-observability-operator.adoc

@@ -5,6 +5,9 @@
 [id="nw-network-observability-operator_{context}"]
 = Viewing statuses
 
+[role="_abstract"]
+View the operational status of the Network Observability Operator by using the `oc get` command to check the `FlowCollector` resource status, as well as the status of the `eBPF agent`, `flowlogs-pipeline`, and console plugin Pods.
+
 The Network Observability Operator provides the Flow Collector API. When a Flow Collector resource is created, it deploys pods and services to create and store network flows in the Loki log store, as well as to display dashboards, metrics, and flows in the {product-title} web console.
 
 .Procedure

modules/nw-view-status-configuration-network-observability-operator.adoc

@@ -5,7 +5,8 @@
 [id="nw-status-configuration-network-observability-operator_{context}"]
 = Viewing Network Observability Operator status and configuration
 
-You can inspect the status and view the details of the `FlowCollector` using the `oc describe` command.
+[role="_abstract"]
+Inspect the current status, configuration details, and generated resources of the Network Observability Operator by using the `oc describe flowcollector/cluster` command.
 
 .Procedure