# \[PATCH 2/2\] Rephrase allowedNetworks for understandability
**URL:** https://forum.syncthing.net/t/patch-2-2-rephrase-allowednetworks-for-understandability/23358
**Category:** General
**Created:** [December 4, 2024, 4:10pm UTC](https://forum.syncthing.net/t/patch-2-2-rephrase-allowednetworks-for-understandability/23358 "2024-12-04T16:10:19Z")
**Posts on this page:** 1
**Page:** 1
### Author:  [@foo](https://forum.syncthing.net/u/foo)
#### Post date: [December 4, 2024, 4:10pm UTC](https://forum.syncthing.net/t/patch-2-2-rephrase-allowednetworks-for-understandability/23358/1 "2024-12-04T16:10:19Z")
As mentioned in [my previous post](https://forum.syncthing.net/t/patch-1-2-clarify-disco-only-is-required-for-dynamic-peers/23357), my initial encounter with syncthing resulted in two tiny patches. Here follows the [second](https://git.netizen.se/syncthing-docs/commit/?h=disco%2ballowednetworks&id=0184c58) of those:
```diff
From 525f83b340e0aa1fb5afbf92525c195ae64de030 Mon Sep 17 00:00:00 2001
From: cos
Date: Fri, 5 Apr 2024 10:22:49 +0200
Subject: [PATCH 2/2] Rephrase allowedNetworks for understandability
Given that the detailed description emphasize the word *remote*, it
appears to have been clear already in 572930bf that the naming makes
it easy to mistake what this option targets. I assume to not have been
the only one understanding it to mean the opposite of what it actually
does after reading the docs in its current wording
---
users/config.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/users/config.rst b/users/config.rst
index 2d42b3c..dcd07e2 100644
--- a/users/config.rst
+++ b/users/config.rst
@@ -764,9 +764,9 @@ From the following child elements at least one ``address`` child must exist.
.. option:: device.allowedNetwork
:aliases: device.allowedNetworks
- If given, this restricts connections to this device to only this network.
- The mechanism is described in detail in a :doc:`separate chapter
- `).
+ If given, restricts to only connect to this device when it is reachable
+ through any of these networks. The mechanism is described in detail in a
+ :doc:`separate chapter `).
.. option:: device.autoAcceptFolders
--
2.46.1
```
I’m far from convinced my suggestion here actually improves things. However I am quite confident that the current phrasing is confusing. I believe misconceptions about how this configuration directive works has been the cause of questions asked independently from at least two other persons on irc since I joined the channel in April.