docs: rename Network Routes to Routes, deprecate, and relocate Browser Client Architecture (#792)

* docs: rename Network Routes to Routes, deprecate, and relocate Browser Client Architecture

- Rename the docs sidebar entry "Network Routes" to "Routes" and the page H1
- Add a deprecation note to the Routes page: all use cases except exit nodes
  have moved to Networks; reconcile the body framing accordingly
- Move Browser Client Architecture under Peers > Browser Client
  (/manage/peers/browser-client/architecture), nest the nav, add a redirect,
  and update cross-links
- Shrink the site-to-site Architecture diagram boxes to fit their content

* docs: rename Routes nav 'Concept' link to 'Overview'

src/pages/introduction.mdx

@@ -102,7 +102,7 @@ It literally takes less than 5 minutes to deploy a secure point-to-point VPN wit
         'Compare NetBird Cloud with the self-hosted version and decide which deployment fits your needs.',
     },
     {
-      href: '/about-netbird/browser-client-architecture',
+      href: '/manage/peers/browser-client/architecture',
       name: 'Browser Client Architecture',
       description:
         'Understand how the Browser Client enables secure remote access directly from web browsers using WebAssembly.',

src/pages/manage/network-routes/index.mdx

@@ -1,9 +1,13 @@
 import { Note, Warning, Button } from '@/components/mdx'
 import { Tiles } from '@/components/Tiles'
 
-# Network Routes
+# Routes
 
-Network Routes let you route traffic from NetBird peers to private networks without installing the NetBird agent on every device. A routing peer forwards packets between your NetBird mesh network and your internal networks (LANs, VPCs, data centers).
+<Warning>
+Routes are deprecated. Every use case except [exit nodes](/manage/network-routes/use-cases/exit-nodes) has moved to [Networks](/manage/networks). Use Networks for all new configurations. For a side-by-side comparison of the two models, see [How Routing Peers Work](/manage/networks/how-routing-peers-work).
+</Warning>
+
+Network Routes let you route traffic from NetBird peers to private networks without installing the NetBird client on every device. A routing peer forwards packets between your NetBird mesh network and your internal networks (LANs, VPCs, data centers).
 
 <p>
     <img src="/docs-static/img/manage/network-routes/concepts/netbird-network-routes.png" alt="Network Routes diagram" className="imagewrapper-big"/>
@@ -17,12 +21,6 @@ Network Routes require NetBird [v0.9.0](https://github.com/netbirdio/netbird/rel
 By default, Network Routes bypass Access Control rules. Traffic flows freely to routed networks unless you [configure access control explicitly](/manage/network-routes/access-control). See [Network Routes caveats](#network-routes-caveats) for details.
 </Warning>
 
-## Network Routes vs Networks
-
-[Networks](/manage/networks) is the newer, simpler replacement for Network Routes. We recommend using Networks where possible; however, Networks do not yet support all remote access scenarios. Network Routes will continue to be maintained, so choose whichever fits your use case.
-
-For a detailed comparison, see our [site-to-site documentation](/use-cases/site-to-site).
-
 ## Key Concepts
 
 ### Network Identifiers and Ranges

src/pages/manage/network-routes/use-cases/site-to-site.mdx

@@ -6,11 +6,15 @@ Site-to-Site connects two networks through routing peers at each end. Neither en
 
 ## Architecture
 
+<div className="not-prose w-fit max-w-full">
+
 ```
 Site A device ──► Routing Peer ──► NetBird Tunnel ──► Routing Peer ──► Site B device
  (no NetBird)       (peer)                              (peer)         (no NetBird)
 ```
 
+</div>
+
 <Note>
 For most site-to-site setups, prefer [Networks Site-to-Site](/manage/networks/use-cases/site-to-site) — it has per-Resource access control and is the actively developed system.
 

src/pages/manage/networks/use-cases/site-to-site.mdx

@@ -6,11 +6,15 @@ Site-to-Site connects two networks through routing peers at each end. Neither en
 
 ## Architecture
 
+<div className="not-prose w-fit max-w-full">
+
 ```
 Site A device ──► Routing Peer ──► NetBird Tunnel ──► Routing Peer ──► Site B device
  (no NetBird)       (peer)                              (peer)         (no NetBird)
 ```
 
+</div>
+
 <Note>
 Networks is the recommended way to build site-to-site. It has per-Resource access control, is Zero Trust by default, and is the actively developed system.
 

src/pages/manage/peers/browser-client.mdx

@@ -141,7 +141,7 @@ The Browser Client maintains NetBird's security standards:
 
 ## Technical Implementation
 
-For technical details on the Browser Client architecture, see the [Browser Client Technical Architecture](/about-netbird/browser-client-architecture) documentation.
+For technical details on the Browser Client architecture, see the [Browser Client Technical Architecture](/manage/peers/browser-client/architecture) documentation.
 
 ### SSH Requirements