Fix/drop it wording change

[jonathanihm]

Pre-Submission Checklist

• Your pull request targets the staging branch of freeCodeCamp.
• Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
• You have only one commit (if not, squash them into one commit).
• All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

• Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)
• Add new translation (feature adding new translations)

Checklist:

• Tested changes locally.
• Closes currently open issue: Closes Incorrect phrasing on challenge "Drop It" #14880

Description

Wording change for Drop It challenge

[camperbot]

@jonathanihm thanks for the PR.
You have pushed more than one commit. When you finish editing, squash your commits into one.
Please, review our Guidelines for Contributing, thank you!.

[jonathanihm]

It seems my fork was a little weird when I submitted this, please let me know if you want me to close this and submit a new PR

[raisedadead]

@jonathanihm

You need not close the PR. You just need a rebase (remember to do it when you work on a new fix or feature).

Here is how to do so:
https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/CONTRIBUTING.md#maintaining-your-fork

You should follow the same steps for this PR i.e fix/drop-it-wording-change branch

Hit us up in the Contributors Chat room, in case you need any assistance.

[camperbot]

@jonathanihm updated the pull request.

[jonathanihm]

Sorry, I thought I had done this all but apparently I just suck at Git. Thanks!

[raisedadead]

@jonathanihm thanks for the pull request and making the changes, and do not worry we have all been there, it's only a matter of time and practice and you will be an expert at git too.