Removing the table

Author: robscott

content/en/docs/concepts/services-networking/ingress-controllers.md

@@ -22,31 +22,14 @@ This means that:
 
 <!-- overview -->
 
-## Consider using Gateway API
+## Preferred Option: Gateway API
+
 [Gateway API](/docs/concepts/services-networking/gateway/) is stable and
-includes many more features (and controllers). The following table highlights
-some of the differences between the APIs. Note that many implementations extend
-these APIs with implementation-specific features, this table focuses on portable
-features that are included directly within each Kubernetes API:
-
-{{< table caption = "Comparing Ingress API and Gateway API" >}}
-| | Ingress API | Gateway API |
-| - | - | - |
-| Stable (v1) | ✅ Yes | ✅ Yes |
-| Basic HTTP path matching | ✅ Yes | ✅ Yes |
-| Traffic Splitting | ❌ No | ✅ Yes |
-| Protocols | 🟡 HTTP(S) | ✅ HTTP(S), gRPC, TLS |
-| Advanced Matchers (Headers, Query Params, Methods) | ❌ No | ✅ Yes |
-| Redirects | ❌ No | ✅ Yes |
-| Rewrites | ❌ No | ✅ Yes |
-| TLS Validation | ❌ No | ✅ Yes |
-| Cross-Namespace References | ❌ No | ✅ Yes |
-| AI Extensions | ❌ No | ✅ [Yes](https://gateway-api-inference-extension.sigs.k8s.io/) |
-| Service Mesh Support | ❌ No | ✅ Yes |
-| More Features in Development | ❌ No | ✅ Yes |
-| Conformance Tests | 🟡 Some | ✅ Thorough |
-| # of Implementations | ✅ [30+](/docs/concepts/services-networking/ingress-controllers) | ✅ [30+](https://gateway-api.sigs.k8s.io/implementations/) |
-{{</ table >}}
+includes many more features (and implementations). Instead of relying on an
+assortment of implementation-specific annotations, Gateway API allows you to
+use a broad set of Core APIs with a wide variety of implementations. Unlike
+Ingress, Gateway API is still under active development and continues to gain
+new capabilities with each release.
 
 ## Ingress controllers
 
@@ -55,7 +38,7 @@ Kubernetes as a project supports and maintains [AWS](https://github.com/kubernet
 
 <!-- body -->
 
-## Additional controllers
+## Controllers
 
 {{% thirdparty-content %}}
 

content/en/docs/concepts/services-networking/ingress.md

@@ -32,31 +32,14 @@ This means that:
 
 <!-- body -->
 
-## Consider using Gateway API
+## Preferred Option: Gateway API
+
 [Gateway API](/docs/concepts/services-networking/gateway/) is stable and
-includes many more features (and controllers). The following table highlights
-some of the differences between the APIs. Note that many implementations extend
-these APIs with implementation-specific features, this table focuses on portable
-features that are included directly within each Kubernetes API:
-
-{{< table caption = "Comparing Ingress API and Gateway API" >}}
-| | Ingress API | Gateway API |
-| - | - | - |
-| Stable (v1) | ✅ Yes | ✅ Yes |
-| Basic HTTP path matching | ✅ Yes | ✅ Yes |
-| Traffic Splitting | ❌ No | ✅ Yes |
-| Protocols | 🟡 HTTP(S) | ✅ HTTP(S), gRPC, TLS |
-| Advanced Matchers (Headers, Query Params, Methods) | ❌ No | ✅ Yes |
-| Redirects | ❌ No | ✅ Yes |
-| Rewrites | ❌ No | ✅ Yes |
-| TLS Validation | ❌ No | ✅ Yes |
-| Cross-Namespace References | ❌ No | ✅ Yes |
-| AI Extensions | ❌ No | ✅ [Yes](https://gateway-api-inference-extension.sigs.k8s.io/) |
-| Service Mesh Support | ❌ No | ✅ Yes |
-| More Features in Development | ❌ No | ✅ Yes |
-| Conformance Tests | 🟡 Some | ✅ Thorough |
-| # of Implementations | ✅ [30+](/docs/concepts/services-networking/ingress-controllers) | ✅ [30+](https://gateway-api.sigs.k8s.io/implementations/) |
-{{</ table >}}
+includes many more features (and implementations). Instead of relying on an
+assortment of implementation-specific annotations, Gateway API allows you to
+use a broad set of Core APIs with a wide variety of implementations. Unlike
+Ingress, Gateway API is still under active development and continues to gain
+new capabilities with each release.
 
 ## Terminology