More tidying, mostly spellcheck stuff

.cspell.json

@@ -0,0 +1,56 @@
+{
+  "version": "0.2",
+  "language": "en_US",
+  "ignorePaths": [
+    "node_modules/**",
+    "styles.**"
+  ],
+  "words": [
+    "Allstar",
+    "sidenav",
+    "telework",
+    "USAJOBS",
+    "captioner",
+    "neurodiversity",
+    "socio",
+    "jointts",
+    "FASC",
+    "LUOTR",
+    "SYSANALYSIS",
+    "ohrm",
+    "endunless",
+    "skillset",
+    "skillsets",
+    "skinless",
+    "wireframe",
+    "wireframes",
+    "toolkit",
+    "toolkits",
+    "OPM",
+    "refactorization",
+    "USWDS",
+    "uswds",
+    "subnav",
+    "endfor",
+    "USDA",
+    "usda",
+    "exfiltrate",
+    "browsersync",
+    "outdir",
+    "Snyk",
+    "sitrep",
+    "ISSO",
+    "SDLC",
+    "automations",
+    "ISSM",
+    "timeframe",
+    "pdate",
+    "sitreps",
+    "Joomla",
+    "dependency",
+    "Grype",
+    "dependencies",
+    "hotfixes",
+    "Nygard"
+  ]
+}

.mega-linter.yml

@@ -14,8 +14,8 @@ DISABLE_LINTERS:
   [
     REPOSITORY_DEVSKIM,
     SPELL_MISSPELL,
-    SPELL_CSPELL,
     SPELL_PROSELINT,
+    SPELL_LYCHEE,
     COPYPASTE_JSCPD,
     BASH_EXEC,
   ]
@@ -52,3 +52,9 @@ BASH_SHFMT_ARGUMENTS: -i 2 -bn -ci -sr -kp
 REPOSITORY_TRUFFLEHOG_ARGUMENTS: "--exclude-paths=.trufflehogignore"
 
 YAML_V8R_FILTER_REGEX_EXCLUDE: ".*_data.*"
+
+SPELL_CSPELL_ANALYZE_FILE_NAMES: false
+SPELL_CSPELL_FILE_EXTENSIONS:
+  - ".md"
+
+CLEAR_REPORT_FOLDER: true

.trufflehogignore

@@ -1 +1,2 @@
 .git
+node_modules/

docs/CM.md

@@ -19,7 +19,7 @@ site:
         - NetlifyCMS
     testing-suites:
         - Codeql
-        - Synk
+        - Snyk
         - Dependabot
 
 ---
@@ -81,4 +81,4 @@ Steps taken from a Pull Request for any change to application within our Product
   - That PR is then run in continuous integration (CI) server to ensure they are valid and pass all applied testing and ansible playbook verification/test runs. If checks pass and a developer peer reviews and approves the Pull Request it can be merged into the "main" branch.
   - All changes are deployed from the develop branch to staging environment, and automated or manual tests and/or verifications are run to ensure intended changes are applied correctly.
   - Proposed changes are then discussed, any uptime concerns or timing preferences on deployment to production are communicated.
-  - If there is agreement to proceed between 2 or more members then changes are applied to production, followed by active monitoring and logging to ensure there are no issues after deployment. If there are, changes can be reverted to the previous state.
+  - If there is agreement to proceed between 2 or more members then changes are applied to production, followed by active monitoring and logging to ensure there are no issues after deployment. If there are, changes can be reverted to the previous state.

docs/IR.md

@@ -27,11 +27,11 @@ site:
 Whoever acts on an alert/email/etc would follow this process. You are now the Incident Commander (IC).
 
 1. `Acknowledge` the alert if available e.g. New Relic, Email, Github, etc.
-1. Open an Issue/Ticket/Card/etc in the team's project manangement tool with incident information. Copy the link to it and use it to document the `Incident` in real-time.
+1. Open an Issue/Ticket/Card/etc in the team's project management tool with incident information. Copy the link to it and use it to document the `Incident` in real-time.
   - This team uses: `{{ site.project-management-tool }}`
 3. Notify the team - use the team's Google Group email or Slack `@channel` with a link to the `Incident` in the project management tool.
     - Acknowledge your role as the `Incident Commander` e.g. "Looking into this". Use a Slack thread to communicate updates within the team.
-1. Request assistance from specfic teammates to pair with if needed. Others teammates should acknowledge, verify, and offer support in the Slack thread. 
+1. Request assistance from specific teammates to pair with if needed. Others teammates should acknowledge, verify, and offer support in the Slack thread. 
 6. If the site is down, email the team ([ {{ site.google-group-email }}](mailto:{{ site.google-group-email }})).
 7. If this is a **Security Incident** , follow the [TTS Incident Response guide](https://handbook.18f.gov/security-incidents/#reporting-other-incidents), CCing [{{ site.google-group-email }}](mailto:{{ site.google-group-email }}) in the loop.
 1. Assign and delegate tasks to person(s) most technically capable to resolve `Incident`.

docs/architecture/decisions/0002-use-a-static-site-architecture.md

@@ -8,7 +8,7 @@ Accepted
 
 ## Context
 
-This decision was proposed in the context of Technoloy Transformation Services wanting a platform to host both current and future webpages at a single domain. We see the benefits of a static site architecture as:
+This decision was proposed in the context of Technology Transformation Services wanting a platform to host both current and future webpages at a single domain. We see the benefits of a static site architecture as:
 
 * Reduced infrastructure costs
 * Opportunities to add enhancements in the future
@@ -23,7 +23,7 @@ We propose using a static site architecture for tts.gsa.gov.
 We predict that using a static site architecture will:
 
 * Allow TTS to easily meet any high traffic needs
-* Reduce the cost, pain, and delays of maintaining infrastructure in comparison with a more complicated CMS (Wordpress, Drupal, Joomla) architecure
+* Reduce the cost, pain, and delays of maintaining infrastructure in comparison with a more complicated CMS (Wordpress, Drupal, Joomla) architecture
 * Improved security by presenting a reduced attack surface
 
 ## Alternatives
@@ -38,7 +38,7 @@ However, using one of these CMS tools would require us to run a server, which wo
 
 As of Jan 2022, Federalist supports a variety of static site solutions such as Jekyll, Gatsby, and Hugo.
 
-We chose Eleventy because of its flexability and for the large amount of JavaScript knowledge across TTS. Although Eleventy is newer, it's gaining adoption quickly and as this project matures there will be more and more examples and plugins to make use of.
+We chose Eleventy because of its flexibility and for the large amount of JavaScript knowledge across TTS. Although Eleventy is newer, it's gaining adoption quickly and as this project matures there will be more and more examples and plugins to make use of.
 
 ### Federalist