Run VS Code Spell Checker on survey-reporting-dashboard-guide.html

[urvishp13]

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

• [ ] You must use VS Code as your local text editor and install the Code Spell Checker VS Code extension[^2]
• [ ] Do not change any configuration settings or make any spell corrections
• [ ] Open the file _guide-pages/survey-reporting-dashboard-guide.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 #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]]

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

[GRK1998]

Availability: 9:00AM to 5:00PM ETA: Sunday 19th 2024

[LRenDO]

Hi @GRK1998! Great work recording the errors! It looks like you have some errors that are no longer included and may be due to changes in the repo, which is okay. However, it looks like there is a second occurrence of the "ARRAYFORMULA". Please include that duplicate. When you're done go ahead and add the ready for dev label again and ping me here and I will go ahead and approve it. Thank you!

[github-actions[bot]]

@GRK1998

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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, May 28, 2024 at 12:06 AM PST.}

[GRK1998]

Hi @LRenDO I have added the duplicate

[LRenDO]

Thanks! Looks great, @GRK1998!