From 3105f4c4182b327a9a8ddc7c8d27bf5ef17d3723 Mon Sep 17 00:00:00 2001
From: Denis <zaharden@gmail.com>
Date: Sun, 2 Jul 2017 03:58:37 +0700
Subject: [PATCH] Fix typo in the documentation

---
 doc/05-service-monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/05-service-monitoring.md b/doc/05-service-monitoring.md
index 3fd2cc6af..6cf8d700f 100644
--- a/doc/05-service-monitoring.md
+++ b/doc/05-service-monitoring.md
@@ -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).