diff --git a/README.md b/README.md
index 7d2a92d..12cfe9f 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@ Based on this it's also possible to use a network target to simply replicate sna
 
 ## Config
 
-You should have a subvolume present already on your backup drive using something like `snap-sync -c "root home" -d "latest incremental backup"` pointing to `snapshot_root` configured in [clean-snap-sync-external.sh](scripts/clean-snap-sync-external.sh). After first replication snap-sync automatically uses the same subvolume again so that you just have to set the UUID of your external drive you placed your initial snapshot on in the bash scripts in the [scripts](scripts) folder.
+You should have a subvolume present already on your backup drive using something like `snap-sync -c "root home" -d "latest incremental backup"` pointing to `snapshot_root` configured in [clean-snap-sync-external.sh](scripts/clean-snap-sync-external.sh#L16). After first replication snap-sync automatically uses the same subvolume again so that you just have to set the UUID of your external drive you placed your initial snapshot on in the bash scripts in the [scripts](scripts) folder.
 
 If you are going to enable `snap-sync-cleanup.service`, edit the snapshot root and the amount of snapshots to keep on the external drive in `clean-snap-sync-external.sh` as well.