Documentation: Move configuration before advanced topics

[icinga2] / doc / 5-advanced-topics.md

diff --git a/doc/4-advanced-topics.md b/doc/5-advanced-topics.md
similarity index 99%
rename from doc/4-advanced-topics.md
rename to doc/5-advanced-topics.md
index b12d495ec2a7e72cc33329b6470bfffee8d55ea5..34effc4e0352db97e0c435bfe769454716b32bdb 100644 (file)
--- a/doc/4-advanced-topics.md
+++ b/doc/5-advanced-topics.md
@@ -53,7 +53,7 @@ is removed (may happen before or after the actual end time!).
 
 ### <a id="scheduling-downtime"></a> Scheduling a downtime
 
-This can either happen through a web interface or by sending an [external command](4-advanced-topics.md#external-commands)
+This can either happen through a web interface or by sending an [external command](5-advanced-topics.md#external-commands)
 to the external command pipe provided by the `ExternalCommandListener` configuration.
 
 Fixed downtimes require a start and end time (a duration will be ignored).
@@ -462,7 +462,7 @@ You can customize the metric prefix name by using the `host_name_template` and
 
 The example below uses [runtime macros](3-monitoring-basics.md#runtime-macros) and a
 [global constant](19-language-reference.md#constants) named `GraphiteEnv`. The constant name
-is freely definable and should be put in the [constants.conf](5-configuring-icinga-2.md#constants-conf) file.
+is freely definable and should be put in the [constants.conf](4-configuring-icinga-2.md#constants-conf) file.
 
     const GraphiteEnv = "icinga.env1"