Identify all mispelled words on site and make issues to fix

[ExperimentsInHonesty]

Overview

Our website needs to be free of misspellings so that our reputation for quality is maintained.

Action Items

• Identify which VS Code plugin to use for future development
• Make issues from the notes from design
• add all notes from list below in resources, by page - to a spreadsheet (see if design has already made one) Correct Misspelled Words in Figma #2597
• Audit all the pages to find misspellings not identified by design and add to spreadsheet
• make issues

Resources/Instructions

Spreadsheet from design team with all the misspellings they found
VS Code Plugins for spelling
Web Based Chrome Extension checker
Web based external checker - more sensitive than the chrome extension however will only check pages that are linked to main page (not about page, etc.)
Figma spell check plug in SPELL
Figma spell check plug in Spellchecker

List of pages with issues:

https://www.hackforla.org/program-areas

• policymaking needs to be changed to policy making
• susainability needs to be changed to sustainability

https://www.hackforla.org/join

• community is misspelled commmunity
• non-profit should be nonprofit

https://www.hackforla.org/donate

• community is misspelled commmunity

https://www.hackforla.org/communities-of-practice

• none

https://www.hackforla.org/project-meetings

• none

https://www.hackforla.org/about

• definitley needs to be definitely
• langugage needs to be language

https://www.hackforla.org/projects

• scaleable needs to be corrected to scalable

https://www.hackforla.org/credits/

• none

https://hackforla.org/citizen-engagement

• This page is not resolving yet. Check it when it is

[ExperimentsInHonesty]

@answebdev can you tell us what VScode plugin you used?

[ExperimentsInHonesty]

@JessicaLucindaCheng @answebdev It was my fault for not being clear enough, but everyone who has touched this issue seems to have misunderstood the mission. So let's talk about what we should do next.

The mission

The mission is to have a VS code plugin, that has a matching version we can put as a check when PRs are made in github (like code climate for spelling) .. and when I say matching, it's because it would be problematic if someone caught a spelling error on their local that the github check disagreed with. So using the same vendor for both, would solve that.

Then we could have the instructions in the contributing to have people download the vscode plugin and use it before they commit.

Next steps

We still need to do this. So do you want it to be part of this issue, or do we need to make a new one.

spelling errors to use to check that the plugin is effective

• In 1.5.a Docker installation troubleshooting of CONTRIBUTING.md, fix spelling of "te" to "the" in "the following wiki page is a guide for solving te issue:"
• line 41 "your" to "you're" Mobile_responsiveness.yml
• line 33 each changes to each change in Mobile_responsiveness.yml
• line 46 figma should be capitalized in Mobile_responsiveness.yml --> Not sure if this will be caught since it isn't a dictionary word
• "it's" should be "its" on homepage in "Hack for LA is a project of Code for America and is it's official Los Angeles chapter."
• "Non-profit" button and description "I am a non-profit organization." should be "nonprofit" on homepage
• "responsivenes" should be "responsiveness" in How to use Figma effectively on Open Source Volunteer Teams card on https://www.hackforla.org/toolkit/
• "elipsis" should be "ellipsis" in "Click the vertical elipsis located at the top right of the survey form" on https://www.hackforla.org/guide-pages/survey-reporting-dashboard-guide
• "elipsis" should be "ellipsis" in "VERTICAL ELIPSIS" on https://www.hackforla.org/guide-pages/survey-reporting-dashboard-guide
• "elipsis" should be "ellipsis" in "(2) Hovering over the new page added within the dropdown menu, you will see a vertical elipsis." on https://www.hackforla.org/guide-pages/survey-reporting-dashboard-guide
• Fix misspelled words on citizen-engagement-card.yml file from "policymaking" to "policy making" #2909

[ExperimentsInHonesty]

@answebdev can you respond to my question in this comment #2401 (comment)

...do you want it to be part of this issue, or do we need to make a new one.

[answebdev]

@ExperimentsInHonesty Sorry, I think I didn't think the question was directed at me. My mistake. But I think it best to make a new one.

[ExperimentsInHonesty]

Dev lead to make a new issue from this comment #2401 (comment)

Also, add the following as the last action item in the issue you write:

Once we identify the spell checker to be used, please update and edit issue #2909 by
  - [ ] Checking off the dependency for this issue
  - [ ] If all dependencies are checked off, please move issue #2909 to the New Issue Approval column and remove the Dependency label

[ExperimentsInHonesty]

• This is 100% resolved by the creation of Find Linter and Matching VS Code Plugin to Spell Check Site #3546