Normalize case: Github -> GitHub

[dpb587-pivotal]

As a brand reference, G/H should both be capitalized.

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 34911ec

https://deploy-preview-13828--kubernetes-io-master-staging.netlify.com

[glo-pena]

Everything pretty straight forward and correct.
/lgtm

[rlenferink]

As said, looks good!

/lgtm

[rlenferink]

/assign @Bradamant3
as PR wrangler

[glo-pena]

Everything pretty straight forward and correct.
/lgtm

[DanyC97]

@dpb587-pivotal in general we would prefer to have a PR per language since we have different teams who can review the content.

Also a smaller PR is easier to review and than a big PR like this. Not to mention that in order to merge this PR you will need to wait for every language/localization team to chime in (looking at the comments i wouldn't know on which team the people who responded are part of).

Personally i would split this PR.

[rlenferink]

@dpb587-pivotal in general we would prefer to have a PR per language since we have different teams who can review the content.

Also a smaller PR is easier to review and than a big PR like this. Not to mention that in order to merge this PR you will need to wait for every language/localization team to chime in (looking at the comments i wouldn't know on which team the people who responded are part of).

Personally i would split this PR.

Hi @DanyC97 in general, I completely agree with you, e.g. having the case were multiple languages are changed. In this case only a single word is changed Github => GitHub. This is quite easy to check and therefore someone from the root-owners should be enough.

[electrocucaracha]

I found a hit for Github in content/es//community/_index.html, can you take a look?

grep -r "Github" content/es/                                                                                                                                                                                                                                                             14:56:40
content/es//community/_index.html:                <a href="https://github.com/kubernetes/kubernetes"> Proyecto en Github </a>

/lgtm cancel

[dpb587-pivotal]

@electrocucaracha can you verify the checkout you were looking at? I believe that line was already changed here, and I don't see other references in that file.

[electrocucaracha]

@electrocucaracha can you verify the checkout you were looking at? I believe that line was already changed here, and I don't see other references in that file.

It's weird, I'm sure that I cloned and verified that on your branch... But it's true the line has the proper case(https://github.com/dpb587-pivotal/website/blob/patch-2/content/es/community/_index.html#L49)

/lgtm

[DanyC97]

@dpb587-pivotal in general we would prefer to have a PR per language since we have different teams who can review the content.
Also a smaller PR is easier to review and than a big PR like this. Not to mention that in order to merge this PR you will need to wait for every language/localization team to chime in (looking at the comments i wouldn't know on which team the people who responded are part of).
Personally i would split this PR.

Hi @DanyC97 in general, I completely agree with you, e.g. having the case were multiple languages are changed. In this case only a single word is changed Github => GitHub. This is quite easy to check and therefore someone from the root-owners should be enough.

i understand @rlenferink and happy with letting this PR in however we all need to be careful and not abuse / ask for a waiver just because is a simple/ minor/ typo change. The rational is that new contributors will find this PRs and they will follow on the basis that if their PR was merged, mine should be accepted too.

/lgtm

[rlenferink]

@DanyC97 That's definitely true as well! However, the PR already exists now, so for the next time indeed ;)

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dpb587-pivotal]

Thanks for the assist, @rlenferink.