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>
This commit is contained in:
Brendan Jurd 2016-10-14 16:33:53 +11:00 committed by Jean Flach
parent 616bcd1440
commit 4b18d67587
1 changed files with 2 additions and 2 deletions

View File

@ -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