Apply suggestions from code review

jab-rh · eromanova97 · web-flow · commit 890cd7d16aa7 · 2025-05-15T13:33:36.000-04:00
Co-authored-by: Eliska Romanova &lt;eromanov@redhat.com&gt;
diff --git a/release_notes/ocp-4-19-release-notes.adoc b/release_notes/ocp-4-19-release-notes.adoc
@@ -444,7 +444,7 @@ Starting in {product-title} 4.14, Extended Update Support (EUS) is extended to t
 
 The Cluster Network Operator (CNO) now supports enabling Border Gateway Protocol (BGP) routing. With BGP, you can import and export routes to the underlying provider network and use multi-homing, link redundancy, and fast convergence. BGP configuration is managed with the `FRRConfiguration` custom resource (CR).
 
-When upgrading from an earlier version of {product-title} with the Metal LB Operator deployed, you must manually migrate your custom frr-k8s configurations from the `metallb-system` namespace to the `openshift-frr-k8s` namespace. To move these CRs, enter the following commands:
+When upgrading from an earlier version of {product-title} in which you installed the MetalLB Operator, you must manually migrate your custom frr-k8s configurations from the `metallb-system` namespace to the `openshift-frr-k8s` namespace. To move these CRs, enter the following commands:
 
 . To create the `openshift-frr-k8s` namespace, enter the following command:
 +

Original file line number	Diff line number	Diff line change
`@@ -444,7 +444,7 @@ Starting in {product-title} 4.14, Extended Update Support (EUS) is extended to t`
`444`	`444`
`445`	`445`	The Cluster Network Operator (CNO) now supports enabling Border Gateway Protocol (BGP) routing. With BGP, you can import and export routes to the underlying provider network and use multi-homing, link redundancy, and fast convergence. BGP configuration is managed with the `FRRConfiguration` custom resource (CR).
`446`	`446`
`447`		-When upgrading from an earlier version of {product-title} with the Metal LB Operator deployed, you must manually migrate your custom frr-k8s configurations from the `metallb-system` namespace to the `openshift-frr-k8s` namespace. To move these CRs, enter the following commands:
	`447`	+When upgrading from an earlier version of {product-title} in which you installed the MetalLB Operator, you must manually migrate your custom frr-k8s configurations from the `metallb-system` namespace to the `openshift-frr-k8s` namespace. To move these CRs, enter the following commands:
`448`	`448`
`449`	`449`	. To create the `openshift-frr-k8s` namespace, enter the following command:
`450`	`450`	`+`