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[^1]

Action Items

• [ ] For each line 143 - 149 in the HfLA spelling audit spreadsheet[^1]
  • [ ] Copy the filepath (for example pages/toolkit.html) from column A then create a new issue using the "Spell check audit web page template"[^2]
  • [ ] 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 #5248

Resources/Instructions

• This issue is part of #5248 [^1]:HfLA spelling audit spreadsheet [^2]:Spell check audit web page issue template

Child Issues that this issue creates

• [ ] #

[github-actions[bot]]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[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.