diff --git a/docs/checks/azure/database/threat-alert-email-set/index.md b/docs/checks/azure/database/threat-alert-email-set/index.md index b2d8f01049..c972ed745d 100644 --- a/docs/checks/azure/database/threat-alert-email-set/index.md +++ b/docs/checks/azure/database/threat-alert-email-set/index.md @@ -11,7 +11,7 @@ title: At least one email address is set for threat alerts SQL Server sends alerts for threat detection via email, if there are no email addresses set then mitigation will be delayed. ### Possible Impact -Nobody will be prompty alerted in the case of a threat being detected +Nobody will be promptly alerted in the case of a threat being detected ### Suggested Resolution Provide at least one email address for threat alerts diff --git a/docs/guides/trivy.md b/docs/guides/trivy.md index f91a82ebb2..d702ca9b38 100644 --- a/docs/guides/trivy.md +++ b/docs/guides/trivy.md @@ -1,5 +1,5 @@ # Moving towards configuration scanning with Trivy -Overtime we've taken [trivy][trivy] to be the go-to scanning tool for a vareity of things. This also includes terraform scanning. +Overtime we've taken [trivy][trivy] to be the go-to scanning tool for a variety of things. This also includes terraform scanning. This section describes some differences between Trivy and tfsec. @@ -44,4 +44,4 @@ $ tfsec