Create spellcheck audit issues from line 143 - 149 of spreadsheet

[roslynwythe]

Overview

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

Action Items

• For each line 143 - 149 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 merge team"

Note for Dev Leads after issue sign-off

• 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 light-the-way.md #7783
• Run VS Code Spell Checker on lucky-parking.md #7784
• Run VS Code Spell Checker on metro-ontime.md #7785
• Run VS Code Spell Checker on new-schools-today.md #7786
• Run VS Code Spell Checker on not-today.md #7787
• Run VS Code Spell Checker on open-community-survey.md #7788
• Run VS Code Spell Checker on public-tree-map.md #7789

Footnotes

1. HfLA spelling audit spreadsheet ↩ ↩²

2. Spell check audit web page issue template ↩

[HackforLABot]

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

[DakuwoN]

Availability: Monday - Sunday 10AM to 6PM Central
ETA: Sunday December 1st, 2024

[t-will-gillis]

HI @DakuwoN I reviewed your issues- they look great. I am marking them as Ready for Prioritization and closing this issue as successfully completed. Thank you for working on this issue!

[DakuwoN]

Hey thank you @t-will-gillis no problem brother.