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
@@ -115,7 +115,7 @@ The current version of NetBird tracks a wide range of network changes that occur
</details>
Future versions will also support connection events that occur in NetBird agents (e.g., peer A connected to peer B).
Future versions will also support connection events that occur in NetBird clients (e.g., peer A connected to peer B).
<Note>
The `unknown` name or `unknown@unknown.com` email address may be displayed in the activity event store if the encryption key has been corrupted or lost. This issue is most relevant for self-hosted setups. In this case, the events returned by the API could show `unknown@unknown.com` for the email address field and `unknown` for the name field.