Create spellcheck audit issues from line 126 - 133 of spreadsheet

[roslynwythe]

Overview

We need to create issues for the spellcheck audit. The filepaths for the required issues are found in lines 126 - 133 of the HfLA spelling audit spreadsheet¹

Action Items

• For each line 126 - 133 in the HfLA spelling audit spreadsheet¹
  • Copy the filepath (for example pages/toolkit.html) from column A then create a new issue using the "Spell check audit web page template"²
  • Replace the text [INSERT FILE HERE] with the filename (for example toolkit.html)
  • Replace the text [INSERT FILE PATH] with the full file path (for example pages/toolkit.html)
  • Click "Submit New Issue"
  • Copy the issue number and use it to create a link below under "Child Issues that this issue creates" (for example if you enter - [ ] #6497, GitHub will expand that into an issue link
  • Copy the issue number and paste it into the "Link to Audit Issue" column in the spreadsheet in the row that corresponds to the filepath
• When all issues have been created, move this issue into the "Questions/In Review" column and add the label "ready for dev lead"

Note for Dev Leads after issue signoff

• Add all the issues created by this issue to the Epic Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

Resources/Instructions

• This issue is part of Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

Child Issues that this issue creates

• Run VS Code Spell Checker on toc.html #7393
• Run VS Code Spell Checker on donate-gif-text.html #7394
• Run VS Code Spell Checker on donation-circles.html #7395
• Run VS Code Spell Checker on in-kind.html #7396
• Run VS Code Spell Checker on header-container-content.html #7397
• Run VS Code Spell Checker on left-col-content.html #7398
• Run VS Code Spell Checker on our-locations-content.html #7399
• Run VS Code Spell Checker on social.html #7400

Footnotes

1. HfLA spelling audit spreadsheet ↩ ↩²

2. Spell check audit web page issue template ↩

[HackforLABot]

Hi @codyyjxn, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[codyyjxn]

i. Availability: M > F
ii. ETA: Done

[roslynwythe]

Thank you @codyyjxn for creating these issues.