fix(challenges): a sentence didn't make sense, so I modified it#296
fix(challenges): a sentence didn't make sense, so I modified it#296scissorsneedfoodtoo merged 1 commit intofreeCodeCamp:devfrom
Conversation
|
@lalov1, thank you for taking the time to update this challenge. Your changes look very good overall, but I think we can further improve the end of the sentence you edited. Since JSON describes the format of the object rather than the object itself, I think the sentence should read something like the following:
Or perhaps:
There are lots of possible ways to word this, so please let me know if you have another suggestion! |
|
@scissorsneedfoodtoo I think adding "object" at the end should work. Do you want me to fix and resubmit? |
|
Sure, that's absolutely fine! To do that, make sure you're on the right branch with |
ISSUES CLOSED: #18046
e305f4f to
74daf2a
Compare
|
@scissorsneedfoodtoo I think I made the fix, but let me know if something went wrong... |
|
Everything LGTM! 👍 👍 Thank you for taking the time to fix this issue, @lalov1. Looking forward to your next contribution! |
ISSUES CLOSED: #18046
Description
Reworded information because it didn't make sense beforehand.
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 freeCodeCamp/freeCodeCamp#18046