Run VS Code Spell Checker on vote-representation-card.yml

[terrencejihoonjung]

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 spreadsheet¹ and will be resolved in later issues.

Action Items

• You must use VS Code as your local text editor and install the Code Spell Checker VS Code extension²
• Do not change any configuration settings or make any spell corrections
• Open the file '_program-areas/vote-representation-card.yml' and note any Code Spell Checker errors
• Locate the file in column A ("File") of the "Page Audit" sheet. In the column labeled "Result Summary", select the appropriate option: No errors or At least one error.
• If at least one error was reported, copy/paste each cSpell message into a separate row in the Results sheet
• In each new row, select the appropriate value: misspelling or false 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).
• Move this issue to the Questions/In Review column and apply the label ready for dev lead

Merge Team

• After this issue is closed, release the dependency on this issue in Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248
• After the last dependency has been released, close that issue

Resources/Instructions

• This issue is part of Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

Footnotes

1. HfLA spelling audit spreadsheet - Results ↩

2. 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. ↩

[ExperimentsInHonesty]

This has not been reviewed by a merge team member. It need to be confirmed that the two errors the assignee found are the only errors for this page.

[daras-cu]

@ExperimentsInHonesty I believe this issue was a duplicate of this completed issue:

• Run VS Code Spell Checker on vote-representation-card.yml #6572

@terrencejihoonjung noticed there was already a spellcheck issue for vote-representation-card.yml after creating this one, see comment on 6872. There was one other file he noticed also already had an issue created.

I am trying to figure out how the same file ended up on two IMs for spellcheck issues.

• Create spellcheck audit issues from line 119-125 of spreadsheet #6872 is the IM this issue originated from, and Create spellcheck audit issues from line 81-90 of spreadsheet #6499 is the originator of the previous issue. Is it possible the order of the spellcheck audit spreadsheet changed at some point?
• Also, theoretically Create spellcheck audit issues from line 119-125 of spreadsheet #6872 is part of Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248, but it is not on the dependency list. We may need to go back through the spreadsheet and related issues to check if there are other duplicates or files that have been missed. I can look further into it once I wrap up my wins issue if you'd like.

[t-will-gillis]

Hi @daras-cu ( and @ExperimentsInHonesty )-

• I noticed that there were many duplicates also. I have been clicking "Close as not planned" (duplicate). I will go ahead and close this as a duplicate.
• About the line numbering- yes, I think that there have been insertions and moves that have screwed up the line number references. I marked several lines as "this is a duplicate" but left the line in the file so the line numbering would not get worse.