Update

Author: austinsonger

ADS-Framework.md

@@ -56,6 +56,6 @@ These are the general response steps in the event that this alert fired. These s
 # Additional Resources
 Additional Resources are any other internal, external, or technical references that may be useful for understanding the ADS.
 
-The title for this alerting strategy should be informative but succint, and should be targeting a singular event i.e "Non-SA Bastion Logon" rather than reference all events of this type ("Bastion Logons").
+The title for this alerting strategy should be informative but succinct, and should be targeting a singular event i.e "Non-SA Bastion Logon" rather than reference all events of this type ("Bastion Logons").
 
 The strategy should be stored under the Draft Alerting and Detection Strategies page while you're working on it, peer-reviewed, and a Like attached to the page when approved by a peer to move into production. 

Discovering-Risks.md

@@ -149,15 +149,15 @@ Right now you’re the only one who got anything from these interviews. You’ll
 The following are useful areas to organize your findings.
 
 #### 🔭 Scenarios
-A scenario is a concrete way to articulate a risk. Scenarios are undesireable future events. The deliverable has a list. The following examples may help you author them.
+A scenario is a concrete way to articulate a risk. Scenarios are undesirable future events. The deliverable has a list. The following examples may help you author them.
 
 This scenario includes an *impact* 💥:
 
 > An outage in `prod002`  violates customer SLA.
 
 This scenario includes a *vulnerability* 💔:
 
-> The RCE in our mobile app API is used to gain persistance on a server.
+> The RCE in our mobile app API is used to gain persistence on a server.
 
 This scenario includes a *threat* 👻: