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 db27d3ac5e5a470d96b20bed3904ca16fb3a81d2..7e32e8843f5acf5e43a9a73b9e413329cf68595c 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 69efb47f23543018c6fbca15e68921b0d1eaaccc..fefcd9bd9099d6705c37857600a02131e9b1ef93 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.