Revise

Author: jab-rh

networking/bgp_routing/about-bgp-routing.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 This feature provides native Border Gateway Protocol (BGP) routing capabilities for the cluster.
 
-If you have any FRR-K8s custom resources that you created in the `metallb-system` namespace, you must migrate them to the `openshift-frr-k8s` namespace. For more information, see xref:../../networking/bgp_routing/migrating-frr-k8s-resources.adoc#migrating-frr-k8s-resources[Migrating FRR-K8s resources].
+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]

networking/bgp_routing/migrating-frr-k8s-resources.adoc

@@ -6,6 +6,6 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-All user-created FRR-K8s custom resources (CRs) in the `metallb-system` namespace under {product-title} 4.17 and earlier releases must be  migrated to the `openshift-frr-k8s` namespace. As a cluster administrator, complete the steps in this procedure to migrate your FRR-K8s custom resources.
+All user-created FRR-K8s custom resources (CRs) in the `metallb-system` namespace under {product-title} 4.17 and earlier releases must be migrated to the `openshift-frr-k8s` namespace. As a cluster administrator, complete the steps in this procedure to migrate your FRR-K8s custom resources.
 
 include::modules/nw-bgp-frr-k8s-migration.adoc[leveloffset=+1]