Normalize case: Github -> GitHub (kubernetes#13828)

content/en/blog/_posts/2015-05-00-Kubernetes-Release-0170.md

@@ -140,7 +140,7 @@ Release Notes:
 * Update Exec and Portforward client to use pod subresource [#7715][127] (csrwng)
 * Added NFS to PV structs [#7564][128] (markturansky)
 * Fix environment variable error in Vagrant docs [#7904][129] (posita)
-* Adds a simple release-note builder that scrapes the Github API for recent PRs [#7616][130](brendandburns)
+* Adds a simple release-note builder that scrapes the GitHub API for recent PRs [#7616][130](brendandburns)
 * Scheduler ignores nodes that are in a bad state [#7668][131] (bprashanth)
 * Set GOMAXPROCS for etcd [#7863][132] (fgrzadkowski)
 * Auto-generated conversion methods calling one another [#7556][133] (wojtek-t)
@@ -444,7 +444,7 @@ Simple theme. Powered by [Blogger][385].
 [127]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7715 "Update Exec and Portforward client to use pod subresource"
 [128]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7564 "Added NFS to PV structs"
 [129]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7904 "Fix environment variable error in Vagrant docs"
-[130]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7616 "Adds a simple release-note builder that scrapes the Github API for recent PRs"
+[130]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7616 "Adds a simple release-note builder that scrapes the GitHub API for recent PRs"
 [131]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7668 "Scheduler ignores nodes that are in a bad state"
 [132]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7863 "Set GOMAXPROCS for etcd"
 [133]: https://github.com/GoogleCloudPlatform/kubernetes/pull/7556 "Auto-generated conversion methods calling one another"

content/en/blog/_posts/2015-07-00-How-Did-Quake-Demo-From-Dockercon-Work.md

@@ -169,7 +169,7 @@ The LPC demo was done with a simple container that did not require network conne
 In May 2015, the criu branch of libcontainer was merged into master.  Using the newly-introduced lightweight [runC](https://blog.docker.com/2015/06/runc/) container runtime, container migration was demo’ed at DockerCon15.  In this
 [![demo](https://img.youtube.com/vi/7vZ9dRKRMyc/0.jpg)](https://www.youtube.com/watch?v=?mL9AFkJJAq0) (minute 23:00), a container running Quake was checkpointed and restored on a different machine, effectively implementing container migration.
 
-At the time of this writing, there are two repos on Github that have native C/R support in Docker:
+At the time of this writing, there are two repos on GitHub that have native C/R support in Docker:
 - [Docker 1.5](https://github.com/SaiedKazemi/docker/tree/cr) (old libcontainer, relatively stable)
 - [Docker 1.7](https://github.com/boucher/docker/tree/cr-combined) (newer, less stable)  
 

content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md

@@ -12,7 +12,7 @@ Now you got your Raspberry Pi Cluster all setup, it is time to run some software
 First step is to make sure every Pi has Hypriot running, if not yet please check the [getting started guide](http://blog.hypriot.com/getting-started-with-docker-on-your-arm-device/) of them. Also hook up the cluster switch to a network so that Internet is available and every Pi get an IP-address assigned via DHCP. Because we will be running multiple Pi’s it is practical to give each Pi a unique hostname. I renamed my Pi’s to rpi-master, rpi-node-1, rpi-node-2, etc for my convenience. Note that on Hypriot the hostname is set by editing the /boot/occidentalis.txt file, not the /etc/hostname. You could also set the hostname using the Hypriot flash tool.
 
 
-The most important thing about running software on a Pi is the availability of an ARM distribution. Thanks to [Brendan Burns](https://twitter.com/brendandburns), there are Kubernetes components for ARM available in the [Google Cloud Registry](https://cloud.google.com/container-registry/docs/). That’s great. The second hurdle is how to install Kubernetes. There are two ways; directly on the system or in a Docker container. Although the container support has an experimental status, I choose to go for that because it makes it easier to install Kubernetes for you. Kubernetes requires several processes (etcd, flannel, kubectl, etc) to run on a node, which should be started in a specific order. To ease that, systemd services are made available to start the necessary processes in the right way. Also the systemd services make sure that Kubernetes is spun up when a node is (re)booted. To make the installation real easy I created an simple install script for the master node and the worker nodes. All is available at [Github](https://github.com/awassink/k8s-on-rpi). So let’s get started now!
+The most important thing about running software on a Pi is the availability of an ARM distribution. Thanks to [Brendan Burns](https://twitter.com/brendandburns), there are Kubernetes components for ARM available in the [Google Cloud Registry](https://cloud.google.com/container-registry/docs/). That’s great. The second hurdle is how to install Kubernetes. There are two ways; directly on the system or in a Docker container. Although the container support has an experimental status, I choose to go for that because it makes it easier to install Kubernetes for you. Kubernetes requires several processes (etcd, flannel, kubectl, etc) to run on a node, which should be started in a specific order. To ease that, systemd services are made available to start the necessary processes in the right way. Also the systemd services make sure that Kubernetes is spun up when a node is (re)booted. To make the installation real easy I created an simple install script for the master node and the worker nodes. All is available at [GitHub](https://github.com/awassink/k8s-on-rpi). So let’s get started now!
 
 ### Installing the Kubernetes master node
 

content/en/blog/_posts/2016-02-00-Kubernetes-community-meeting-notes-20160211.md

@@ -22,7 +22,7 @@ Note taker: Rob Hirschfeld
   * *SIG Report:*
     * Release Automation and an introduction to David McMahon
     * Docs and k8s website redesign proposal and an introduction to John Mulhausen
-    * This will allow the system to build docs correctly from Github w/ minimal effort
+    * This will allow the system to build docs correctly from GitHub w/ minimal effort
     * Will be check-in triggered
     * Getting website style updates
     * Want to keep authoring really light
@@ -33,7 +33,7 @@ Note taker: Rob Hirschfeld
     * discussion about release criteria: we will hold release date for bugs
 * Testing flake surge is over (one time event and then maintain test stability)
 * 1.3 Planning (time +40 minutes)
-    * working to cleanup the Github milestones — they should be a source of truth.  you can use Github for bug reporting
+    * working to cleanup the GitHub milestones — they should be a source of truth.  you can use GitHub for bug reporting
     * push off discussion while 1.2 crunch is under
     * Framework
         * dates

content/en/blog/_posts/2016-07-00-Oh-The-Places-You-Will-Go.md

@@ -14,7 +14,7 @@ _--Justin_
 
 You started with an excellent foundation - good declarative functionality, built around a solid API with a well defined schema and the machinery so that we could evolve going forwards. And sure enough, over your first year you grew so fast: autoscaling, HTTP load-balancing support (Ingress), support for persistent workloads including clustered databases (PetSets). You’ve made friends with more clouds (welcome Azure & OpenStack to the family), and even started to span zones and clusters (Federation). And these are just some of the most visible changes - there’s so much happening inside that brain of yours!  
 
-I think it’s wonderful you’ve remained so open in all that you do - you seem to write down everything on Github - for better or worse. I think we’ve all learned a lot about that on the way, like the perils of having engineers make scaling statements that are then weighed against claims made without quite the same framework of precision and rigor. But I’m proud that you chose not to lower your standards, but rose to the challenge and just ran faster instead - it might not be the most realistic approach, but it is the only way to move mountains!  
+I think it’s wonderful you’ve remained so open in all that you do - you seem to write down everything on GitHub - for better or worse. I think we’ve all learned a lot about that on the way, like the perils of having engineers make scaling statements that are then weighed against claims made without quite the same framework of precision and rigor. But I’m proud that you chose not to lower your standards, but rose to the challenge and just ran faster instead - it might not be the most realistic approach, but it is the only way to move mountains!  
 
 And yet, somehow, you’ve managed to avoid a lot of the common dead-ends that other open source software has fallen into, particularly as those projects got bigger and the developers end up working on it more than they use it directly. How did you do that? There’s a probably-apocryphal story of an employee at IBM that makes a huge mistake, and is summoned to meet with the big boss, expecting to be fired, only to be told “We just spent several million dollars training you. Why would we want to fire you?”. Despite all the investment google is pouring into you (along with Redhat and others), I sometimes wonder if the mistakes we are avoiding could be worth even more. There is a very open development process, yet there’s also an “oracle” that will sometimes course-correct by telling us what happens two years down the road if we make a particular design decision. This is a parent you should probably listen to!  
 

content/en/blog/_posts/2017-11-00-Kubernetes-Easy-Way.md

@@ -52,7 +52,7 @@ We’re done with step 1. In my experience it usually takes less than 5 minutes
 
 
 ## Deploy an Application to Kubernetes
-First go to [Codefresh and create an account using Github, Bitbucket, or Gitlab](https://codefresh.io/kubernetes-deploy/). As mentioned previously, Codefresh is free for both open source and smaller private projects. We’ll use it to create the configuration Yaml necessary to deploy our application to Kubernetes. Then we'll deploy our application and automate the process to happen every time we commit code changes. Here are the steps:  
+First go to [Codefresh and create an account using GitHub, Bitbucket, or Gitlab](https://codefresh.io/kubernetes-deploy/). As mentioned previously, Codefresh is free for both open source and smaller private projects. We’ll use it to create the configuration Yaml necessary to deploy our application to Kubernetes. Then we'll deploy our application and automate the process to happen every time we commit code changes. Here are the steps:  
 
 1. 1.Create a Codefresh account
 2. 2.Connect to Google Cloud (or other cluster)

content/en/blog/_posts/2017-12-00-Introducing-Kubeflow-Composable.md

@@ -5,7 +5,7 @@ slug: introducing-kubeflow-composable
 url: /blog/2017/12/Introducing-Kubeflow-Composable
 ---
 
-**_Today’s post is by David Aronchick and Jeremy Lewi, a PM and Engineer on the Kubeflow project, a new open source Github repo dedicated to making using machine learning (ML) stacks on Kubernetes easy, fast and extensible._**  
+**_Today’s post is by David Aronchick and Jeremy Lewi, a PM and Engineer on the Kubeflow project, a new open source GitHub repo dedicated to making using machine learning (ML) stacks on Kubernetes easy, fast and extensible._**  
 
 
 
@@ -19,7 +19,7 @@ Worse, these deployments are so tied to the clusters they have been deployed to
 
 
 ## Introducing Kubeflow
-To address these concerns, we’re announcing the creation of the Kubeflow project, a new open source Github repo dedicated to making using ML stacks on Kubernetes easy, fast and extensible. This repository contains:  
+To address these concerns, we’re announcing the creation of the Kubeflow project, a new open source GitHub repo dedicated to making using ML stacks on Kubernetes easy, fast and extensible. This repository contains:  
 
 - JupyterHub to create & manage interactive Jupyter notebooks
 - A Tensorflow [Custom Resource](/docs/concepts/api-extension/custom-resources/) (CRD) that can be configured to use CPUs or GPUs, and adjusted to the size of a cluster with a single setting

content/en/blog/_posts/2018-05-04-Announcing-Kubeflow-0-1.md

@@ -86,14 +86,14 @@ It’d be impossible to have gotten where we are without enormous help from ever
 * [PyTorch operator](https://github.com/kubeflow/pytorch-operator) for running PyTorch jobs
 * [Seldon Core](https://github.com/kubeflow/kubeflow/tree/master/kubeflow/seldon) for running complex model deployments and non-TensorFlow serving
 
-It’s difficult to overstate how much the community has helped bring all these projects (and more) to fruition. Just a few of the contributing companies include: Alibaba Cloud, Ant Financial, Caicloud, Canonical, Cisco, Datawire, Dell, Github, Google, Heptio, Huawei, Intel, Microsoft, Momenta, One Convergence, Pachyderm, Project Jupyter, Red Hat, Seldon, Uber and Weaveworks.
+It’s difficult to overstate how much the community has helped bring all these projects (and more) to fruition. Just a few of the contributing companies include: Alibaba Cloud, Ant Financial, Caicloud, Canonical, Cisco, Datawire, Dell, GitHub, Google, Heptio, Huawei, Intel, Microsoft, Momenta, One Convergence, Pachyderm, Project Jupyter, Red Hat, Seldon, Uber and Weaveworks.
 
 # Learning More
 
 If you’d like to try out Kubeflow, we have a number of options for you:
 
 1. You can use sample walkthroughs hosted on [Katacoda](https://www.katacoda.com/kubeflow)
-2. You can follow a guided tutorial with existing models from the [examples repository](https://github.com/kubeflow/examples). These include the [Github Issue Summarization](https://github.com/kubeflow/examples/tree/master/github_issue_summarization), [MNIST](https://github.com/kubeflow/examples/tree/master/mnist) and [Reinforcement Learning with Agents](https://github.com/kubeflow/examples/tree/master/agents).
+2. You can follow a guided tutorial with existing models from the [examples repository](https://github.com/kubeflow/examples). These include the [GitHub Issue Summarization](https://github.com/kubeflow/examples/tree/master/github_issue_summarization), [MNIST](https://github.com/kubeflow/examples/tree/master/mnist) and [Reinforcement Learning with Agents](https://github.com/kubeflow/examples/tree/master/agents).
 3. You can start a cluster on your own and try your own model. Any Kubernetes conformant cluster will support Kubeflow including those from contributors [Caicloud](https://www.prnewswire.com/news-releases/caicloud-releases-its-kubernetes-based-cluster-as-a-service-product-claas-20-and-the-first-tensorflow-as-a-service-taas-11-while-closing-6m-series-a-funding-300418071.html), [Canonical](https://jujucharms.com/canonical-kubernetes/), [Google](https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-container-cluster), [Heptio](https://heptio.com/products/kubernetes-subscription/), [Mesosphere](https://github.com/mesosphere/dcos-kubernetes-quickstart), [Microsoft](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough), [IBM](https://cloud.ibm.com/docs/containers?topic=containers-cs_cluster_tutorial#cs_cluster_tutorial), [Red Hat/Openshift ](https://docs.openshift.com/container-platform/3.3/install_config/install/quick_install.html#install-config-install-quick-install)and [Weaveworks](https://www.weave.works/product/cloud/).
 
 There were also a number of sessions at KubeCon + CloudNativeCon  EU 2018 covering Kubeflow. The links to the talks are here; the associated videos will be posted in the coming days. 

content/en/blog/_posts/2018-07-10-coredns-ga.md

@@ -167,10 +167,10 @@ You can find out more on the [CoreDNS Blog](https://coredns.io/blog).
 
 CoreDNS is an incubated [CNCF](https:://cncf.io) project.
 
-We're most active on Slack (and Github):
+We're most active on Slack (and GitHub):
 
 - Slack: #coredns on <https://slack.cncf.io>
-- Github: <https://github.com/coredns/coredns>
+- GitHub: <https://github.com/coredns/coredns>
 
 More resources can be found:
 

content/en/blog/_posts/2018-07-18-11-ways-not-to-get-hacked.md

@@ -76,7 +76,7 @@ Don't forget: keeping these logs inside the cluster is a security threat in
 
 **Centralising authentication and authorisation across an organisation (aka Single Sign On) helps onboarding, offboarding, and consistent permissions for users**.
 
-Integrating Kubernetes with third party auth providers (like Google or Github) uses the remote platform's identity guarantees (backed up by things like 2FA) and prevents administrators having to reconfigure the Kubernetes API server to add or remove users.
+Integrating Kubernetes with third party auth providers (like Google or GitHub) uses the remote platform's identity guarantees (backed up by things like 2FA) and prevents administrators having to reconfigure the Kubernetes API server to add or remove users.
 
 [Dex](https://github.com/coreos/dex) is an OpenID Connect Identity (OIDC) and OAuth 2.0 provider with pluggable connectors. Pusher takes this a stage further with [some custom tooling](https://thenewstack.io/kubernetes-single-sign-one-less-identity/), and there are some [other](https://github.com/negz/kuberos) [helpers](https://github.com/micahhausler/k8s-oidc-helper) available with slightly different use cases.
 

content/en/blog/_posts/2018-08-10-introducing-kubebuilder.md

@@ -47,5 +47,5 @@ Kubebuilder is a project under [SIG API Machinery][SIG-APIMachinery] and is bein
 
  - Kubebuilder [chat room on Slack][slack-channel]
  - SIG [mailing list][mailing-list]
- - [Github issues][open-an-issue]
+ - [GitHub issues][open-an-issue]
  - Send a pull request in the [kubebuilder repo][kubebuilder-repo]

content/en/blog/_posts/2018-10-04-non-code-contributors-guide.md

@@ -28,7 +28,7 @@ Some of the ways that you can contribute to the Kubernetes community without wri
 - Project, program, and [product management](https://github.com/kubernetes/community/blob/master/sig-pm/README.md)
 - And many more!
 
-The guide to get started with Kubernetes project contribution is [documented on Github](https://github.com/kubernetes/community/tree/master/contributors/guide), and as the Non-Code Contributors Guide is a part of that Kubernetes Contributors Guide, it can be found [here](https://github.com/kubernetes/community/blob/master/contributors/guide/non-code-contributions.md). As stated earlier, this list is not exhaustive and will continue to be a work in progress.   
+The guide to get started with Kubernetes project contribution is [documented on GitHub](https://github.com/kubernetes/community/tree/master/contributors/guide), and as the Non-Code Contributors Guide is a part of that Kubernetes Contributors Guide, it can be found [here](https://github.com/kubernetes/community/blob/master/contributors/guide/non-code-contributions.md). As stated earlier, this list is not exhaustive and will continue to be a work in progress.   
 
 To date, the typical Non-Code contributions fall into the following categories:
 

content/en/community/_index.html

@@ -53,7 +53,7 @@ <h4>We would love to hear from you, how you are using Kubernetes,<br> and what w
                 <p>Get the latest news and updates.</p>
             </div>
             <div>
-                <a href="https://github.com/kubernetes/kubernetes">Github Project</a>
+                <a href="https://github.com/kubernetes/kubernetes">GitHub Project</a>
                 <p>Check out the project and consider contributing.</p>
             </div>
             <div>

content/en/docs/contribute/_index.md

@@ -26,7 +26,7 @@ For information on the Kubernetes documentation style guide, see the [style guid
   for specific criteria for membership.
 - A SIG Docs _reviewer_ is a member of the Kubernetes organization who has
   expressed interest in reviewing documentation pull requests and who has been
-  added to the appropriate Github group and `OWNERS` files in the Github
+  added to the appropriate GitHub group and `OWNERS` files in the GitHub
   repository, by a SIG Docs Approver.
 - A SIG Docs _approver_ is a member in good standing who has shown a continued
   commitment to the project. An approver can merge pull requests

content/en/docs/contribute/advanced.md

@@ -38,7 +38,7 @@ for weekly rotations. The PR wrangler's duties include:
   [Intermediate contributing](/docs/contribute/intermediate/) for guidelines
   about how SIG Docs uses metadata.
 
-### Helpful Github queries for wranglers
+### Helpful GitHub queries for wranglers
 
 The following queries are helpful when wrangling. After working through these three queries, the remaining list of PRs to be
 reviewed is usually small. These queries specifically exclude localization PRs, and only include the `master` branch (except for the last one).