Run VS Code Spell Checker on public-tree-map.md

[DakuwoN]

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 '_projects/public-tree-map.md' 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 merge team

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. ↩

[HackforLABot]

Hi @belunatic, 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).

[DakuwoN]

This was part of my Skills Developer checklist and the link to the issue was given to me from that page, it then listed numbers 143-149 I believe in the spreadsheet, so I just followed the directions.