chore(challenges): fixed a minor spelling error#233
chore(challenges): fixed a minor spelling error#233moT01 merged 1 commit intofreeCodeCamp:devfrom lauren-van-sloun:Fix/MinorSpellingError
Conversation
Changed "a option" to "an option" in css-grid.json ISSUES CLOSED: 17990
|
@ashera138 looks good I think, that's my first time merging something so hopefully I did it correctly - You should maybe put in the description of the PR that you also changed all that spacing so the person reviewing it knows. |
|
I actually noticed the extra white spaces after pushing (oops). I think maybe it was because I did the edit in Notepad++? I'm not sure. Thanks again for helping me on my first pr! 👍 |
|
Perhaps, you didn't deliberately add them I take? - I was going to say they should be deleted, but I noticed several other files shared that structure so I didn't think it was a problem. Thanks for contributing 👍 |
|
Yeah, I didn't intentionally add them. And you're welcome. 😄 |
|
@ashera138, thanks again for your contribution! And thank you for taking over the QA and merge @moT01 👍 No need to worry about all of the extra line breaks. That's just the new prettier format that runs with the linter. Really threw me the first time, too! |
|
Oh alright, good to know. Thanks for mentioning that @scissorsneedfoodtoo. And thanks you guys for sharing an easy issue for a beginner to grab. 😃 |
|
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Fixed a minor spelling error ("a option" => "an option")
Pre-Submission Checklist
devbranch.fix/,feature/, ortranslate/(e.g.fix/challenge-tests)npm test.npm run committo generate a conventional commit message.Learn more here: https://conventionalcommits.org/#why-use-conventional-commits
If they were done on the web interface you have ensured that you are creating conventional commit messages.
Checklist:
Closes #17990