Run VS Code Spell Checker on guides-team.md

[santiseccovidal]

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 '_projects/guides-team.md' and note any Code Spell Checker errors
• [ ] Locate the file in column A (named "Filepath") 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.

[HackforLABot]

Hello @jenjenkayi, we appreciate you taking on issue #7453, however it looks like you've already worked on enough issues of this complexity. Try checking out some of the issues of the next complexity from the Prioritized Backlog :)

We are going to unassign you from this issue so you can take on another issue.

Hfla appreciates you! :)

P.S. There is one exception to this rule/automation, and that is if you were away for a long time, and need to do the issue ladder again. If that is the case, please post the following note on the issue and on your Skills Issue (Pre-work Checklist). A Merge team member will reassign you to this issue, and will help you get assigned to subsequent issues up to medium size.

I am returning after a significant time away, and need to do the issue ladder again. Please assign me back to this issue.

[HackforLABot]

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

[RodgerLugo]

i. Availability: Week Days after 6 pm ii. ETA: June 13

[t-will-gillis]

Hi @RodgerLugo Please remember to change issue status from "Prioritized backlog" to "In progress (actively working)" when you assign yourself to an issue. I will change it for you.

[HackforLABot]

@RodgerLugo

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, June 10, 2025 at 12:05 AM PST.}

[RodgerLugo]

Progress: I’ve reviewed the file using the VS Code Spell Checker extension and completed the spell check. Blockers: I currently do not have access to the HfLA spelling audit spreadsheet, which is required to complete the audit and proceed with the pull request. Availability: Weekdays after 5 PM. ETA: Early next week, when access to the HfLA spelling audit spreadsheet.

[t-will-gillis]

Hi @RodgerLugo I added you to the website Drive access using the email you provided on the Roster. You should have access to the spreadsheet now. Let us know if you have questions. Thanks!

[t-will-gillis]

Hi @RodgerLugo Thank you for working on this issue. A couple of comments:

• on the HfLA spelling audit spreadsheet - Results sheet, "Page Audit" tab, there is an entry for _projects/guide-teams.md already, near line 137. Please remove the extra entry around line 188, and please add the correct entry that "At least one error" was found.
• Otherwise, you noted on the "Results" tab that there was one false positive found.

After you make these changes, please send me a message so I can close the issue. Thanks again!

[RodgerLugo]

Hi @t-will-gillis, Thank you for the clarification! I’ve made the changes, removed the duplicate entry, and confirmed the correct result is selected. Let me know if anything else is needed. Thanks again!

[t-will-gillis]

Hey @RodgerLugo Looks great! Closing this as successfully completed.