Create spellcheck audit issues from line 150 - 158 of spreadsheet

[roslynwythe]

Overview

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

Action Items

• For each line 150 - 158 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 spare.md #7804
• Run VS Code Spell Checker on tdm-calculator.md #7805
• Run VS Code Spell Checker on tech-work-experience.md #7806
• Run VS Code Spell Checker on undebate.md #7807
• Run VS Code Spell Checker on vrms.md #7808
• Run VS Code Spell Checker on website.md #7809
• Run VS Code Spell Checker on work-for-la.md #7810
• Run VS Code Spell Checker on writeforall.md #7811
• Run VS Code Spell Checker on youthjusticenav.md #7812

Footnotes

1. HfLA spelling audit spreadsheet ↩ ↩²

2. Spell check audit web page issue template ↩

[github-actions]

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