Run VS Code Spell Checker on _includes/current-guides.html

ramitaarora commented 1 month 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 '_includes/current-guides.html' 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 merge team

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.

HackforLABot commented 3 weeks ago

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

mmcclanahan commented 3 weeks ago

Availability: Wed - Fri 8am-8pm ETA: EOD

t-will-gillis commented 2 weeks ago

Dev unassigned without completing issue- resetting.

HackforLABot commented 2 weeks ago

Hello @vorleakyek, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

HackforLABot commented 2 weeks ago

Hi @vorleakyek, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).

HackforLABot commented 2 weeks ago

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

patelbansi3009 commented 2 weeks ago

ETA: 1 hour Availability : All day 08/27/24

LRenDO commented 2 weeks ago

Hi @patelbansi3009! Great job with this issue! It looks like 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!

hackforla / website