Fix case of GitHub

jbampton · jbampton · commit e8ee332bf630 · 2020-10-06T23:51:15.000+10:00
Change `Github` to `GitHub`
diff --git a/README.md b/README.md
@@ -27,7 +27,7 @@ npm link cloudflare-docs-engine && npm run bootstrap && npm run develop
 
 ## Publishing
 
-Each [product](https://github.com/cloudflare/cloudflare-docs/tree/master/products)’s docs are automatically deployed via [@cloudflare/wrangler](https://github.com/cloudflare/wrangler) using Github Actions.
+Each [product](https://github.com/cloudflare/cloudflare-docs/tree/master/products)’s docs are automatically deployed via [@cloudflare/wrangler](https://github.com/cloudflare/wrangler) using GitHub Actions.
 
 Test environment deploys to:
 
diff --git a/products/argo-tunnel/src/content/use-cases/index.md b/products/argo-tunnel/src/content/use-cases/index.md
@@ -21,4 +21,4 @@ To do this, [download](../downloads/) the Mac, Linux or Windows version of Tunne
 
 ## Webhooks In Development Environments
 
-When developing an application that uses webhooks (such as building an app for [Github](https://developer.github.com/webhooks/), [Slack](https://api.slack.com/incoming-webhooks) or [Stripe](https://stripe.com/docs/webhooks)) you can use Tunnel to run a webhook endpoint from your local environment. Once you run Tunnel on your computer, Tunnel will expose a public URL that you can set as your webhook endpoint. Tunnel will forward all requests to that endpoint to your local development environment.
+When developing an application that uses webhooks (such as building an app for [GitHub](https://developer.github.com/webhooks/), [Slack](https://api.slack.com/incoming-webhooks) or [Stripe](https://stripe.com/docs/webhooks)) you can use Tunnel to run a webhook endpoint from your local environment. Once you run Tunnel on your computer, Tunnel will expose a public URL that you can set as your webhook endpoint. Tunnel will forward all requests to that endpoint to your local development environment.
diff --git a/products/docs-engine/src/content/contributing/development-setup.md b/products/docs-engine/src/content/contributing/development-setup.md
@@ -61,6 +61,6 @@ At this point, you can make changes to the Markdown files inside the contect dir
 
 <Aside>
 
-__Note:__ Unfortunately, for now you’ll need to stop and restart `npm run develop` every time you make changes. This is something we’re urgently looking to fix and can be tracked [in this Github issue](https://github.com/cloudflare/cloudflare-docs-engine/issues/279), which also includes a workaround which may help in the interim.
+__Note:__ Unfortunately, for now you’ll need to stop and restart `npm run develop` every time you make changes. This is something we’re urgently looking to fix and can be tracked [in this GitHub issue](https://github.com/cloudflare/cloudflare-docs-engine/issues/279), which also includes a workaround which may help in the interim.
 
 </Aside>
diff --git a/products/docs-engine/src/content/how-it-works.md b/products/docs-engine/src/content/how-it-works.md
@@ -6,11 +6,11 @@ order: 1
 
 <Aside>
 
-__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on Github](https://github.com/adamschwartz)). Thanks for your patience.
+__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on GitHub](https://github.com/adamschwartz)). Thanks for your patience.
 
 </Aside>
 
-In short, docs sites built with the Cloudflare Docs Engine are [Gatsby](https://www.gatsbyjs.com) sites with a bunch of [custom MDX components](/markdown) and a shell UI you that’s consistent across products, all deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via the [Wrangler Github Action](https://github.com/cloudflare/wrangler-action).
+In short, docs sites built with the Cloudflare Docs Engine are [Gatsby](https://www.gatsbyjs.com) sites with a bunch of [custom MDX components](/markdown) and a shell UI you that’s consistent across products, all deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via the [Wrangler GitHub Action](https://github.com/cloudflare/wrangler-action).
 
 --------------------------------
 
@@ -99,7 +99,7 @@ Many of the other fields are self-explanatory. See [Configuration](/reference/co
 
 ### 3. wrangler.toml
 
-Each docs site is deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via a [Wrangler Github Action](https://github.com/cloudflare/wrangler-action).
+Each docs site is deployed as a [Workers Sites project](https://workers.cloudflare.com/sites) via a [Wrangler GitHub Action](https://github.com/cloudflare/wrangler-action).
 
 To set this up, you’ll need to [configure your `wrangler.toml`](https://developers.cloudflare.com/workers/cli-wrangler/configuration#keys) file just as you would any other [Workers Sites project](https://developers.cloudflare.com/workers/platform/sites/).
 
@@ -167,7 +167,7 @@ Here’s a minimal example site built with Docs Engine:
 `}}/>
 </div></div></div>
 
-__[Open demo](https://docs-engine-example.adam.workers.dev)__ · ([Github](https://github.com/adamschwartz/docs-engine-example))
+__[Open demo](https://docs-engine-example.adam.workers.dev)__ · ([GitHub](https://github.com/adamschwartz/docs-engine-example))
 
 --------------------------------
 
diff --git a/products/docs-engine/src/content/how-to-guides/contribute-to-a-product.md b/products/docs-engine/src/content/how-to-guides/contribute-to-a-product.md
@@ -6,7 +6,7 @@ order: 1
 
 <Aside>
 
-__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in with Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on Github](https://github.com/adamschwartz)). Thanks for your patience.
+__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in with Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on GitHub](https://github.com/adamschwartz)). Thanks for your patience.
 
 </Aside>
 
@@ -18,7 +18,7 @@ A product has been migrated if it is listed in the [migration table](https://git
 
 ## Two ways to contibute
 
-1. For small changes, simply find the `.md` file you want to modify inside the product’s `src/content/` directory. The `Edit on Github` link in the footer of every deployed page will automatically link you there.
+1. For small changes, simply find the `.md` file you want to modify inside the product’s `src/content/` directory. The `Edit on GitHub` link in the footer of every deployed page will automatically link you there.
 
 2. For larger changes, or changes made to multiple files at once, you’ll want to set up a local development environment, which you can do by [following these steps](/how-to-guides/migrate-a-product#step-2-set-up-local-development).
 
diff --git a/products/docs-engine/src/content/how-to-guides/migrate-a-product.md b/products/docs-engine/src/content/how-to-guides/migrate-a-product.md
@@ -6,17 +6,17 @@ order: 0
 
 <Aside>
 
-__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in with Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on Github](https://github.com/adamschwartz)). Thanks for your patience.
+__Note for Cloudflare employees:__ The details of this process are still being worked out. For the time being, please do not migrate any Cloudflare products without first checking in with Adam ([afs@cloudflare.com](mailto:afs@cloudflare.com), [@adamschwartz on GitHub](https://github.com/adamschwartz)). Thanks for your patience.
 
 </Aside>
 
-This document is intended to help __Cloudflare employees__ migrate [existing docs sites](https://developers.cloudflare.com/docs/) to the [`products/` folder](https://github.com/cloudflare/cloudflare-docs/tree/master/products) inside the [@cloudflare/cloudflare-docs](https://github.com/cloudflare/cloudflare-docs) repo on Github.
+This document is intended to help __Cloudflare employees__ migrate [existing docs sites](https://developers.cloudflare.com/docs/) to the [`products/` folder](https://github.com/cloudflare/cloudflare-docs/tree/master/products) inside the [@cloudflare/cloudflare-docs](https://github.com/cloudflare/cloudflare-docs) repo on GitHub.
 
 --------------------------------
 
 ## Prerequisites
 
-This document assumes a basic understanding of software development, how Github works, as well as familiarity with the Markdown syntax and YAML frontmatter.
+This document assumes a basic understanding of software development, how GitHub works, as well as familiarity with the Markdown syntax and YAML frontmatter.
 
 It also assumes you have read through [how the Docs Engine works](/how-it-works).
 
@@ -82,7 +82,7 @@ The next thing you’ll want to do is get a local development setup going.
 
 <Aside>
 
-__Note:__ Unfortunately, for now you’ll need to stop and restart `npm run develop` every time you make changes. This is something we’re urgently looking to fix and can be tracked [in this Github issue](https://github.com/cloudflare/cloudflare-docs-engine/issues/279), which also includes a workaround which may help in the interim.
+__Note:__ Unfortunately, for now you’ll need to stop and restart `npm run develop` every time you make changes. This is something we’re urgently looking to fix and can be tracked [in this GitHub issue](https://github.com/cloudflare/cloudflare-docs-engine/issues/279), which also includes a workaround which may help in the interim.
 
 </Aside>
 
@@ -99,7 +99,7 @@ In terms of improving/updating the content itself, there are a number of great r
 - [__Workers docs site__ example](https://developers.cloudflare.com/workers) – You can also take a look at the [Workers content](https://github.com/cloudflare/cloudflare-docs/tree/4fd3a4af9507b20bb23fea4d7c4f4cd349c0f463/products/workers/src/content) for an example of a well-structured docs site.
 
 
-- Feel free to [@adamschwartz](https://github.com/adamschwartz) in an issue on Github, or DM @afs in chat.
+- Feel free to [@adamschwartz](https://github.com/adamschwartz) in an issue on GitHub, or DM @afs in chat.
 
 
 ## Step 4: Deploy your new site
@@ -108,7 +108,7 @@ This is still being worked out, but in essence, this requires three easy steps (
 
 1. Uncomment a few lines inside your `wrangler.toml` file to enable `[env.production]`.
 
-2. Add a second `wrangler publish` with the new `production` environment in the Github Action [`deploy.yml` file](https://github.com/cloudflare/cloudflare-docs/blob/4fd3a4af9507b20bb23fea4d7c4f4cd349c0f463/.github/workflows/deploy.yml).
+2. Add a second `wrangler publish` with the new `production` environment in the GitHub Action [`deploy.yml` file](https://github.com/cloudflare/cloudflare-docs/blob/4fd3a4af9507b20bb23fea4d7c4f4cd349c0f463/.github/workflows/deploy.yml).
 
 3. Make a pull request to remove the corresponding content from inside Bitbucket (`@DOCS/developer-docs/browse/src/content`).
 
diff --git a/products/docs-engine/src/content/how-to-guides/set-up-a-new-repo.md b/products/docs-engine/src/content/how-to-guides/set-up-a-new-repo.md
@@ -24,7 +24,7 @@ Here’s a minimal example site built with Docs Engine:
 
 __[Open demo](https://docs-engine-example.adam.workers.dev)__
 
-To try it yourself, fork the [example repo on Github](https://github.com/adamschwartz/docs-engine-example), and then [set up a dev environment](/contributing/development-setup).
+To try it yourself, fork the [example repo on GitHub](https://github.com/adamschwartz/docs-engine-example), and then [set up a dev environment](/contributing/development-setup).
 
 --------------------------------
 
diff --git a/products/docs-engine/src/content/index.md b/products/docs-engine/src/content/index.md
@@ -12,7 +12,7 @@ Documentation for the __Docs Engine__ which powers Cloudflare’s developer docs
 
 The engine is built with [Gatsby](https://www.gatsbyjs.com/), and makes generous use of custom [MDX components](/markdown).
 
-It’s __open-source__ and [available on Github](https://github.com/cloudflare/cloudflare-docs-engine).
+It’s __open-source__ and [available on GitHub](https://github.com/cloudflare/cloudflare-docs-engine).
 
 <p><Link to="/how-it-works" class="Button Button-is-docs-primary">How it works</Link> &nbsp; <Link to="/faq" class="Button Button-is-docs-secondary">FAQ</Link></p>
 
@@ -22,7 +22,7 @@ It’s __open-source__ and [available on Github](https://github.com/cloudflare/c
 
 <TableWrap>
 
-| Docs site                                                              | Github                                                                                                                        |
+| Docs site                                                              | GitHub                                                                                                                        |
 |------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
 | [Workers](https://developers.cloudflare.com/workers/)                  | [@cloudflare/cloudflare-docs/.../workers](https://github.com/cloudflare/cloudflare-docs/tree/master/products/workers)         |
 | [Docs Engine](https://docs-engine-docs.adam.workers.dev/) — This site. | [@cloudflare/cloudflare-docs/.../docs-engine](https://github.com/cloudflare/cloudflare-docs/tree/master/products/docs-engine) |
diff --git a/products/docs-engine/src/content/reference/configuration.md b/products/docs-engine/src/content/reference/configuration.md
@@ -24,7 +24,7 @@ Create a `docs-config.js` file which exports (by setting `module.exports`) a Jav
   - The logo for the docs site, represented as the SVG `<path/>` [`d` attribute](https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/d) for an inline SVG element with `viewBox="0 0 48 48"`. The example `"M8 8h32v32h-32v-32z"` would draw a solid `32px` square centered inside the `48px` square space.
 
 - `contentRepo` <Type>string</Type> <PropMeta>required</PropMeta>
-  - The Github repo (e.g. `"cloudflare/cloudflare-docs"`) used to for example construct the the “Edit on Github” links displayed in each docs page’s footer.
+  - The GitHub repo (e.g. `"cloudflare/cloudflare-docs"`) used to for example construct the the “Edit on GitHub” links displayed in each docs page’s footer.
 
 - `contentRepoFolder` <Type>string</Type> <PropMeta>optional</PropMeta>
   - By default the engine assumes that a docs site’s structure is placed in the root of a project repo. However, this whole structure can also be placed inside any sub-folder by setting this property. For example, this site’s content is inside the [`products/docs-engine` folder](https://github.com/cloudflare/cloudflare-docs/tree/4fd3a4af9507b20bb23fea4d7c4f4cd349c0f463/products/docs-engine) of [@cloudflare/cloudflare-docs](https://github.com/cloudflare/cloudflare-docs) so its `"products/docs-engine"`.
diff --git a/products/logs/src/content/analytics-integrations/elastic/index.md b/products/logs/src/content/analytics-integrations/elastic/index.md
@@ -52,7 +52,7 @@ Cloudflare logs are HTTP/HTTPS request logs in JSON format and are gathered from
 </a>
 Before getting Cloudflare logs into Elastic:
 
-1. Install an AWS Lambda function, available in the file _cloudflare-elastic-lambda.zip_ from Github at this location: [https://github.com/cloudflare/cloudflare-elastic/releases/tag/v0.3-7.x](https://github.com/cloudflare/cloudflare-elastic/releases/tag/v0.3-7.x).
+1. Install an AWS Lambda function, available in the file _cloudflare-elastic-lambda.zip_ from GitHub at this location: [https://github.com/cloudflare/cloudflare-elastic/releases/tag/v0.3-7.x](https://github.com/cloudflare/cloudflare-elastic/releases/tag/v0.3-7.x).
 
 2. Upload the _cloudflare-elastic-lambda.zip_ file to an S3 bucket.
 
diff --git a/products/mobile-sdk/src/content/unity/unity-android.md b/products/mobile-sdk/src/content/unity/unity-android.md
@@ -6,7 +6,7 @@ title: Getting Started with Unity for Android
 
 The Neumob Unity plugin implements support for using Neumob, allowing you to accelerate network requests in your Unity-Android builds.
 
-The Neumob Unity plugin requires Unity 5.0 or newer and API 14 and up. You can find the plugin on the `Unity Asset store <http://u3d.as/nYw>`_ or you can checkout the Github repository `here <https://github.com/neumob/neumob-unity-android>`_.
+The Neumob Unity plugin requires Unity 5.0 or newer and API 14 and up. You can find the plugin on the `Unity Asset store <http://u3d.as/nYw>`_ or you can checkout the GitHub repository `here <https://github.com/neumob/neumob-unity-android>`_.
 
 ## Installation ##
 
diff --git a/products/mobile-sdk/src/content/unity/unity-ios.md b/products/mobile-sdk/src/content/unity/unity-ios.md
@@ -6,7 +6,7 @@ title: Getting Started with Unity for iOS
 
 The Neumob Unity plugin implements support for using Neumob, allowing you to accelerate network requests in your Unity-iOS builds.
 
-The Neumob Unity plugin requires Unity 5.0 or newer and iOS 7.0 and up.You can find the plugin on the `Unity Asset store <http://u3d.as/nX8>`_ or you can checkout the Github repository `here <https://github.com/neumob/neumob-unity-ios>`_.
+The Neumob Unity plugin requires Unity 5.0 or newer and iOS 7.0 and up.You can find the plugin on the `Unity Asset store <http://u3d.as/nX8>`_ or you can checkout the GitHub repository `here <https://github.com/neumob/neumob-unity-ios>`_.
 
 ## Installation ##
 
diff --git a/products/stream/src/content/getting-started/uploading-golang.md b/products/stream/src/content/getting-started/uploading-golang.md
@@ -63,4 +63,4 @@ upload.Progress()
 upload.Finished()
 ```
 
-Please see [go-tus](https://github.com/eventials/go-tus) on Github for functionality such as resuming uploads and getting more details about the progress of the upload.
+Please see [go-tus](https://github.com/eventials/go-tus) on GitHub for functionality such as resuming uploads and getting more details about the progress of the upload.
diff --git a/products/terraform/docs-config.js b/products/terraform/docs-config.js
@@ -6,7 +6,7 @@ module.exports = {
   contentRepoFolder: "products/terraform",
   externalLinks: [
     {
-      title: "Github @cloudflare/terraform-provider-cloudflare",
+      title: "GitHub @cloudflare/terraform-provider-cloudflare",
       url: "https://github.com/cloudflare/terraform-provider-cloudflare"
     },
     {
diff --git a/products/terraform/src/content/index.md b/products/terraform/src/content/index.md
@@ -22,6 +22,6 @@ See [Installing Terraform](/installing/).
 
 ## Issues
 
-Report Terraform config issues via [Github](https://github.com/terraform-providers/terraform-provider-cloudflare/issues).
+Report Terraform config issues via [GitHub](https://github.com/terraform-providers/terraform-provider-cloudflare/issues).
 
 </ContentColumn>

Original file line number	Diff line number	Diff line change
`@@ -21,4 +21,4 @@ To do this, [download](../downloads/) the Mac, Linux or Windows version of Tunne`
`21`	`21`
`22`	`22`	`## Webhooks In Development Environments`
`23`	`23`
`24`		-When developing an application that uses webhooks (such as building an app for [Github](https://developer.github.com/webhooks/), [Slack](https://api.slack.com/incoming-webhooks) or [Stripe](https://stripe.com/docs/webhooks)) you can use Tunnel to run a webhook endpoint from your local environment. Once you run Tunnel on your computer, Tunnel will expose a public URL that you can set as your webhook endpoint. Tunnel will forward all requests to that endpoint to your local development environment.
	`24`	+When developing an application that uses webhooks (such as building an app for [GitHub](https://developer.github.com/webhooks/), [Slack](https://api.slack.com/incoming-webhooks) or [Stripe](https://stripe.com/docs/webhooks)) you can use Tunnel to run a webhook endpoint from your local environment. Once you run Tunnel on your computer, Tunnel will expose a public URL that you can set as your webhook endpoint. Tunnel will forward all requests to that endpoint to your local development environment.