docs: remove experimental lazy connections wording

src/pages/get-started/cli.mdx

@@ -102,7 +102,7 @@ The command will check if the peer is logged in and connect to the management se
       --disable-ssh-auth                    Disable SSH JWT authentication. If enabled, any peer with network access can connect without user authentication.
       --dns-resolver-address string         Sets a custom address for NetBird's local DNS resolver. If set, the agent won't attempt to discover the best IP and port to listen on. An empty string "" clears the previous configuration. E.g. --dns-resolver-address 127.0.0.1:5053 or --dns-resolver-address ""
       --dns-router-interval duration        DNS route update interval (default 1m0s)
-      --enable-lazy-connection              [Experimental] Enable the lazy connection feature. If enabled, the client will establish connections on-demand. Note: this setting may be overridden by management configuration.
+      --enable-lazy-connection              Enable the lazy connection feature. If enabled, the client will establish connections on-demand. Note: this setting may be overridden by management configuration.
       --enable-rosenpass                    [Experimental] Enable Rosenpass feature. If enabled, the connection will be post-quantum secured via Rosenpass.
       --enable-ssh-local-port-forwarding    Enable local port forwarding for SSH server
       --enable-ssh-remote-port-forwarding   Enable remote port forwarding for SSH server

src/pages/manage/peers/lazy-connection.mdx

@@ -1,7 +1,7 @@
 import {Note} from "@/components/mdx";
 
 # Lazy Connections
-NetBird now includes an experimental lazy connection feature designed to improve performance and reduce resource usage by connecting to peers only when needed. Instead of maintaining always-on connections, NetBird activates them on-demand based on activity or signaling.
+NetBird includes a lazy connection feature designed to improve performance and reduce resource usage by connecting to peers only when needed. Instead of maintaining always-on connections, NetBird activates them on-demand based on activity or signaling.
 
 This guide walks you through enabling and configuring this feature in your NetBird client.
 
@@ -15,10 +15,6 @@ This guide walks you through enabling and configuring this feature in your NetBi
     If you're self-hosting NetBird, ensure your server is updated to version <strong>v0.50.1</strong>, which adds support for lazy connections.
 </Note>
 
-<Note>
-    This feature is currently under active development and will continue to evolve. Future releases will enhance disconnection logic and add support for accessing resources through routing peers, which is not yet available.
-</Note>
-
 ## What Are Lazy Connections?
 
 When enabled, lazy connections allow the NetBird agent to:

src/pages/use-cases/security/implement-zero-trust.mdx

@@ -638,10 +638,10 @@ At larger scale, you will care about:
 - Overlapping routes to different environments (for example, multiple `172.17.0.0/16` networks)
 - Connection overhead for many peers
 
-NetBird has route selection tools and an experimental lazy connections feature for large networks. In practice:
+NetBird has route selection tools and a lazy connections feature for large networks. In practice:
 
 - Use network/route selection to avoid accidental routing into the wrong VPC or site when CIDRs overlap. You can do this in the systray application or via the command line.
-- [Lazy connections](/manage/peers/lazy-connection) reduce CPU and battery usage on devices by establishing tunnels only when traffic is sent, rather than maintaining keep-alive with every peer in the mesh. Note that lazy connections is an experimental feature that requires NetBird client version 0.50.1 or later and does NOT support accessing resources through routing peers (Networks). Review the current scaling guidance and lazy connections documentation before rolling out to thousands of peers.
+- [Lazy connections](/manage/peers/lazy-connection) reduce CPU and battery usage on devices by establishing tunnels only when traffic is sent, rather than maintaining keep-alive with every peer in the mesh. Note that lazy connections require NetBird client version 0.50.1 or later. Review the current scaling guidance and lazy connections documentation before rolling out to thousands of peers.
 
 <Note>
 **Verification checklist:**