Update function.ipynb

[NinoRisteski]

two typo fixes in function.ipynb

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

Preview

Preview and run these notebook edits with Google Colab:

• site/en/guide/function.ipynb

Rendered notebook diffs available on ReviewNB.com.

Format and style

Use the TensorFlow docs notebook tools to format for consistent source diffs and lint for style:

$ python3 -m pip install -U --user git+https://github.com/tensorflow/docs

$ python3 -m tensorflow_docs.tools.nbfmt notebook.ipynb

$ python3 -m tensorflow_docs.tools.nblint --arg=repo:tensorflow/docs notebook.ipynb

If commits are added to the pull request, synchronize your local branch: git pull origin patch-1

[MarkDaoust]

Hey @NinoRisteski, thanks for the PR.

The change looks good, and I can see that you've signed the CLA, but the CLA bot won't let me merge because the email on the commit (95188570+NinoRisteski​@users.noreply.github.com) doesn't match the email you signed with. Can you resubmit without the "keep my email address private" option?

[NinoRisteski]

Hi @MarkDaoust, I just resubmitted with the same mail as my github profile. Hope its good now?

[MarkDaoust]

resubmitted

Where? I don't see any change or new PR.

[NinoRisteski]

I resubmitted the CLA with the same email as my GitHub profile. Should I make another commit, or new PR?

[MarkDaoust]

Cool, I can see that you've signed the CLA with two email addresses, the problem right now is that the commit itself is tagged with a different autogenerated address, not the one you signed the CLA with. So CLA bot doesn't recognize it as you.

In the checks section check under the details link.

So I think you need to make a new PR, or fix it and force-push this branch.

[MarkDaoust]

Fixed in #2265