Checkpoint

Author: jab-rh

modules/nw-bgp-about.adoc

@@ -21,7 +21,7 @@ https://github.com/openshift/openshift-docs/pull/85842/files#r1900917285
 
 BGP routing is supported on the following infrastructure types:
 
-- Bare-metal
+- Bare metal
 - {vmw-full} on-premise
 
 [id="prerequisites_{context}"]
@@ -34,11 +34,11 @@ Use of BGP routing requires that you have properly configured BGP for your netwo
 
 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]
 ====
-If you are using the MetalLB Operator prior to upgrading to {product-title} 4.18, you must manually copy any existing `FRRConfiguration` CRs in the `metallb-system` namespace to the `openshift-frr-k8s` namespace. This includes `FRRConfiguration` CRs created by both cluster administrators and by cluster components.
+If you are using the MetalLB Operator before upgrading to {product-title} 4.18, you must manually copy any existing `FRRConfiguration` CRs in the `metallb-system` namespace to the `openshift-frr-k8s` namespace. This includes `FRRConfiguration` CRs created by both cluster administrators and by cluster components.
 ====
 
 [id="cluster-network-operator_{context}"]