OSDOCS-13634-16: Removed TP notice for customized br-ex bridge

Author: dfitzmau

Diff for: modules/creating-manifest-file-customized-br-ex-bridge.adoc

@@ -22,17 +22,11 @@ endif::[]
 
 ifndef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
 As an alternative to using the `configure-ovs.sh` shell script to set a `br-ex` bridge on a bare-metal platform, you can create a `MachineConfig` object that includes an NMState configuration file. The NMState configuration file creates a customized `br-ex` bridge network configuration on each node in your cluster.
-
-:FeatureName: Creating a `MachineConfig` object that includes a customized `br-ex` bridge
-include::snippets/technology-preview.adoc[]
 endif::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
 
 ifdef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
 As an alternative to using the `configure-ovs.sh` shell script to set a `br-ex` bridge on a bare-metal platform, you can create a `NodeNetworkConfigurationPolicy` custom resource (CR) that includes an NMState configuration file. The NMState configuration file creates a customized `br-ex` bridge network configuration on each node in your cluster.
 
-:FeatureName: Creating a `NodeNetworkConfigurationPolicy` CR that includes a customized `br-ex` bridge
-include::snippets/technology-preview.adoc[]
-
 This feature supports the following tasks:
 
 * Modifying the maximum transmission unit (MTU) for your cluster.

Diff for: release_notes/ocp-4-16-release-notes.adoc

@@ -2693,7 +2693,7 @@ In the following tables, features are marked with the following statuses:
 |Configure the `br-ex` bridge needed by OVN-Kuberenetes using NMState
 |Not Available
 |Not Available
-|Technology Preview
+|General Availability
 
 |Creating a route with externally managed certificate
 |Not Available