Fixed some typos.

[EricFortin]

I found one reviewing validation code. I decided to not stop at one and fixed a couple of others in the same file.

[googlebot]

Thanks for your pull request. t 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 (e.g. 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 project maintainer to go/cla#troubleshoot.
• 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.

[EricFortin]

Signed it!

…

On Mon, Feb 26, 2018 at 4:37 PM, googlebot ***@***.***> wrote: Thanks for your pull request. t 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/ <https://cla.developers.google.com/> to sign.* Once you've signed (or fixed any issues), please reply here (e.g. 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 <https://cla.developers.google.com/clas> and verify that your email is set on your git commits <https://help.github.com/articles/setting-your-email-in-git/>. 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 project maintainer to go/cla#troubleshoot. - The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data <https://cla.developers.google.com/clas> and verify that your email is set on your git commits <https://help.github.com/articles/setting-your-email-in-git/>. - The email used to register you as an authorized contributor must also be attached to your GitHub account <https://github.com/settings/emails>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABlWtQZzpOi-Q20cit6n1JKWroGPuTnwks5tYyQYgaJpZM4ST97h> .

[googlebot]

CLAs look good, thanks!

[markmandel]

Step #3: mkdir -p ~/.kube
Step #3: mkdir -p /workspace/build//.config/gcloud
Step #3: docker run --rm -v /workspace/build//.config/gcloud:/root/.config/gcloud -v ~/.kube:/root/.kube -v /workspace:/go/src/agones.dev/agones agones-build:0229fec933 go test -race agones.dev/agones/...
Step #3: # agones.dev/agones/pkg/apis/stable/v1alpha1
Step #3: src/agones.dev/agones/pkg/apis/stable/v1alpha1/types.go:198:87: syntax error: unexpected newline, expecting comma or }
Step #3: # agones.dev/agones/pkg/apis/stable/v1alpha1
Step #3: src/agones.dev/agones/pkg/apis/stable/v1alpha1/types.go:198:87: syntax error: unexpected newline, expecting comma or }
Step #3: make: *** [test] Error 2
Step #3: Makefile:102: recipe for target 'test' failed

Looks like you accidentally removed the , at the end of line 198.

[EricFortin]

Thanks Mark, I fixed it. There's a unwritten rule somewhere stating that your first PR must not build right?

[markmandel]

Awesome. final thing 😄 can we rebase down to 1 commit, and I'll give this the 👍

[markmandel]

LGTM!