diff --git a/docs/known-limitations/known-limitations.md b/docs/known-limitations/known-limitations.md
index c339814a..eb2ecdaf 100644
--- a/docs/known-limitations/known-limitations.md
+++ b/docs/known-limitations/known-limitations.md
@@ -6,7 +6,6 @@ working hard to address:
 * [Deleting a VPC and creating a new one right away can cause the agent to fail](#deleting-a-vpc-and-creating-a-new-one-right-away-can-cause-the-agent-to-fail)
 * [Configuration not allowed when port is member of PortChannel](#configuration-not-allowed-when-port-is-member-of-portchannel)
 * [External peering over a connection originating from an MCLAG switch can fail](#external-peering-over-a-connection-originating-from-an-mclag-switch-can-fail)
-* [Mesh limitations on TH5-based devices](#mesh-limitations-on-th5-based-devices)
 * [Breakout and CMIS transceiver initialization issues on DS5000](#breakout-and-cmis-transceiver-initialization-issues-on-ds5000)
 
 ### Deleting a VPC and creating a new one right away can cause the agent to fail
@@ -72,26 +71,6 @@ No connectivity from the workload server(s) in the VPC towards the prefix routed
 
 Connect your externals to non-MCLAG switches instead.
 
-### Mesh limitations on TH5-based devices
-
-On TH5-based devices, such as the Celestica DS5000, mesh topologies have major
-limitations:
-
-* Failover of mesh connections using an intermediate mesh node does not
-  work correctly
-* Gateway peering of VPCs does not work correctly, i.e. VPCs attached to leaves
-  that are not directly connected to the gateway node cannot peer properly via
-  the gateway
-
-We are investigating these issues together with our partners to determine the
-root cause and possible workarounds.
-
-#### Known workarounds
-
-None. We recommend avoiding mesh topologies on TH5-based devices for the
-time being, with the exception of 2-node topologies without gateway, where
-the above issues would not apply.
-
 ### Breakout and CMIS transceiver initialization issues on DS5000
 
 On Celestica DS5000 devices, certain transceivers using the Common Management Interface Specification (CMIS) fail to initialize properly under specific conditions.
diff --git a/docs/user-guide/connections.md b/docs/user-guide/connections.md
index 2643a4f7..7a3afa8c 100644
--- a/docs/user-guide/connections.md
+++ b/docs/user-guide/connections.md
@@ -147,10 +147,6 @@ A Mesh connection is used between a pair of leaf switches directly connected to
 for a spine switch in between. This can be used to create smaller mesh topologies, or to connect border leaves
 to the fabric when there are no available spine ports.
 
-!!! warning
-    Mesh connections have major limitations on TH5-based devices. See the
-    [Known Limitations](../known-limitations/known-limitations.md#mesh-limitations-on-th5-based-devices) section for details.
-
 Here's an example YAML definition of a Mesh connection between two leaves:
 
 ```yaml
@@ -276,8 +272,7 @@ spec:
 These connection types are for gateway to spine connections. These connections
 will carry the traffic between VPCs that need network services, like NAT. More
 details about the Gateway are in the [Gateway section](gateway.md). In a mesh
-topology the connections will be between gateway and the leaf nodes. Note that
-gateway is not supported with mesh connections on TH5 leafs.
+topology the connections will be between gateway and the leaf nodes.
 
 ```{.yaml .annotate linenums="1" filename="gw-connection.yaml"}
 apiVersion: wiring.githedgehog.com/v1beta1