Run VSCode Spell Checker on _includes/about-page/about-card-platform.html

[roslynwythe]

Overview

We need to audit HfLA codebase files for spelling errors using the VSCode Code Spell Checker extension in order to ensure site quality. Results will be categorized as misspellings, 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 '_includes/about-page/about-card-platform.html' and note any Code Spell Checker errors
• Locate the file in column A ("File") of the "Page Audit" sheet. In the column labelled "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 it 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 @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[github-actions]

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]

i. Availability: Monday to Wednesday 9:00 to 5:00
ii. ETA: Friday 22 September

[github-actions]

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 :)

[github-actions]

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

[bluechocolate2019]

Availability: Wednesday 11 - 3, Friday 12 - 4, possibly Sat if necessary
ETA: Oct 1

[LRenDO]

Hi @bluechocolate2019! Great job with this issue! It looks like there are errors on my end too! You also did a great job with moving the issue to the right column and adding the correct label.

I do have one request.

• On the Results sheet of the spreadsheet in the cSpell message column, please add the two instances (even though they are the same word) of the error message found in the Problems list in VS Code. See below.

Once it's completed, you can ping me here in a comment to let me know and add the ready for dev lead tag back to the issue. Thanks for working on this issue!

[bluechocolate2019]

Hi, @LRenDO, sorry for the delay. I came down with Covid and haven't been able to do anything until now. I added in another instance as requested on the Results spreadsheet and have added back the "ready for dev lead" label.

[roslynwythe]

Thank you @bluechocolate2019 for completing the spreadsheet with the appropriate details. This issue is closed as completed.

[LRenDO]

Hi, @LRenDO, sorry for the delay. I came down with Covid and haven't been able to do anything until now. I added in another instance as requested on the Results spreadsheet and have added back the "ready for dev lead" label.

All good! I'm sorry to hear that. I'm glad you're feeling better!Thanks for getting to it when you were able!