docs: standardize on "NetBird client" over "agent" for the client software (#940)

* docs: standardize on "NetBird client" over "agent" for the client software

* docs: address review feedback

- fix "a software" grammar and use lowercase "NetBird client"
- define routing peer as a peer whose client bridges, keeping peer and client distinct
- correct kernel-space claim: the kernel WireGuard data path is what runs in the kernel
- clarify which address the application uses to reach the SOCKS5 proxy from a separate container
This commit is contained in:
Jack Carter
2026-08-21 13:24:33 +02:00
committed by GitHub
parent d60d579197
commit 62baad95a1
28 changed files with 50 additions and 47 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ NetBird's client honors policies pushed by your Mobile Device Management
(MDM) channel, so an administrator can enforce configuration across a
fleet of devices instead of touching each machine. On every supported
platform the daemon reads from the **OS-native managed-configuration
store** that your MDM already writes to. No agent of ours sits between
store** that your MDM already writes to. No extra NetBird software sits between
you and the MDM provider; whatever you can push to that store (manually,
via Group Policy, via a Configuration Profile, via your MDM console)
becomes effective NetBird policy.