Revise

Author: jab-rh

modules/nw-bgp-about.adoc

@@ -3,10 +3,10 @@
 // * networking/bgp_routing/about-bgp-routing.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="nw-bgp-about_{context}"]
+[id="nw-bgp-about_routing_{context}"]
 = About Border Gateway Protocol (BGP) routing
 
-{product-title} supports BGP routing through FRRouting (FRR), a free, open source internet routing protocol suite for Linux and UNIX platforms. FRR-K8s is a Kubernetes based daemon set that exposes a subset of the FRR API in a Kubernetes-compliant manner. As a cluster administrator, you can use the FRRConfiguration custom resource (CR) to access FRR services.
+{product-title} supports BGP routing through FRRouting (FRR), a free, open source internet routing protocol suite for Linux, UNIX, and similar operating systems. FRR-K8s is a Kubernetes-based daemon set that exposes a subset of the FRR API in a Kubernetes-compliant manner. As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to access FRR services.
 
 [id="supported-platforms_{context}"]
 == Supported platforms
@@ -16,17 +16,14 @@ BGP routing is supported on the following infrastructure types:
 - Bare metal
 - {vmw-full} on-premise
 
-[id="prerequisites_{context}"]
-== Prerequisites
-
-Use of BGP routing requires that you have properly configured BGP for your network provider. Outages or misconfigurations of your network provider might cause disruptions to your cluster network.
+BGP routing requires that you have properly configured BGP for your network provider. Outages or misconfigurations of your network provider might cause disruptions to your cluster network.
 
 [id="considerations-for-use-with-the-metallb-operator_{context}"]
 == Considerations for use with the MetalLB Operator
 
 The MetalLB Operator is installed as an add-on to the cluster. Deployment of the MetalLB Operator automatically enables FRR-K8s as an additional routing capability provider and uses the FRR-K8s daemon installed by this feature.
 
-Before upgrading to 4.18, any existing FRRConfiguration in the `metallb-system` namespace not managed by the MetalLB operator (added by a cluster administrator or any other component) needs to be copied to the `openshift-frr-k8s` namespace manually, creating the namespace if necessary.
+Before upgrading to 4.18, any existing `FRRConfiguration` in the `metallb-system` namespace not managed by the MetalLB operator (added by a cluster administrator or any other component) needs to be copied to the `openshift-frr-k8s` namespace manually, creating the namespace if necessary.
 
 [IMPORTANT]
 ====
@@ -38,7 +35,7 @@ If you are using the MetalLB Operator and there are existing `FRRConfiguration`
 
 The Cluster Network Operator API exposes the following API field to configure BGP routing:
 
-- `spec.additionalRoutingCapabilities`: Enables deployment of the FRR-K8S daemon for the cluster, which can be used independently of route advertisements. When enabled, the FRR-K8S daemon is deployed on all nodes.
+- `spec.additionalRoutingCapabilities`: Enables deployment of the FRR-K8s daemon for the cluster, which can be used independently of route advertisements. When enabled, the FRR-K8s daemon is deployed on all nodes.
 
 [id="bgp-routing-custom-resources_{context}"]
 == BGP routing custom resources

modules/nw-bgp-frr-k8s-migration.adoc

@@ -10,8 +10,8 @@ You can migrate the FRR-K8s custom resources from the `metallb-system` namespace
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Log in to the cluster with a user with `cluster-admin` privileges.
+* You have installed the {oc-first}.
+* You are logged in to the cluster as a user with the `cluster-admin` role.
 
 .Procedure
 
@@ -24,7 +24,7 @@ When upgrading from an earlier version of {product-title} with the Metal LB Oper
 $ oc create namespace openshift-frr-k8s
 ----
 
-. To automate the migration, create a `migrate.sh` with the following content:
+. To automate the migration, create a shell script named `migrate.sh` with the following contents:
 +
 [source,bash]
 ----
@@ -45,7 +45,9 @@ oc get frrconfigurations.frrk8s.metallb.io -n "${OLD_NAMESPACE}" -o json |\
 $ bash migrate.sh
 ----
 
-. To confirm that the migration succeeded, run the following command:
+.Verification
+
+* To confirm that the migration succeeded, run the following command:
 +
 [source,terminal]
 ----

modules/nw-bgp-routing-config.adoc

@@ -17,9 +17,9 @@ As a cluster administrator, you can enable BGP routing support for your cluster.
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Log in to the cluster with a user with `cluster-admin` privileges.
-* Cluster is installed on compatible infrastructure.
+* You have installed the {oc-first}.
+* You are logged in to the cluster as a user with the `cluster-admin` role.
+* The cluster is installed on compatible infrastructure.
 
 .Procedure
 
@@ -41,9 +41,9 @@ As a cluster administrator, you can disable BGP routing support for your cluster
 
 .Prerequisites
 
-* Install the OpenShift CLI (`oc`).
-* Log in to the cluster with a user with `cluster-admin` privileges.
-* Cluster is installed on compatible infrastructure.
+* You have installed the {oc-first}.
+* You are logged in to the cluster as a user with the `cluster-admin` role.
+* The cluster is installed on compatible infrastructure.
 
 .Procedure
 

networking/bgp_routing/about-bgp-routing.adoc

@@ -8,7 +8,10 @@ toc::[]
 
 This feature provides native Border Gateway Protocol (BGP) routing capabilities for the cluster.
 
+[IMPORTANT]
+====
 If you are using the MetalLB Operator and there are existing `FRRConfiguration` CRs in the `metallb-system` namespace created by cluster administrators or third-party cluster components other than the MetalLB Operator, you must ensure that they are copied to the `openshift-frr-k8s` namespace or that those third-party cluster components use the new namespace. For more information, see xref:../../networking/bgp_routing/migrating-frr-k8s-resources.adoc#migrating-frr-k8s-resources[Migrating FRR-K8s resources].
+====
 
 include::modules/nw-bgp-about.adoc[leveloffset=+1]
 include::modules/nw-metallb-frr-k8s-configuration-crd.adoc[leveloffset=+1]