From 22dcd0fb3e5bc261c30fd92d24f3519a1f481951 Mon Sep 17 00:00:00 2001
From: Daniel Sevostyanov <12199206+SevDan@users.noreply.github.com>
Date: Wed, 17 Mar 2021 21:57:11 +0400
Subject: [PATCH] #1 Typo 'Messanger' -> 'Messenger'

---
 ...common-development-and-operations-01-incomplete-000001.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt b/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
index b582811..2f0752a 100644
--- a/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
+++ b/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
@@ -109,7 +109,7 @@ D. Common Topics
 	2.3. Cloud Providers
 	2.4. Vendor Locking
 3. Team Tools & Software
-	3.1. Messangers
+	3.1. Messengers
 	3.2. Project & Product Management
 	3.3. Bug Reporting
 	3.4. TMS
@@ -232,7 +232,7 @@ The second behavior of monitoring is alerting.
 You should push important (and only important!) alerts to your developers/operations/management when fatal troubles happens.
 
 You can automate it with your corporate messangers (with bots API), emails and SMS-services. 
-Messangers are good and enought for most cases.
+Messengers are good and enought for most cases.
 
 2.3 Reliability Engineering