diff --git a/admin-guide/configuration/icinga2.md b/admin-guide/configuration/icinga2.md
index 47ab8d84..e2286e12 100644
--- a/admin-guide/configuration/icinga2.md
+++ b/admin-guide/configuration/icinga2.md
@@ -26,7 +26,7 @@ Still no alerts are generated, respectively they are suppressed by a global infi
 icinga2::alerting::enable: true
 ```
 
-Per default these alerts are now sent during office hours to the admins. For further notification fine tuning checkout the chapters [Notifications](#notifications) and [Check Customization](#check-customization).
+Per default these alerts are now sent during office hours to the admins. For further notification fine tuning checkout the chapters [](#notifications) and [](#check-customization).
 
 Finally, if Icinga2 shall be managed without Puppet (not recommended except for Icinga2 infrastructure servers), then set
 ```
@@ -38,6 +38,7 @@ icinga2::puppet: false
 Users and groups in `aaa::admins` and `icinga2::web::users` will have access to these nodes on [monitoring.psi.ch](https://monitoring.psi.ch).
 Prefix the group name with a `%` to distinguish them from users.
 
+(notifications)=
 ## Notifications
 
 ### Notification Recipients
@@ -81,6 +82,7 @@ The minimal settings are applied, e.g. a service with criticality `C` will never
 By default we already run a comprehensive set of checks. Some of them can be fine-tuned in Hiera.
 Whenever you have a use case which is not covered yet, please talk to us.
 
+(check-customization)=
 ## Check Customization
 
 Most checks can have custom parameters. The variables you can adapt you find as "Custom Variables" in the page of given service. In Hiera you can add below the key `icinga2::service_check::customize` as multi level hash the service name and below the variable name with the new values.