Create spellcheck audit issues from line 118-125 of spreadsheet

[roslynwythe]

Overview

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

Action Items

• For each line 118-125 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 hamburger-nav.html #7386
• Run VS Code Spell Checker on head.html #7387
• Run VS Code Spell Checker on header.html #7388
• Run VS Code Spell Checker on hero.html #7389
• Run VS Code Spell Checker on home-getting-started.html #7390
• Run VS Code Spell Checker on join-donate-card.html #7391
• Run VS Code Spell Checker on main-nav.html #7392

Footnotes

1. HfLA spelling audit spreadsheet ↩ ↩²

2. Spell check audit web page issue template ↩

[HackforLABot]

Hi @k-cardon, 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 :)

[k-cardon]

Availability: after 8pm or weekends usually
ETA: should be complete by the end of the week

Provide Update

1. Progress: have access to Google drive so can begin to work on this now!
2. Blockers: none at present
3. Availability: some right now, usually evenings and weekends
4. ETA: end of week

[k-cardon]

Please note that item 125 from the spelling audit spreadsheet was already completed by #5597 last year.

[k-cardon]

Provide Update

1. Progress: complete
2. Blockers: waiting for approval
3. Availability: n/a
4. ETA: n/a

[roslynwythe]

Thank you @k-cardon for creating these small issues