Run VS Code Spell Checker on sdg2.yml

lukewangm commented 2 months 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 '_data/internal/sdg/sdg2.yml' and note any Code Spell Checker errors
[x] 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.
[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.

github-actions[bot] commented 1 month ago

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

blaycoder commented 1 month ago

Do let fellow developers know about your:- i. Availability: Today ii. ETA: Today

blaycoder commented 1 month ago

ii. ETA: Issue have been completed

t-will-gillis commented 4 weeks ago

Hi @blaycoder Please remember to work on only one issue at a time, and to work on issues of increasing complexity. It appears you have six issues open currently. Since you completed a Complexity: Small, your next issue should be a Complexity: Medium.

I am unassigning you from this issue.

github-actions[bot] commented 3 weeks ago

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

Limeload commented 3 weeks ago

i. Availability: 05/28 - 06/05 ii. ETA: 06/05

LRenDO commented 2 weeks ago

Hi @Limeload! Great job with this issue! It looks like there are no errors on this page on my end too! You also did a great job with moving the issue to the right column. Next time be sure to add the ready for dev lead label as well. Thanks for contributing to this epic!

hackforla / website