Epic: Website Spelling Checks and Structure

### Dependency
- #1146
- #2206
- #2404
- #2492

### Overview
We need to spell check the website, both manual and automated, before handoff so that we are handing off a quality product and preparing them for future development.

### Action Items
- [x] Create three issues for the phases of spell checking
- [ ] Add a `ready for product` label once issues are sub issues are closed and see if we have achieved the objective or do more issues need to get made
- [ ] add a bullet list to the slide that communicates to the stakeholders what we did.

### Resources/Instructions
- This link of GHAs that do spell checks might help: https://github.com/marketplace?type=&verification=&query=spell
- Issue from HfLA website team on same: https://github.com/hackforla/website/issues/3546
- [Bonnie's Query for spell checkers](https://github.com/marketplace?type=&verification=&query=spell)
- Suggestion of a specific spell checker (provided by Fang) [eslint-plugin-spellcheck](https://github.com/aotaduy/eslint-plugin-spellcheck)

#### Slides
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg)
- [Staging Deck, slide 413](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit#slide=id.g33fd44e1e89_2_30)
- Release Deck
- [YYYY-MM-DD Release Deck, slide 413]