diff --git a/netalertx/README.md b/netalertx/README.md
index 5ad9dad1f..9ff93dbe0 100644
--- a/netalertx/README.md
+++ b/netalertx/README.md
@@ -49,7 +49,7 @@ comparison to installing any other Hass.io add-on.
 ## Configuration
 
 1. If unavailable, the app generates a default `app.conf` and `app.db` file on the first run.
-1. The preferred way is to manage the configuration via the Settings section in the UI, if UI is inaccessible you can modify `app.conf` in the `/data/config/` folder directly.
+1. The preferred way is to manage the configuration via the Settings section in the UI, if UI is inaccessible you can modify `app.conf` in the `/config/config/` folder directly.
 1. You have to specify which network(s) should be scanned. This is done by entering subnets that are accessible from the host. If you use the default `ARPSCAN` plugin, you have to specify at least one valid subnet and interface in the `SCAN_SUBNETS` setting. See the [documentation on How to set up multiple SUBNETS, VLANs and what are limitations](https://github.com/jokob-sk/NetAlertX/blob/main/docs/SUBNETS.md) and for troubleshooting and more advanced scenarios.
 1. Read how to get devices into your [Home Assistant instance via the MQTT plugin](https://github.com/jokob-sk/NetAlertX/blob/main/docs/HOME_ASSISTANT.md)
 1. Back everything up by following the [Backups documentation](https://github.com/jokob-sk/NetAlertX/blob/main/docs/BACKUPS.md).