diff --git a/content/docs/manage/resources/private/exit-node.mdx b/content/docs/manage/resources/private/exit-node.mdx
index b1e987b..8af46cd 100644
--- a/content/docs/manage/resources/private/exit-node.mdx
+++ b/content/docs/manage/resources/private/exit-node.mdx
@@ -13,14 +13,11 @@ Sometimes you do want Pangolin to carry your public internet traffic, for instan
 To do this, make a site an exit node and point other devices at it using an exit node resource. Routing everything through an exit node uses the default routes (0.0.0.0/0, ::/0), the same way a typical VPN does.
 
 <Note>
-    Exit nodes and subnet routers both route traffic, but they do different
-    jobs. An exit node sends outbound internet traffic from your Pangolin
-    clients through sites, like a VPN server. Your traffic appears to originate
-    from the exit node's location, which helps with geo-restricted content or
-    privacy. A subnet router gives access to specific private subnets. Pangolin
-    clients can reach Pangolin resources in those subnets, and internet routing
-    is unchanged. For private networks such as office LANs or cloud VPCs, use a
-    subnet router.
+    Looking to reach a private network such as an office LAN or a cloud VPC
+    instead? Use a [subnet router](/manage/clients/subnet-router). It gives
+    Pangolin clients access to resources in specific private subnets and lets
+    devices that can't run the Pangolin client connect too. It doesn't change
+    how internet traffic is routed.
 </Note>
 
 ## Benefits