Documentation: Fix typo in Configuration Best Practice

fixes #9268

Signed-off-by: Michael Friedrich <michael.friedrich@gmail.com>

diff --git a/AUTHORS b/AUTHORS
index 1086aa4a1b760e58c7bb2b3383cf6500ed026b6f..591d3bb8e512419b0ccb3a50c447ab9a010f6196 100644 (file)
--- a/AUTHORS
+++ b/AUTHORS
@@ -1,3 +1,4 @@
+Alexander A. Klimov <alexander.klimov@netways.de>
 Alexander Schomburg <script.acc@alex.schomb.org>
 Alexander Wirt <formorer@debian.org>
 Andrew Meyer <ameyer+secure@nodnetwork.org>

diff --git a/doc/5-configuring-icinga-2.md b/doc/5-configuring-icinga-2.md
index cbd3d8b25a1f90b8af34817683297888b074f4f6..f8e955d623f0086369440b042393b883e5375b59 100644 (file)
--- a/doc/5-configuring-icinga-2.md
+++ b/doc/5-configuring-icinga-2.md
@@ -17,7 +17,7 @@ decide for a possible strategy.
 There are many ways of creating Icinga 2 configuration objects:
 
 * Manually with your preferred editor, for example vi(m), nano, notepad, etc.
-* Generated by a [configuration management too](13-addons-plugins.md#configuration-tools) such as Puppet, Chef, Ansible, etc.
+* Generated by a [configuration management tool](13-addons-plugins.md#configuration-tools) such as Puppet, Chef, Ansible, etc.
 * A configuration addon for Icinga 2
 * A custom exporter script from your CMDB or inventory tool
 * your own.