Run VS Code Spell Checker on _data/internal/privacy-policy.yml

[roslynwythe]

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 '_data/internal/privacy-policy.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. For developers who do not use VS Code, use the corresponding npm package, cspell. Those instructions can be found at https://www.npmjs.com/package/cspell ↩

[github-actions]

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]

Do let fellow developers know about your:-
i. Availability: 8PM - 12AM WAT
ii. ETA: Issue will completed as soon the issue is closed. All the action items have been checked and taken

[LRenDO]

Hi @blaycoder! It looks like you found the same errors that I see on my end. I have one small request. Please copy the file path _data/internal/privacy_policy.yml onto line 103 column A as well. When you're done you can move it back to the Questions / In Review column and add the ready for dev lead label again. Thanks!

[github-actions]

@blaycoder

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, March 26, 2024 at 12:06 AM PST.}

[blaycoder]

Progress: I have copied the file path _data/internal/privacy_policy.yml onto line 103 column A in the excel sheet. I have moved this issue back to the Questions / In Review column and added the ready for dev lead label again.
Availability: 10hrs
ETA: As soon as the changes are approved and the issue is closed by the dev lead.

[LRenDO]

HI @blaycoder! Great job with this issue! It looks like there are the same errors on this page on my end too! You also did a great job with moving the issue to the right column and adding the correct label. Thanks for contributing to this epic!