fix typo/punctuation in MockFunctionAPI.md

[ChrisCoastal]

Summary

Small fix typo and comma errors in website documentation jest.fn(implementation?) section in MockFunctionAPI.md.

Test plan

No testing needed:
Simple 'there' -> 'where' typo fix.
No comma after 'if' when it begins a subordinate clause that follows the main clause.

[facebook-github-bot]

Hi @ChrisCoastal!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[ChrisCoastal]

CLA signed. Should be ready for merging. Thanks.

[mrazauskas]

Thanks! Could you also fix the same MockFunctionAPI.md file in docs and website/versioned_docs/version-28.0 directories, please?

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[ChrisCoastal]

@mrazauskas Thanks for your review, Tom! I've updated the pull request with commits for MockFunctionAPI.md in docs and website/versioned_docs/version-28.0. Much appreciated.

[mrazauskas]

@SimenB Friendly ping (;

This is ready to land. The text with typos was introduced from v28. So all applicable versioned docs are fixed.

[SimenB]

Thanks!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.