Run VS Code Spell Checker on home-unite-us.md

santisecco commented 1 month ago

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[^1] and will be resolved in later issues.

Action Items

[x] You must use VS Code as your local text editor and install the Code Spell Checker VS Code extension[^2]
[x] Do not change any configuration settings or make any spell corrections
[x] Open the file '[_projects/home-unite-us.md' and note any Code Spell Checker errors
[x] Locate the file in column A (named "Filepath") of the "Page Audit" sheet. In the column labeled "Result Summary", select the appropriate option: No errors or At least one error.
[x] If at least one error was reported, copy/paste each cSpell message into a separate row in the Results sheet
[x] 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).
[x] Move this issue to the Questions/In Review column and apply the label ready for dev lead

Merge Team

[x] After this issue is closed, release the dependency on this issue in #5248
[ ] After the last dependency has been released, close that issue

Resources/Instructions

This issue is part of #5248 [^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.

HackforLABot commented 1 month ago

Hello @k-cardon, we appreciate you taking on issue #7456, however it looks like you've already worked on enough issues of this complexity. Try checking out some of the issues of the next complexity from the Prioritized Backlog :)

We are going to unassign you from this issue so you can take on another issue.

Hfla appreciates you! :)

P.S. There is one exception to this rule/automation, and that is if you were away for a long time, and need to do the issue ladder again. If that is the case, please post the following note on the issue and on your Skills Issue (Pre-work Checklist). A Merge team member will reassign you to this issue, and will help you get assigned to subsequent issues up to medium size.

I am returning after a significant time away, and need to do the issue ladder again. Please assign me back to this issue.

HackforLABot commented 3 weeks ago

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

siyunfeng commented 3 weeks ago

Availability: 6:00 PM - 10:00 PM, Weekdays (EDT) ETA: Sat, 10/19/2024

siyunfeng commented 3 weeks ago

Hi @santisecco , I have completed every step in Action Items.

cSpell Results:

"pdfs": Unknown word [In 129] - (False Positive)
"wireframes": Unknown word [In 134] - (False Positive)
"OIDC": Unknown word [In 145] - (False Positive)

Do I still need to submit a PR since it wasn't required to change anything in the _projects/home-unite-us.md file?

t-will-gillis commented 3 weeks ago

Hi @siyunfeng No, you do not need to submit a PR- we will review this and get back to you. Thank you!

santisecco commented 3 weeks ago

@siyunfeng check Will's comment, I believe merge team will review your work but from what I can see everything seems correct.

t-will-gillis commented 3 weeks ago

Hey @siyunfeng Looks good- You noted that at least one error was found on the "Page Audit" sheet, and listed the three words that were flagged on the "Results" page.

Great job and thank you for working on this epic. I am closing this issue as successfully completed.

hackforla / website