Mention returning undefined in "Finders Keepers"

[Kwpolska]

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. [is that really necessary for a simple text change? considering how hard the setup is?]

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 (replace XXXX with an issue no): Closes #XXXX

Description

The "Finders Kepeers" challenge text does not mention the need to return undefined if no element passes the truth test. Therefore, students can’t do it without checking the challenge tests.

[Bouncey]

@Kwpolska Thanks for the PR 👍

Can you point me in the direction of the original issue please?

[Kwpolska]

What original issue? (I didn’t create any GitHub issues if that’s what you ask.)

[Bouncey]

LGTM 👍

Thanks for contributing 🎉