fix typos

[Birdi7]

Hello. I fixed 2 typos in README's

[googlebot]

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

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[Birdi7]

@googlebot I signed it!

[kpreid]

Sorry, I couldn't find a CLA on file under your GitHub username. Please make sure you've signed the CLA and that your commits are edited to have your matching email address (right now they are [email protected], which I believe is the default for users without a public email address).

[Birdi7]

@kpreid But I signed it with email [email protected] marked Birdi7 as my Github username. The commits are signed with [email protected] also

[kpreid]

The commit author email address in your two commits is still [email protected]. The easiest way to fix this — assuming you're using GitHub's web interface — is to make the same edits again, in a different branch than patch-1. Before you do this, make sure the "Keep my email addresses private" option in GitHub's preferences is off.

(On the command line, a rebase -i where you edit each commit by git commit --amend --reset-author and make no other changes would do it, assuming you've set your email address. But I would not recommend doing this if you're not familiar with performing interactive rebases.)