Fix bad heading level for {commands,groups}.conf

The heading levels for commands.conf and groups.conf were incorrect.  They should have been at level 4, underneath "4.2.3 The conf.d directory", but instead they were at level 3.

fixes #12933

Signed-off-by: Jean Flach <jean-marcel.flach@icinga.com>

diff --git a/doc/4-configuring-icinga-2.md b/doc/4-configuring-icinga-2.md
index 9e455fa3fb649e388c9866db30a48c93a14cfe73..5a54bd919e0e52cc18b1549565b417e61d51b4a4 100644 (file)
--- a/doc/4-configuring-icinga-2.md
+++ b/doc/4-configuring-icinga-2.md
@@ -523,7 +523,7 @@ implicitely use the `icingaadmins` UserGroup defined in [users.conf](4-configuri
 More details on defining notifications and their additional attributes such as
 filters can be read in [this chapter](3-monitoring-basics.md#notifications).
 
-### <a id="commands-conf"></a> commands.conf
+#### <a id="commands-conf"></a> commands.conf
 
 This is the place where your own command configuration can be defined. By default
 only the notification commands used by the notification templates defined in [templates.conf](4-configuring-icinga-2.md#templates-conf).
@@ -531,7 +531,7 @@ only the notification commands used by the notification templates defined in [te
 You can freely customize these notification commands, and adapt them for your needs.
 Read more on that topic [here](3-monitoring-basics.md#notification-commands).
 
-### <a id="groups-conf"></a> groups.conf
+#### <a id="groups-conf"></a> groups.conf
 
 The example host defined in [hosts.conf](hosts-conf) already has the
 custom attribute `os` set to `Linux` and is therefore automatically