From 71136b54fa740c146c2d8550ddd245957fe845cc Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Wed, 13 May 2026 12:35:00 +0200
Subject: [PATCH] docs(site-to-vpn): drop the Networks-vs-Network-Routes note

The guide is written around Networks; the side-note suggesting Network
Routes as an alternative path adds noise without value. The Step 4 inline
note keeps the Network Routes equivalent for anyone who needs it.
---
 .../network-routes/use-cases/by-scenario/site-to-vpn.mdx   | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx
index 0a9e85de..2245a57a 100644
--- a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx
+++ b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx
@@ -22,13 +22,6 @@ Clientless Device ──► Routing Peer ──► NetBird Overlay ──► Net
    (no NetBird)         (peer)                              (peer)
 ```
 
-<Note>
-This scenario works with both [Networks](/manage/networks) (recommended) and
-[Network Routes](/manage/network-routes) — the configuration is the same in
-substance, only the dashboard surface differs. Use Networks unless you
-already have an established Network Routes setup. This guide uses Networks.
-</Note>
-
 <Warning>
 The routing peer must perform **outbound source NAT** for site traffic
 entering the NetBird overlay. NetBird performs this automatically only when