Update TROUBLESHOOTING.md

TROUBLESHOOTING.md

@@ -23,7 +23,7 @@ For issues with the HW/SW inventory, such as no or incomplete CDP/LLDP/IP addres
 - [Inventory IPv4 addresses](https://thl-cmk.hopto.org/gitlab/checkmk/vendor-independent/inventory/inv_ipv4_addresses/-/blob/master/CONTRIBUTING.md)
 - [Interface name](https://thl-cmk.hopto.org/gitlab/checkmk/vendor-independent/inventory/inv_ifname/-/blob/master/CONTRIBUTING.md)
 
-If you have no inventory at all, check your HW/SW-Inventory rule(s) (see the [HowTo](HOWTO.md) ) or the offical Checkmk documentation [The HW/SW Inventory](https://docs.checkmk.com/latest/en/inventory.html?lquery=hw/sw)
+If you have no inventory at all, check your HW/SW-Inventory rule(s) (see the [HowTo](HOWTO.md#3-checkmk-rules)) or the offical Checkmk documentation [The HW/SW Inventory](https://docs.checkmk.com/latest/en/inventory.html?lquery=hw/sw)
 </details>
 
 <details><summary>The desired topology layer was not created</summary>
@@ -99,7 +99,7 @@ A workaround for this problem is to create an empty dummy topology file in the d
 
 This can happen if you have multiple Layer2 domains (CDP/LLDP). E.g. locations that are connected via a WAN connection such as MPLS or the Internet. Normally there is no CDP/LLDP adjacency between these sites.
 
-To solve this problem, add at least one seed device from each site to the configuration file (see [HowTo](HOWTO.md)). This way NVDCT will create a topology file for all Layer2 domains together. To view a specific location, you need to start the topology view from a device of that location. Currently there is no good way to connect these Layer2 domains within Checkmk.
+To solve this problem, add at least one seed device from each site to the configuration file (see [HowTo](HOWTO.md#6-modify-the-user-settings-for-nvdct)). This way NVDCT will create a topology file for all Layer2 domains together. To view a specific location, you need to start the topology view from a device of that location. Currently there is no good way to connect these Layer2 domains within Checkmk.
 
 </details>
 
@@ -190,6 +190,6 @@ DROP_HOSTS_REGEX = [
 
 1. check whether the L3v4 layer is activated in the configuration file or whether the -l L3v4 option is used (see above _The desired topology layer was not created_)
 
-1. The creation of the Layer3 topology is based on the host label `nvdct/routing_capable:yes`. This label is added by the `inv_ip_address` plugin to all hosts with more than one IP address. After the inventory has been run, you must rediscover the host labels in Checkmk. See the [HowTo](HOWTO.md) or the Checkmk documentation about [Labels](https://docs.checkmk.com/latest/en/labels.html?lquery=host%20label)
+1. The creation of the Layer3 topology is based on the host label `nvdct/routing_capable:yes`. This label is added by the `inv_ip_address` plugin to all hosts with more than one IP address. After the inventory has been run, you must rediscover the host labels in Checkmk. See the [HowTo](HOWTO.md#4-host-labels) or the Checkmk documentation about [Labels](https://docs.checkmk.com/latest/en/labels.html?lquery=host%20label)
 
 </details>