Adjust docs for 2.10.x from cherry-picked commits

diff --git a/doc/12-icinga2-api.md b/doc/12-icinga2-api.md
index 79c076353fd4a1756a778907c0436882b75e1c05..5bbe226067ebfc3b8298e33e549664cf722dc584 100644 (file)
--- a/doc/12-icinga2-api.md
+++ b/doc/12-icinga2-api.md
@@ -308,7 +308,7 @@ consider passing them in the request body. For GET requests, this method is expl
 [here](12-icinga2-api.md#icinga2-api-requests-method-override).
 
 You can use [jo](https://github.com/jpmens/jo) to format JSON strings on the shell. An example
-for API actions shown [here](#icinga2-api-actions-unix-timestamps).
+for API actions shown [here](12-icinga2-api.md#icinga2-api-actions-unix-timestamps).
 
 
 ### Global Parameters <a id="icinga2-api-parameters-global"></a>
@@ -2247,11 +2247,11 @@ and developers have been working hard to add more REST API
 clients and integrations into DevOps tools.
 
 * [Libraries](12-icinga2-api.md#icinga2-api-clients-libraries)
-* [Status](#icinga2-api-clients-status)
-* [Management](#icinga2-api-clients-management)
-* [Event Streams](#icinga2-api-clients-event-streams)
-* [Actions](#icinga2-api-clients-actions)
-* [REST API Apps](#icinga2-api-clients-apps)
+* [Status](12-icinga2-api.md#icinga2-api-clients-status)
+* [Management](12-icinga2-api.md#icinga2-api-clients-management)
+* [Event Streams](12-icinga2-api.md#icinga2-api-clients-event-streams)
+* [Actions](12-icinga2-api.md#icinga2-api-clients-actions)
+* [REST API Apps](12-icinga2-api.md#icinga2-api-clients-apps)
 
 Additional [programmatic examples](12-icinga2-api.md#icinga2-api-clients-programmatic-examples)
 will help you getting started using the Icinga 2 API in your environment.

diff --git a/doc/19-technical-concepts.md b/doc/19-technical-concepts.md
index 9ac1c0bced5720854373aae6d8ebbebda7069050..0b50715ad48ca29ca84c6a5a737a6ffb1b011def 100644 (file)
--- a/doc/19-technical-concepts.md
+++ b/doc/19-technical-concepts.md
@@ -594,27 +594,27 @@ support HA awareness, provide the `enable_ha` configuration attribute. When `ena
 is set to `true` (usually the default), "Run-Once" is set and the feature pauses on one side.
 
 ```
-vim /etc/icinga2/features-enabled/graphite.conf
+vim /etc/icinga2/features-enabled/ido-mysql.conf
 
-object GraphiteWriter "graphite" {
+object IdoMysqlConnection "ido-mysql" {
   ...
   enable_ha = true
 }
 ```
 
-Once such a feature is paused, there won't be any more event handling, e.g. the Elasticsearch
-feature won't process any checkresults nor write to the Elasticsearch REST API.
+Once such a feature is paused, there won't be any more event handling, e.g. the IDO MySQL
+feature won't write status and config updates anymore for this endpoint.
 
 When the cluster connection drops, the feature configuration object is updated with
 the new object authority by the ApiListener timer and resumes its operation. You can see
 that by grepping the log file for `resumed` and `paused`.
 
 ```
-[2018-10-24 13:28:28 +0200] information/GraphiteWriter: 'g-ha' paused.
+[2018-10-24 13:28:28 +0200] information/IdoMysqlConnection: 'ido-mysql' paused.
 ```
 
 ```
-[2018-10-24 13:28:28 +0200] information/GraphiteWriter: 'g-ha' resumed.
+[2018-10-24 13:28:28 +0200] information/IdoMysqlConnection: 'ido-mysql' resumed.
 ```
 
 Specific features with HA capabilities are explained below.