v5

Author: wojciech11

05_slides/README.md

@@ -12,15 +12,15 @@
 flowchart
  I(Incident) -. Well defined process .->l
  l(Incident\nCommander) --> H(Communication\n Manager)
- l --> D(Direct\nContributor)
+ l --> D(Direct\nContributor/s)
  l --> C(Communication\nChannel)
 ```
 
 Roles:
 
 - Incident Commander (IC) - "the commander holds all positions that they have not delegated. If appropriate, they can remove roadblocks that prevent Ops from working most effectively" ([sre book](https://www.atlassian.com/incident-management/incident-response/incident-commander#3-duties-of-an-incident-commander)).
 
-- Communication Manager (CM) - manages communications, periodics updates about the incident to the other teams, stakeholders, and clients (directly or indirectly). The communication could be done by email, slack, or a [statuspage](https://spacelift.statuspage.io).
+- Communication Manager (CM) - manages communications, periodically updates about the incident to the other teams, stakeholders, and clients (directly or indirectly). The communication could be done by email, slack, or a [statuspage](https://spacelift.statuspage.io).
 
 - Direct Contributor (DC) - a person or persons that works on solving the problem
 
@@ -29,8 +29,8 @@ Procedure:
 1. Alert -> OnCaller or person on duty become a IC
 2. IC creates a channel to coordinate the incident (a call, slack channel, etc.)
 3. IC names CM and DCs
-4. CM handles the external communication and stackholder management
-5. DCs works on the solution, ICs use his super powers to ensure we can resolve the indicent.
+4. CM handles the external communication and stakeholder management
+5. DCs works on the solution, ICs use his super powers to ensure we can resolve the incident.
 
 After: