Change the `Feature: Administrative` label to `feature: spelling` in spell check issue template about website

[t-will-gillis]

Hi @santisecco

• I agree that 'template' refers to spell-check-audit.md
• For consistency, the label should have a single space, i.e. role: back end/devOps. I see what you are saying about how the existing template has two spaces. As a test, I added many extra spaces on all of the labels and it seems that the correct label gets selected still, but I would remove the extra space anyway.
  Thanks!

I am removing the Status: Help Wanted label, but if you still have questions feel free to ask and/or add the label back to this issue.

[github-actions]

Hi @urvishp13.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[roslynwythe]

Hi @urvishp13 great job writing this issue. Since this issue involves labels, there are a few steps I would like to add to the test procedure. Please refer to #4786 (comment) and you will find two "bullet points" that describe how the developer should go about creating labels in their repository so that the labels will appear in the test issue.

Also, thank you for referencing the ER from this issue under "Additional Resources". There is a GitHub "hack" that we like to use when referencing issues; that is, if a line of text begins with a hypen ("-"), then any references to issues in that line will be expanded with the issue title.

Just one other tiny thing - we like to hide any comments that are not going to be useful to the developer picking up the issue. So please hide the comment above that the bot created.

When you have made those changes, please move the issue back to "Questions/In Review" and apply "ready for dev lead" label. Thanks!

[github-actions]

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

[santisecco]

I have a question. I want to confirm that I understood correctly.
"Create labels corresponding to each label that was listed in the updated issue template".
By "updated issue template" is this the file github/ISSUE_TEMPLATE/spell-check-audit.md after my changes?

Then by "The color of the labels don't have to match those on the hackforla/website repository" are these the labels from_https://github.com/hackforla/website/labels_?

Perhaps my question is obvious since by the issue's heading which says "spell check issue template" I can infer that refers to the file github/ISSUE_TEMPLATE/spell-check-audit.md

Finally by "then locate the template updated by your issue, and click "Get Started" to open the issue template." is this the file spell-check-audit.md in my fork?

[santisecco]

@urvishp13 Hi Urvish perhaps you can help me out with this doubt

[santisecco]

Also I noticed that in the file "spell-check-audit.md" there's seems to be "back end/devOps" with two extra spaces being "back end/devOps", it's at the start of a new line so I don't know which of the two texts I must use in the label creation.

[santisecco]

I have a blocker:
After reading again CONTRIBUTIG.md I'll be clearer in expressing my difficulties.
I do not clearly understand if the issue is refering to the file spell-check-audit.md by the term "template".
I also don't know if I am supposed to add the label "role: back
end/devOps" as it appears in the file or instead "role: back end/devOps"

Here's what I've done so far
1- Assumed that by template we mean the spell-check-audit.md
2- As the issue states "but the text of the labels must match exactly." when creating the labels I just copy/paste the text from the file. Starting from the first character in the word to the last. This made the label creation in Github have a few more spaces but the visual was not affected [image attached- note difference between "back end" and "front end"]

I want to know if that is correct before moving on with the rest.
The branch I'm working on is "change-label-spellcheck-6857"