Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run VSCode Code Spell Checker on _guide-pages/2FA.html #5311

Closed
6 of 9 tasks
Tracked by #5248
roslynwythe opened this issue Aug 26, 2023 · 6 comments
Closed
6 of 9 tasks
Tracked by #5248

Run VSCode Code Spell Checker on _guide-pages/2FA.html #5311

roslynwythe opened this issue Aug 26, 2023 · 6 comments
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. feature: spelling ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Aug 26, 2023

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 spreadsheet1 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 extension2
  • Do not change any configuration settings or make any spell corrections
  • Open the file _guide-pages/2FA.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

Resources/Instructions

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.

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Aug 26, 2023
@github-actions

This comment was marked as outdated.

@roslynwythe roslynwythe added good first issue Good for newcomers Feature: Administrative Administrative chores etc. role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours Complexity: Small Take this type of issues after the successful merge of your second good first issue Ready for Prioritization ready for product size: 0.5pt Can be done in 3 hours or less and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing good first issue Good for newcomers ready for product size: 0.25pt Can be done in 0.5 to 1.5 hours labels Aug 26, 2023
@roslynwythe
Copy link
Member Author

@ExperimentsInHonesty please advise, could this be a good first issue?

@github-actions
Copy link

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

@kezzaam
Copy link
Member

kezzaam commented Oct 28, 2023

Review ETA: EOD 10/28/23
Availability: 27th and 28th October 7-9pm

@kezzaam kezzaam added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 28, 2023
@kezzaam
Copy link
Member

kezzaam commented Oct 28, 2023

Checked _guide-pages/2FA.html and updated spreadsheet Page Audit and Results, rows 36-40. Moved issue to Questions/In Review.

@roslynwythe
Copy link
Member Author

Thank you @kezzaam for spell checking this page and for reporting results in the spreadsheet. This issue is closed as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. feature: spelling ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Projects
Development

No branches or pull requests

4 participants