chore: Review the language fixes.

[pallabiwrites]

Description

Fixes #

Note: It's a good idea to open an issue first for discussion.

Checklist

• I have followed Sample Guidelines from AUTHORING_GUIDE.MD
• README is updated to include all relevant information
• Tests pass: nox -s py-3.6 (see Test Environment Setup)
• Lint pass: nox -s lint (see Test Environment Setup)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• Please merge this PR for me once it is approved.
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample

[google-cla]

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.

[google-cla]

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.

[engelke]

Thanks for this pull request, cleaning up this code. LGTM, so after you sign the CLA and we have another review, we will merge it.

[pallabiwrites]

Hi Charles, Thanks. I have signed the CLA. Regards, Pallabi

…

On Wed, Aug 18, 2021 at 9:37 PM Charles Engelke ***@***.***> wrote: ***@***.**** approved this pull request. Thanks for this pull request, cleaning up this code. LGTM, so after you sign the CLA and we have another review, we will merge it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6591 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU35UOAIT4XF2XS5K6PWULTT5PLEJANCNFSM5CLFLNSA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[dandhlee]

Thanks for putting this in!

For what it's worth, following e.g. with a comma is not a formal standard in some parts of the world. It seems like it may be a case in the US, but not for UK. Nothing wrong with what we have here, but in case anyone thinks that this is mandatory that it's up to the writer.

[dandhlee]

Merging without product DPE approval as it's just comment changes.