Fix GitHub typo Git'h'ub to Git'H'ub.

[potato4d]

No description provided.

[googlebot]

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).

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

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[potato4d]

I signed it.

[googlebot]

CLAs look good, thanks!

[equinox]

It's here, also. Throughout the different READMEs there are "github", "Github" etc might be worth making them all "GitHub" in the one pr at some point

[potato4d]

OK, I'll try it.

[potato4d]

I have completed fix it.
Changes are document only, source code is not done because it may be destructive(e.g. /packages/angular-cli/commands/github-pages-deploy.ts)

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

[hansl]

Ignoring the CLA bot because the original author signed it (see comments above), and I'm a Google employee.

[hansl]

LGTM, thanks!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}