Update 08-advanced-topics.md

[icinga2] / doc / 05-service-monitoring.md

diff --git a/doc/05-service-monitoring.md b/doc/05-service-monitoring.md
index 3fd2cc6afbe318526cc3dd23ff8399325a3f8e80..855b75b53e788802edade8444930782d2e711a3e 100644 (file)
--- a/doc/05-service-monitoring.md
+++ b/doc/05-service-monitoring.md
@@ -49,7 +49,7 @@ configuration which can be used in the [Service](09-object-types.md#objecttype-s
 [Host](09-object-types.md#objecttype-host) object definition.
 
 Please check if the Icinga 2 package already provides an
-[existing CheckCommand definition](10-icinga-template-library.md#plugin-check-commands).
+[existing CheckCommand definition](10-icinga-template-library.md#icinga-template-library).
 If that's the case, throroughly check the required parameters and integrate the check command
 into your host and service objects.
 
@@ -115,7 +115,7 @@ exist.
 
 Common best practices when creating a new plugin are for example:
 
-* Choose the pragramming language wisely
+* Choose the programming language wisely
  * Scripting languages (Bash, Python, Perl, Ruby, PHP, etc.) are easier to write and setup but their check execution might take longer (invoking the script interpreter as overhead, etc.).
  * Plugins written in C/C++, Go, etc. improve check execution time but may generate an overhead with installation and packaging.
 * Use a modern VCS such as Git for developing the plugin (e.g. share your plugin on GitHub).