diff --git a/HOWTO.md b/HOWTO.md
index 1a73ca6e8749a7ac844da9cc20a6f5bc19ba29cf..b708363a1b71e2972f6be3396662828cddbc4dc8 100644
--- a/HOWTO.md
+++ b/HOWTO.md
@@ -62,11 +62,11 @@ Run the HW/SW inventory at least once for each host and then check whether the r
 
 ## 6. Modify the user settings for NVDCT
 
-Before you create the topology data, take a look at `~/local/bin/nvdct/conf/nvdct.toml`. Here you can fine tune some aspects of the topology creation. Before you do this, please create a copy of the nvdct.toml file (e.g. my_nvdct.toml) and only change the copy. By working with a copy of the `nvdct.toml` file, you ensure that your changes will survive the next update of the `nvdct.mkp`. For the CDP/LLDP topologies add at least your seed devices - from where NVDCT will start to create the topology - in the `SEED_DEVICES` section.
+Before you create the topology data, take a look at `~/local/bin/nvdct/conf/nvdct.toml`. Here you can fine tune some aspects of the topology creation. Before you do this, please create a copy of the nvdct.toml file (e.g. my_nvdct.toml) and only change the copy. By working with a copy of the `nvdct.toml` file, you ensure that your changes will survive the next update of the `nvdct.mkp`. For the CDP/LLDP topologies add at least your seed devices - from where NVDCT will start to create the topology - in the `L2_SEED_DEVICES` section.
 
 ```
 # list of (additional to -s/--seed-devices) seed devices
-SEED_DEVICES = [
+L2_SEED_DEVICES = [
     "DEVICE01",
     "DEVICE02",
     "DEVICE03",
@@ -83,7 +83,7 @@ layers = ["LLDP", "L3v4"]
 ## 7. Create the topology data
 
 ```
-~/local/bin/nvdct/nvdct.py -u ~/local/bin/nvdct/conf/my_nvdct.toml
+~/local/bin/nvdct/nvdct.py -u ~/local/bin/nvdct/conf/my_nvdct.toml -d
 ```
 
 For CMK 2.3.0 you should find the created data under `~/var/check_mk/topology/data`. There should be also a symbolic link to the default topology.