Run VS Code Spell Checker on pages/privacy-policy.html

[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 'pages/privacy-policy.html' 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. ↩

[github-actions]

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

[ramitaarora]

i. Availability: Weekdays 9am-12pm
ii. ETA: Thursday Feb 22

[ramitaarora]

Blocker: I am not able to make a pull request for this issue. I did make a branch and pushed it but am unable to link it to a pull request. The branch is called spell-checker-5992.

Thank you!

[roslynwythe]

Blocker: I am not able to make a pull request for this issue. I did make a branch and pushed it but am unable to link it to a pull request. The branch is called spell-checker-5992.

Thank you!

@ramitaarora since this issue does not modify the code base, there are no commits to merge and no need for a pull request. Issues of this nature are reviewed by merge team or dev leads, after the developer moves the issue to the "Questions/In Review" column. I apologize for not making that clear. Thank you for running the spell check on this file and reporting your results as requested in the spreadsheet. This issue is closed.