openshift · bergerhoffer · Oct 6, 2025 · Oct 1, 2025
diff --git a/modules/coo-troubleshooting-ui-plugin-using.adoc b/modules/coo-troubleshooting-ui-plugin-using.adoc
@@ -30,7 +30,7 @@ Other signal types require optional components to be installed:
 image::coo-troubleshooting-panel-link.png[Troubleshooting Panel link]
 +
 Click on the **Troubleshooting Panel** link to display the panel.
-. The panel consists of query details and a topology graph of the query results. The selected alert is converted into a Korrel8r query string and sent to the `korrel8r` service. 
+. The panel consists of query details and a topology graph of the query results. The selected alert is converted into a Korrel8r query string and sent to the `korrel8r` service.
 The results are displayed as a graph network connecting the returned signals and resources. This is a _neighbourhood_ graph, starting at the current resource and including related objects up to 3 steps away from the starting point.
 Clicking on nodes in the graph takes you to the corresponding web console pages for those resouces.
 . You can use the troubleshooting panel to find resources relating to the chosen alert.
@@ -62,11 +62,11 @@ image::coo-troubleshooting-experimental.png[Experimental features]
 [arabic]
 ... **Hide Query** hides the experimental features.
 
-... The query that identifies the starting point for the graph. 
-The query language, part of the link:https://korrel8r.github.io/korrel8r[Korrel8r] correlation engine used to create the graphs, is experimental and may change in future. 
-The query is updated by the **Focus** button to correspond to the resources in the main web console window. 
+... The query that identifies the starting point for the graph.
+The query language, part of the link:https://korrel8r.github.io/korrel8r[Korrel8r] correlation engine used to create the graphs, is experimental and may change in future.
+The query is updated by the **Focus** button to correspond to the resources in the main web console window.
 
-... **Neighbourhood depth** is used to display a smaller or larger neighbourhood. 
+... **Neighbourhood depth** is used to display a smaller or larger neighbourhood.
 +
 [NOTE]
 ====
@@ -80,4 +80,4 @@ Setting a large value in a large cluster might cause the query to fail, if the n
 
 **** `netflow:network` representing any network observability network event.
 
-**** `log:__LOG_TYPE__` representing stored logs, where `__LOG_TYPE__` must be one of `application`, `infrastructure` or `audit`.
+**** `log:__LOG_TYPE__` representing stored logs, where `__LOG_TYPE__` must be one of `application`, `infrastructure` or `audit`.
diff --git a/modules/dr-restoring-cluster-state.adoc b/modules/dr-restoring-cluster-state.adoc
@@ -437,8 +437,8 @@ $ oc get csr
 +
 [source,terminal]
 ----
-NAME        AGE    SIGNERNAME                         REQUESTOR                     CONDITION                                                            
-csr-<uuid>   8m3s   kubernetes.io/kubelet-serving     system:node:<node_name>       Pending  
+NAME        AGE    SIGNERNAME                         REQUESTOR                     CONDITION
+csr-<uuid>   8m3s   kubernetes.io/kubelet-serving     system:node:<node_name>       Pending
 ----
 
 ... Approve all new CSRs by running the following command, replacing `csr-<uuid>` with the name of the CSR:

diff --git a/modules/network-observability-filtering-ebpf-rule.adoc b/modules/network-observability-filtering-ebpf-rule.adoc
@@ -52,7 +52,7 @@ spec:
 ----
 <1> To enable eBPF flow filtering, set `spec.agent.ebpf.flowFilter.enable` to `true`.
 <2> To define the action for the flow filter rule, set the required `action` parameter. Valid values are `Accept` or `Reject`.
-<3> To define the IP address and CIDR mask for the flow filter rule, set the required `cidr` parameter. This parameter supports both IPv4 and IPv6 address formats. To match any IP address, use `0.0.0.0/0` for IPv4 or ``::/0` for IPv6.
+<3> To define the IP address and CIDR mask for the flow filter rule, set the required `cidr` parameter. This parameter supports both IPv4 and IPv6 address formats. To match any IP address, use `0.0.0.0/0` for IPv4 or `::/0` for IPv6.
 <4> To define the sampling rate for matched flows and override the global sampling setting `spec.agent.ebpf.sampling`, set the `sampling` parameter.
 <5> To filter flows by Peer IP CIDR, set the `peerCIDR` parameter.
 
@@ -86,4 +86,4 @@ spec:
 <2> To report packet drops for each network flow, add the `PacketDrop` value to the `spec.agent.ebpf.features` list.
 <3> To enable eBPF flow filtering, set `spec.agent.ebpf.flowFilter.enable` to `true`.
 <4> To define the action for the flow filter rule, set the required `action` parameter. Valid values are `Accept` or `Reject`.
-<5> To filter flows containing drops, set `pktDrops` to `true`.
+<5> To filter flows containing drops, set `pktDrops` to `true`.
diff --git a/modules/persistent-storage-csi-drivers-supported.adoc b/modules/persistent-storage-csi-drivers-supported.adoc
@@ -27,7 +27,7 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 
 The following table describes the CSI drivers that are
 ifndef::openshift-dedicated[]
-installed with {product-title}, 
+installed with {product-title},
 endif::openshift-dedicated[]
 supported by {product-title}, and which CSI features they support, such as volume snapshots and resize.
 
@@ -37,12 +37,12 @@ ifndef::openshift-rosa,openshift-rosa-hcp[]
 If your CSI driver is not listed in the following table, you must follow the installation instructions provided by your CSI storage vendor to use their supported CSI features.
 ====
 
-For a list of third-party-certified CSI drivers, see the _Red Hat ecosystem portal_ under _Additional Resources_.
+For a list of third-party-certified CSI drivers, see the _Red Hat ecosystem portal_ under _Additional resources_.
 
 endif::openshift-rosa,openshift-rosa-hcp[]
 
 ifdef::openshift-rosa,openshift-rosa-hcp,openshift-aro[]
-In addition to the drivers listed in the following table, ROSA functions with CSI drivers from third-party storage vendors. Red Hat does not oversee third-party provisioners or the connected CSI drivers and the vendors fully control source code, deployment, operation, and Kubernetes compatibility. These volume provisioners are considered customer-managed and the respective vendors are responsible for providing support. See the link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.html#rosa-policy-responsibilities_rosa-policy-responsibility-matrix[Shared responsibilities for {product-title}] matrix for more information. 
+In addition to the drivers listed in the following table, ROSA functions with CSI drivers from third-party storage vendors. Red Hat does not oversee third-party provisioners or the connected CSI drivers and the vendors fully control source code, deployment, operation, and Kubernetes compatibility. These volume provisioners are considered customer-managed and the respective vendors are responsible for providing support. See the link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.html#rosa-policy-responsibilities_rosa-policy-responsibility-matrix[Shared responsibilities for {product-title}] matrix for more information.
 endif::openshift-rosa,openshift-rosa-hcp,openshift-aro[]
 
 .Supported CSI drivers and features in {product-title}