Run VS Code Spell Checker on vote-representation-card.yml #6572
Closed
7 of 9 tasks
Labels
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
feature: spelling
ready for dev lead
Issues that tech leads or merge team members need to follow up on
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 0.5pt
Can be done in 3 hours or less
Milestone
Overview
We need to audit HfLA codebase files for spelling errors using the Code Spell Checker extension in VS Code in order to ensure site quality. Results will be categorized as misspellings or false positives in the HfLA spelling audit spreadsheet1 and will be resolved in later issues.
Action Items
Code Spell Checker
VS Code extension2No errors
orAt least one error
.Results
sheetmisspelling
orfalse positive
from the "Result type" column. A false positive is a term that is not a misspelling but is not recognized by the spell checker because it is a technical term, abbreviation, acronym, URL or proper noun (name of a person, place or organization).ready for dev lead
Merge Team
Resources/Instructions
Footnotes
HfLA spelling audit spreadsheet - Results ↩
The recommended installation method is to install Code Spell Checker directly from the VS Code text editor, and those instructions can be found here. The extension can also be installed via the VS Code Marketplace website here. ↩
The text was updated successfully, but these errors were encountered: