diff --git a/docs/SUBNETS.md b/docs/SUBNETS.md
new file mode 100755
index 00000000..b5e1db66
--- /dev/null
+++ b/docs/SUBNETS.md
@@ -0,0 +1,10 @@
+## Subnets configuration
+
+The arp-scan time itself depends on the number of IP addresses to check.
+The number of IPs to check depends on the [network mask](https://www.calculator.net/ip-subnet-calculator.html) you set on the `SCAN_SUBNETS` setting.
+
+For example, a `/24` mask results in 256 IPs to check, where as a `/16` mask checks around 65,536. Every IP takes a couple seconds. This means that with an incorrect configuration the arp-scan will take hours to complete instead of seconds.
+
+- Specify the network mask. For example, the filter `192.168.1.0/24` covers IP ranges 192.168.1.0 to 192.168.1.255
+- Run `iwconfig` in your container to find your interface name(s) (e.g.: `eth0`, `eth1`).
+- Append e.g.: ` -vlan=107` to the interface field (e.g.: `eth0 -vlan=107`) for multiple vlans. More details in this [issue](https://github.com/jokob-sk/Pi.Alert/issues/170)
\ No newline at end of file
diff --git a/front/php/templates/language/en_us.php b/front/php/templates/language/en_us.php
index 14ea1f62..05687618 100755
--- a/front/php/templates/language/en_us.php
+++ b/front/php/templates/language/en_us.php
@@ -490,15 +490,7 @@ $lang['en_us'] = array(
'ENABLE_ARPSCAN_description' => 'Arp-scan is a command-line tool that uses the ARP protocol to discover and fingerprint IP hosts on the local network. An alternative to ARP scan is to enable the PIHOLE_ACTIVEPiHole integration settings.',
'SCAN_SUBNETS_name' => 'Subnets to scan',
'SCAN_SUBNETS_description' => '
-The arp-scan time itself depends on the number of IP addresses to check.
-The number of IPs to check depends on the network mask you set here.
-For example, a /24 mask results in 256 IPs to check, where as a /16
-mask checks around 65,536. Every IP takes a couple seconds. This means that with an incorrect configuration
-the arp-scan will take hours to complete instead of seconds.
-
192.168.1.0/24 covers IP ranges 192.168.1.0 to 192.168.1.255.iwconfig in your container to find your interface name(s) (e.g.: eth0, eth1)