chore: pre-commit

Author: esacteksab

docs/developing/code-reviews/README.md

@@ -7,7 +7,7 @@ gaining valuable feedback from peers, ensuring that quality standards are upheld
 throughout a project, and defects are caught as early as possible.
 
 We recognize code reviews can be a vulnerable exercise and should be approached
-with care and deliberate intention.  We've collected some of the best practices
+with care and deliberate intention. We've collected some of the best practices
 for projects to systematize the code review process and lay out expectations for
 the creator of the pull request as well as the role of the reviewer.
 

docs/developing/command-line-tools/docker.md

@@ -3,7 +3,7 @@
 ## Overview
 
 Docker is useful because it allows you to both package and run
-software with all its dependencies and configuration in isolation.  It
+software with all its dependencies and configuration in isolation. It
 also allows you (in theory) to have the same environment in
 development as in CI and production.
 
@@ -18,9 +18,9 @@ brew cask install docker
 ### Configuration of Shared Folders
 
 Anecdata suggests that removing some of the default shared folders can
-decrease CPU usage.  Usually you only need to share volumes under your
-home directory.  Open the docker for mac preferences, then select
-"File Sharing" and then remove `/Volumes` and `/private`.  You may
+decrease CPU usage. Usually you only need to share volumes under your
+home directory. Open the docker for mac preferences, then select
+"File Sharing" and then remove `/Volumes` and `/private`. You may
 also find improvements removing `/Users` and replacing it with
 `/Users/YOUR_USERNAME_GOES_HERE`.
 
@@ -36,13 +36,13 @@ Storage Driver: overlay2
 
 If you don't see overlay2, upgrading to the latest version will add
 that support, but you would need to recreate all of your docker data
-to utilize it.  The `Reset` bomb should do it.
+to utilize it. The `Reset` bomb should do it.
 
 ### Configuration of Disk Image
 
 If you've been running Docker for Mac for some time, make sure you are
-using the `raw` disk image format and not `qcow2`.  Open Docker for
-Mac preferences and select `Disk`.  Make sure the image ends with
+using the `raw` disk image format and not `qcow2`. Open Docker for
+Mac preferences and select `Disk`. Make sure the image ends with
 `Docker.raw`.
 
 ### Configuration of Resources
@@ -59,7 +59,7 @@ by the docker developers.
 ## Volume Mount Performance
 
 Synchronizing the data between the host (your Mac) and the container
-can be resource intensive and/or slow.  Read about the [performance
+can be resource intensive and/or slow. Read about the [performance
 tuning options](https://docs.docker.com/docker-for-mac/osxfs-caching/)
 to see if they might apply to the conditions in your project.
 

docs/developing/growth/README.md

@@ -13,7 +13,7 @@ speeding up tests) and the client getting the benefit of learning that
 happened elsewhere. Allowing time for growth ensures consistent, high
 quality work which benefits everyone.
 
-Mentoring is an important part of growth.  Truss has [shared some
+Mentoring is an important part of growth. Truss has [shared some
 techniques for
 mentoring](https://truss.works/blog/2016/8/12/theres-a-method-to-the-mentoring-advice-from-a-teacher-turned-developer).
 
@@ -23,6 +23,6 @@ restrict exploration and "just get the ticket done", but that should
 happen infrequently.
 
 If someone is interested in a topic that is not related to their
-client work, a separate plan will need to be made.  That might involve
+client work, a separate plan will need to be made. That might involve
 changing client teams, changing client projects, or joining Truss
 Reserve.

docs/developing/vcs/tools.md

@@ -48,7 +48,7 @@ for merge conflicts or mistakenly adding secret keys in our code. See
 pre-commit config file from one of our projects.
 
 Since git does not distribute hooks when a repository is cloned, you will
-have to install pre-commit in each cloned repo manually using `pre-commit install --install-hooks` or pre-commit will not run in that repo.  To assist
+have to install pre-commit in each cloned repo manually using `pre-commit install --install-hooks` or pre-commit will not run in that repo. To assist
 with automating this step, pre-commit has a [feature] to exploit the
 [template directory] setting in git:
 

docs/incident-response/on-call.md

@@ -87,7 +87,7 @@ you are expected to fulfill.
   have this covered.
 - If you know you will be away for an extended period during an on-call
   shift, it is *your* responsibility to find someone to cover your shift.
-  If you are unable to, talk to your lead and see if they can help.  If
+  If you are unable to, talk to your lead and see if they can help. If
   you will be gone for more than a day or two, it may be easiest to swap
   the entire shift with someone. PagerDuty allows you to schedule these
   with [overrides](https://community.pagerduty.com/t/creating-a-schedule-override/850).

docs/incident-response/security-incidents.md

@@ -10,4 +10,4 @@ to navigate. This document will outline how to approach security
 incidents in general; individual projects will likely have additional
 reporting requirements based on client needs.
 
-\[This is a stub and needs to be expanded.\]
+[This is a stub and needs to be expanded.]

docs/infrasec/alert-providers.md

@@ -89,6 +89,6 @@ it's merited).
 | API                        | Yes ([Documentation](https://docs.opsgenie.com/docs/api-overview))            | Yes ([Documentation](https://v2.developer.pagerduty.com/))              | Yes ([Documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide/)) |
 | Cloudwatch Integration     | Yes                                                                           | Yes                                                                     | Yes                                                                                               |
 | Slack Integration          | Yes                                                                           | Yes                                                                     | Yes                                                                                               |
-| Other Notable Integrations | CircleCI,  Jira, New Relic, StatusPage                                        | Jira, New Relic, Statuspage                                             | Jira, New Relic, Statuspage                                                                       |
+| Other Notable Integrations | CircleCI, Jira, New Relic, StatusPage                                         | Jira, New Relic, Statuspage                                             | Jira, New Relic, Statuspage                                                                       |
 | Data Retention             | 1 year (unlimited at $29)                                                     | Unlimited                                                               | Not listed (but unlimited noted at $49)                                                           |
 | Terraform Provider         | No ([abandoned](https://www.terraform.io/docs/providers/opsgenie/index.html)) | [Yes](https://www.terraform.io/docs/providers/pagerduty/index.html)     | No official provider, some limited attempts                                                       |

docs/infrasec/ansible/molecule-primer.md

@@ -22,8 +22,8 @@ anyway. Using Python 3 as the Python binary is also highly recommended. In addit
 will need these Python modules as well:
 
 - molecule
-- molecule\[docker\] - For testing with docker containers (the default)
-- molecule\[ec2\] - For testing on ec2 instances
+- molecule[docker] - For testing with docker containers (the default)
+- molecule[ec2] - For testing on ec2 instances
 - docker-py
 - boto
 

docs/infrasec/aws/aws-organizations.md

@@ -1,7 +1,7 @@
 # AWS Organizations
 
 [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html)
-provide a native way to manage multiple AWS accounts.  They provide
+provide a native way to manage multiple AWS accounts. They provide
 consolidated billing, APIs (e.g., via Terraform) for automating account
 creation, and the ability to apply account-wide IAM like policies.
 

docs/infrasec/aws/sns-guardduty-alert-integrations.md

@@ -286,7 +286,7 @@ resource "pagerduty_extension" "slack-v2-service" {
 }
 ```
 
-You're not quite done yet. PagerDuty does not actually authorize the link between the extension and Slack until you manually create it. Sign into PagerDuty and [visit the extensions page](https://movemil.pagerduty.com/extensions). Locate your new extension in the Service Extensions table and click on the gear button on the bottom right of the far-right Details cell for your extension. Select either the Re-authorize/Authorize or Edit option (they do the same thing) from the drop-down. Scroll down and select the channel you prefer under `Where should PagerDuty post?` then click "Allow". You should see a notification appear in the channel you've selected in Slack that says "\[your name\] added an integration to this channel: PagerDuty". Make sure to record that you've done this in your Manual Operations log. Note: You only need to create one extension per service rather than per environment.
+You're not quite done yet. PagerDuty does not actually authorize the link between the extension and Slack until you manually create it. Sign into PagerDuty and [visit the extensions page](https://movemil.pagerduty.com/extensions). Locate your new extension in the Service Extensions table and click on the gear button on the bottom right of the far-right Details cell for your extension. Select either the Re-authorize/Authorize or Edit option (they do the same thing) from the drop-down. Scroll down and select the channel you prefer under `Where should PagerDuty post?` then click "Allow". You should see a notification appear in the channel you've selected in Slack that says "[your name] added an integration to this channel: PagerDuty". Make sure to record that you've done this in your Manual Operations log. Note: You only need to create one extension per service rather than per environment.
 
 ## GuardDuty Tie-In
 
@@ -323,4 +323,4 @@ When an alert occurs and you are notified via PagerDuty or Slack, you'll have to
 
 1. Immediately Acknowledge the finding, which you can do via the PagerDuty app, website, or Slack integration.
 1. Once you've found a resolution for the incident, you should Resolve it (which again you can do via app, site, or on Slack).
-1. Archive the relevant GuardDuty finding using the AWS Console. Because you've set your `infrasec` as the administrative account for GuardDuty, all  findings for member accounts "roll up" there. Depending on whether the alerts are in the GovCloud or Commercial space, that will be either the `project-com-infrasec` or `project-gov-infrasec` account. Make sure you are in the correct region (either `us-west-2` or `us-east-1`, depending on where the alert fired). Confirm the alert you are archiving fired in the account you expected by checking the `Account ID` column in the Findings table.
+1. Archive the relevant GuardDuty finding using the AWS Console. Because you've set your `infrasec` as the administrative account for GuardDuty, all findings for member accounts "roll up" there. Depending on whether the alerts are in the GovCloud or Commercial space, that will be either the `project-com-infrasec` or `project-gov-infrasec` account. Make sure you are in the correct region (either `us-west-2` or `us-east-1`, depending on where the alert fired). Confirm the alert you are archiving fired in the account you expected by checking the `Account ID` column in the Findings table.