Fix headings in the docs

refs #6918

(cherry picked from commit e909302fd90ccc4aecdb99bcc04750c4aa0f098d)

diff --git a/doc/19-technical-concepts.md b/doc/19-technical-concepts.md
index d34e03760e3d7a2c00a7b54abd5430748723d767..045ca39c800943ce5ce17bad5bfce01bcb6fa00a 100644 (file)
--- a/doc/19-technical-concepts.md
+++ b/doc/19-technical-concepts.md
@@ -900,7 +900,7 @@ Event Receiver (Client): `CheckResultAPIHandler` in `REGISTER_APIFUNCTION`
 
 ### Messages
 
-#### <a id="technical-concepts-json-rpc-messages-icinga-hello"></a> icinga::Hello
+#### icinga::Hello <a id="technical-concepts-json-rpc-messages-icinga-hello"></a>
 
 > Location: `apilistener.cpp`
 
@@ -925,7 +925,7 @@ Event Receiver: `HelloAPIHandler`
 
 None, this is a required message.
 
-#### <a id="technical-concepts-json-rpc-messages-event-heartbeat"></a> event::Heartbeat
+#### event::Heartbeat <a id="technical-concepts-json-rpc-messages-event-heartbeat"></a>
 
 > Location: `jsonrpcconnection-heartbeat.cpp`
 
@@ -957,7 +957,7 @@ the client. This is to avoid stale connections with no message processing.
 
 None, this is a required message.
 
-#### <a id="technical-concepts-json-rpc-messages-event-checkresult"></a> event::CheckResult
+#### event::CheckResult <a id="technical-concepts-json-rpc-messages-event-checkresult"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -991,7 +991,7 @@ Message updates will be dropped when:
 * Hosts/services do not exist
 * Origin is a remote command endpoint different to the configured, and whose zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-setnextcheck"></a> event::SetNextCheck
+#### event::SetNextCheck <a id="technical-concepts-json-rpc-messages-event-setnextcheck"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1025,7 +1025,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-setnextnotification"></a> event::SetNextNotification
+#### event::SetNextNotification <a id="technical-concepts-json-rpc-messages-event-setnextnotification"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1060,7 +1060,7 @@ Message updates will be dropped when:
 * Notification does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-setforcenextcheck"></a> event::SetForceNextCheck
+#### event::SetForceNextCheck <a id="technical-concepts-json-rpc-messages-event-setforcenextcheck"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1094,7 +1094,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-setforcenextnotification"></a> event::SetForceNextNotification
+#### event::SetForceNextNotification <a id="technical-concepts-json-rpc-messages-event-setforcenextnotification"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1128,7 +1128,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-setacknowledgement"></a> event::SetAcknowledgement
+#### event::SetAcknowledgement <a id="technical-concepts-json-rpc-messages-event-setacknowledgement"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1167,7 +1167,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-clearacknowledgement"></a> event::ClearAcknowledgement
+#### event::ClearAcknowledgement <a id="technical-concepts-json-rpc-messages-event-clearacknowledgement"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1200,7 +1200,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone is not allowed to access this checkable.
 
-#### <a id="technical-concepts-json-rpc-messages-event-sendnotifications"></a> event::SendNotifications
+#### event::SendNotifications <a id="technical-concepts-json-rpc-messages-event-sendnotifications"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1237,7 +1237,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone the same as the receiver. This binds notification messages to the HA zone.
 
-#### <a id="technical-concepts-json-rpc-messages-event-notificationsentuser"></a> event::NotificationSentUser
+#### event::NotificationSentUser <a id="technical-concepts-json-rpc-messages-event-notificationsentuser"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1277,7 +1277,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone the same as the receiver. This binds notification messages to the HA zone.
 
-#### <a id="technical-concepts-json-rpc-messages-event-notificationsenttoallusers"></a> event::NotificationSentToAllUsers
+#### event::NotificationSentToAllUsers <a id="technical-concepts-json-rpc-messages-event-notificationsenttoallusers"></a>
 
 > Location: `clusterevents.cpp`
 
@@ -1321,7 +1321,7 @@ Message updates will be dropped when:
 * Checkable does not exist.
 * Origin endpoint's zone the same as the receiver. This binds notification messages to the HA zone.
 
-#### <a id="technical-concepts-json-rpc-messages-event-executecommand"></a> event::ExecuteCommand
+#### event::ExecuteCommand <a id="technical-concepts-json-rpc-messages-event-executecommand"></a>
 
 > Location: `clusterevents-check.cpp` and `checkable-check.cpp`
 
@@ -1377,7 +1377,7 @@ The returned messages are synced directly to the sender's endpoint, no cluster b
 
 > **Note**: EventCommand errors are just logged on the remote endpoint.
 
-#### <a id="technical-concepts-json-rpc-messages-config-update"></a> config::Update
+#### config::Update <a id="technical-concepts-json-rpc-messages-config-update"></a>
 
 > Location: `apilistener-filesync.cpp`
 
@@ -1416,7 +1416,7 @@ Config updates will be ignored when:
 * The zone is not configured on the receiver endpoint.
 * The zone is authoritative on this instance (this only happens on a master which has `/etc/icinga2/zones.d` populated, and prevents sync loops)
 
-#### <a id="technical-concepts-json-rpc-messages-config-updateobject"></a> config::UpdateObject
+#### config::UpdateObject <a id="technical-concepts-json-rpc-messages-config-updateobject"></a>
 
 > Location: `apilistener-configsync.cpp`
 
@@ -1490,7 +1490,7 @@ Error handling:
 * Compare modified and original attributes and restore any type of change here.
 
 
-#### <a id="technical-concepts-json-rpc-messages-config-deleteobject"></a> config::DeleteObject
+#### config::DeleteObject <a id="technical-concepts-json-rpc-messages-config-deleteobject"></a>
 
 > Location: `apilistener-configsync.cpp`
 
@@ -1542,7 +1542,7 @@ Error handling:
 
 * Log an error if `DeleteObject` fails (only if the object does not already exist)
 
-#### <a id="technical-concepts-json-rpc-messages-pki-requestcertificate"></a> pki::RequestCertificate
+#### pki::RequestCertificate <a id="technical-concepts-json-rpc-messages-pki-requestcertificate"></a>
 
 > Location: `jsonrpcconnection-pki.cpp`
 
@@ -1574,7 +1574,7 @@ in the `api` feature.
 Only valid certificate request messages are processed, and valid signed certificates
 won't be signed again.
 
-#### <a id="technical-concepts-json-rpc-messages-pki-updatecertificate"></a> pki::UpdateCertificate
+#### pki::UpdateCertificate <a id="technical-concepts-json-rpc-messages-pki-updatecertificate"></a>
 
 > Location: `jsonrpcconnection-pki.cpp`
 
@@ -1614,7 +1614,7 @@ Message updates are dropped when
 * The origin sender is not in a parent zone of the receiver.
 * The certificate fingerprint is in an invalid format.
 
-#### <a id="technical-concepts-json-rpc-messages-pki-updatecertificate"></a> log::SetLogPosition
+#### log::SetLogPosition <a id="technical-concepts-json-rpc-messages-pki-updatecertificate"></a>
 
 > Location: `apilistener.cpp` and `jsonrpcconnection.cpp`