From f59cfd8dec39b9b528443d71a2af8a356de01bb7 Mon Sep 17 00:00:00 2001
From: Steven Smith <77019920+stevsmit@users.noreply.github.com>
Date: Fri, 27 Oct 2023 08:35:32 -0400
Subject: [PATCH] Revert "Adds TP designation BACK to multi-nic docs"

---
 modules/nw-egress-ips-about.adoc | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/modules/nw-egress-ips-about.adoc b/modules/nw-egress-ips-about.adoc
index 25f6dde6e6..a797fd2ef5 100644
--- a/modules/nw-egress-ips-about.adoc
+++ b/modules/nw-egress-ips-about.adoc
@@ -150,9 +150,6 @@ For more information, see link:https://docs.microsoft.com/en-us/azure/azure-reso
 [id="nw-egress-ips-multi-nic-considerations_{context}"]
 == Considerations for using an egress IP on additional network interfaces
 
-:FeatureName: Using an egress IP on additional network interfaces
-include::snippets/technology-preview.adoc[]
-
 In {product-title}, egress IPs provide administrators a way to control network traffic. Egress IPs can be used with the `br-ex`, or primary, network interface, which is a Linux bridge interface associated with Open vSwitch, or they can be used with additional network interfaces. 
 
 You can inspect your network interface type by running the following command: