Replace Github with GitHub

Author: ronaldbarendse

10/umbraco-cms/extending/filesystemproviders/azure-blob-storage.md

@@ -44,7 +44,7 @@ The correct package will have be installed in your project.
 
 ## Configuring Blob storage
 
-The next step is to configure your blob storage. There are multiple approaches for this, but in this document, we're going to do it through `appsettings.json`. For more configuration options, see the [readme](https://github.com/umbraco/Umbraco.StorageProviders#umbracostorageproviders) on the Github repository.
+The next step is to configure your blob storage. There are multiple approaches for this, but in this document, we're going to do it through `appsettings.json`. For more configuration options, see the [readme](https://github.com/umbraco/Umbraco.StorageProviders#umbracostorageproviders) on the GitHub repository.
 
 Open up your `appsettings.json` file and add the connection string and container name under `Umbraco:Storage:AzureBlob:Media`. Your Umbraco section of appsettings will look something like this:
 

10/umbraco-cms/extending/packages/creating-a-package.md

@@ -147,7 +147,7 @@ The `Title`, `Description`, `PackageTags` came with the template and we added so
 | ------------------------ | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Version                  | 1.0.0               | This is automatically set to 1.0.0 but can be changed as appropriate.                                                                                                                                       |
 | Authors                  | Your name           | Here you get to take credit for your awesome work!                                                                                                                                                          |
-| PackageProjectUrl        | https://umbraco.com | This URL will be shown as the package's URL when others install it. It will likely be a Github repository, or similar.                                                                                      |
+| PackageProjectUrl        | https://umbraco.com | This URL will be shown as the package's URL when others install it. It will likely be a GitHub repository, or similar.                                                                                      |
 | PackageLicenseExpression | MIT                 | The license is set to MIT. Please consider how you want your package licensed. If in doubt when deciding an open-source license there are [good resources available](https://choosealicense.com/licenses/). |
 
 ### Pack it

10/umbraco-cms/extending/ui-library.md

@@ -24,7 +24,7 @@ You can also change the stylesheet of custom properties to see how the component
 
 ## Installing the UI Library Components
 
-You can download the UI Library package from [Github](https://github.com/umbraco/Umbraco.UI/tree/v1/contrib/packages).
+You can download the UI Library package from [GitHub](https://github.com/umbraco/Umbraco.UI/tree/v1/contrib/packages).
 
 If you are installing a component via npm, there are two ways to import it:
 
@@ -40,7 +40,7 @@ If you are installing a component via npm, there are two ways to import it:
     '@umbraco-ui/uui-button/lib/uui-button.element';
     ```
 
-For more information on installation, Content Delivery Networks (CDN), or included components, see the [Readme file in the Github](https://github.com/umbraco/Umbraco.UI#readme) project.
+For more information on installation, Content Delivery Networks (CDN), or included components, see the [Readme file in the GitHub](https://github.com/umbraco/Umbraco.UI#readme) project.
 
 ## Getting Started with the UI Library
 

10/umbraco-cms/reference/security/cookies.md

@@ -33,4 +33,4 @@ services.AddSession(options =>
     });
 ```
 
-For information on the rest of the cookies, see the [Constants-Web.cs](https://github.com/umbraco/Umbraco-CMS/blob/v10/contrib/src/Umbraco.Core/Constants-Web.cs) file on Github.
+For information on the rest of the cookies, see the [Constants-Web.cs](https://github.com/umbraco/Umbraco-CMS/blob/v10/contrib/src/Umbraco.Core/Constants-Web.cs) file on GitHub.

10/umbraco-cms/tutorials/creating-and-distributing-a-package.md

@@ -12,18 +12,18 @@ The content in this article is valid _only_ for Umbraco version 8. For Umbraco v
 * [Creating a test site locally](creating-and-distributing-a-package.md#creating-a-test-site-locally)
 * [Creating a package from the backoffice](creating-and-distributing-a-package.md#creating-a-package-from-the-backoffice)
 * [Creating a draft package on Our](creating-and-distributing-a-package.md#creating-a-draft-package-on-our)
-* [Pushing your package to Github](creating-and-distributing-a-package.md#pushing-your-package-to-github)
+* [Pushing your package to GitHub](creating-and-distributing-a-package.md#pushing-your-package-to-github)
 * [Pack up your package locally using UmbPack](creating-and-distributing-a-package.md#pack-up-your-package-locally-using-umbpack)
 * [Pushing your package to Our using UmbPack](creating-and-distributing-a-package.md#pushing-your-package-to-our-using-umbpack)
-* [Deploy your package using Github Actions](creating-and-distributing-a-package.md#deploy-your-package-using-github-actions)
+* [Deploy your package using GitHub Actions](creating-and-distributing-a-package.md#deploy-your-package-using-github-actions)
 * [Archive older versions on push](creating-and-distributing-a-package.md#archive-older-versions-on-push)
 
 ## Prerequisites
 
 To run this tutorial you will need the following:
 
 * Be able to run an Umbraco site locally
-* Git + Github account
+* Git + GitHub account
 * [Our Umbraco member account](https://our.umbraco.com/member/Signup) with access to upload packages
 * UmbPack installed
 * Umbraco Package templates installed
@@ -60,7 +60,7 @@ It will show you all the options you have for creating a new Umbraco site + pack
 dotnet new umbraco-v8-package -n PackageWorkshop -d
 ```
 
-This will create a new package called `PackageWorkshop`, and add a custom Dashboard for us to use in this tutorial. By default you will also get a Github Action added that we will return to later.
+This will create a new package called `PackageWorkshop`, and add a custom Dashboard for us to use in this tutorial. By default you will also get a GitHub Action added that we will return to later.
 
 After running you will have a folder called `PackageWorkshop`, inside that you will have your site and solution files. So try to open it in Visual Studio or Rider by opening the `PackageWorkshop.sln` file.
 
@@ -234,13 +234,13 @@ Now your package is on Our, and if the "Go live" button is clicked it is visible
 
 The next step is to make it a bit simpler to deploy updates to the package. It is perfectly fine to log in here and upload a new version each time. The next steps will show an easier way though.
 
-## Pushing your package to Github
+## Pushing your package to GitHub
 
 If you are creating a package in order to share it with others it is a great idea to also share the source code. It is the open source way.
 
-To share it, and make it easier to manage and deploy updates we will set up a Github repository for the package. This tutorial assumes you know what Github is, and that you have an account.
+To share it, and make it easier to manage and deploy updates we will set up a GitHub repository for the package. This tutorial assumes you know what GitHub is, and that you have an account.
 
-Create a fresh repo, with no readme, gitignore or license - do not choose a repository template (set to 'No Template'). On the second screen it will give you a command to push an existing repository to the new Github repo, should look like this but with your own user in the link:
+Create a fresh repo, with no readme, gitignore or license - do not choose a repository template (set to 'No Template'). On the second screen it will give you a command to push an existing repository to the new GitHub repo, should look like this but with your own user in the link:
 
 ```none
 git remote add origin https://github.com/jmayntzhusen/package-workshop.git
@@ -257,26 +257,26 @@ git add .
 git commit -m "Initial commit, dashboard package"
 ```
 
-At this point you have your solution in a local git repository, and we can then use the command from Github to push it up:
+At this point you have your solution in a local git repository, and we can then use the command from GitHub to push it up:
 
 ```none
 git remote add origin https://github.com/jmayntzhusen/package-workshop.git
 git branch -M main
 git push -u origin main
 ```
 
-Now you have it all on Github:
+Now you have it all on GitHub:
 
-![Github repo](<images/github-repo (1).png>)
+![GitHub repo](<images/github-repo (1).png>)
 
 ## Pack up your package locally using UmbPack
 
-At this point you know how to create a package from the backoffice, upload it to Our and push your changes to Github. That's what it takes to create and maintain a package.
+At this point you know how to create a package from the backoffice, upload it to Our and push your changes to GitHub. That's what it takes to create and maintain a package.
 
 If you want to make changes and push a new version you can carry out the following steps:
 
 * Create the new package in the backoffice
-* Sync your code to Github
+* Sync your code to GitHub
 * Go to Our and upload a new zip version
 * Set that to the current version
 * Optionally archive the previous one
@@ -399,15 +399,15 @@ You can edit all of these defaults, and also specify older versions of your pack
 
 So at this point we can work on our package locally, build a new version within seconds by running the pack command and then deploy it to Our using the push command.
 
-Not easy enough for you? Let's try automating this entire thing with Github actions then.
+Not easy enough for you? Let's try automating this entire thing with GitHub actions then.
 
-## Deploy your package using Github Actions
+## Deploy your package using GitHub Actions
 
-If you think back to the beginning when we set up our sites using the Package Templates you may remember that by default you get a Github action installed as well.
+If you think back to the beginning when we set up our sites using the Package Templates you may remember that by default you get a GitHub action installed as well.
 
 If you check out the `~/.github/workflows` folder in your solution, you will see there is a readme file and a build.yml file.
 
-The build.yml file is used by Github actions, which will perform some tasks for you when certain criteria are met. If you haven't worked with continuous integration and deployment (CI/CD) before, then this may seem like magic - but don't worry we will run through the commands.
+The build.yml file is used by GitHub actions, which will perform some tasks for you when certain criteria are met. If you haven't worked with continuous integration and deployment (CI/CD) before, then this may seem like magic - but don't worry we will run through the commands.
 
 The build.yml file contains several things, let's have a quick overview:
 
@@ -433,9 +433,9 @@ The action that it performs is what is under `jobs:build:steps`. There is a step
 It sets the version of the package to be what we've set in the release tag based on a previous step.
 {% endhint %}
 
-Below this there is another step to push the package to Our, which again is like our approach locally - except now we add the API key as a Github secret so it's not public to everyone.
+Below this there is another step to push the package to Our, which again is like our approach locally - except now we add the API key as a GitHub secret so it's not public to everyone.
 
-![Github secret](images/gh-secret.png)
+![GitHub secret](images/gh-secret.png)
 
 ```yml
 - name: Push to Our
@@ -444,7 +444,7 @@ Below this there is another step to push the package to Our, which again is like
 
 With these 2 commands and a few previous ones setting up the prerequisite build and nuget tools it is now ready to be fully automated.
 
-Ensure you have set a Github secret with the name `UMBRACO_DEPLOY_KEY` and the value of the key from Our, and then go to your local solution and uncomment the UmbPack push command in the \~/.github/workflows/build.yml file.
+Ensure you have set a GitHub secret with the name `UMBRACO_DEPLOY_KEY` and the value of the key from Our, and then go to your local solution and uncomment the UmbPack push command in the \~/.github/workflows/build.yml file.
 
 Then make sure it is added and committed locally:
 
@@ -454,14 +454,14 @@ git commit -m "Enable umbpack push in GH action"
 git push
 ```
 
-Your solution and Github repo are now in sync, and the umbpack commands in the Github action are enabled and ready to run. Final step is to create a release tag and push it to Github:
+Your solution and GitHub repo are now in sync, and the umbpack commands in the GitHub action are enabled and ready to run. Final step is to create a release tag and push it to GitHub:
 
 ```none
 git tag release/1.0.0
 git push origin release/1.0.0
 ```
 
-At this point you can go to Github and visit the Action tab to see your Github action run. When it's completed successfully you can go to your package overview on Our and see the package there.
+At this point you can go to GitHub and visit the Action tab to see your GitHub action run. When it's completed successfully you can go to your package overview on Our and see the package there.
 
 ## Archive older versions on push
 

10/umbraco-commerce/release-notes.md

@@ -90,4 +90,4 @@ This section contains the release notes for Umbraco Commerce 10 including all ch
 
 ## Legacy release notes
 
-You can find the release notes for **Vendr** in the [Change log file on Github](../../13/umbraco-commerce/changelog-archive/Vendr-core.md).
+You can find the release notes for **Vendr** in the [Change log file on GitHub](../../13/umbraco-commerce/changelog-archive/Vendr-core.md).

10/umbraco-commerce/upgrading/version-specific-upgrades.md

@@ -20,4 +20,4 @@ See the [Migrate from Vendr to Umbraco Commerce guide](../upgrading/migrate-from
 
 ## Legacy version specific upgrade notes
 
-You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on Github](https://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions). 
+You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions). 

10/umbraco-deploy/SUMMARY.md

@@ -20,7 +20,7 @@
 * [Getting started](getting-started/get-started-with-deploy.md)
 * [CI/CD Build and Deployment Pipeline](getting-started/cicd-pipeline/README.md)
   * [Azure DevOps](getting-started/cicd-pipeline/ci-cd-azure-dev-ops.md)
-  * [Github actions](getting-started/cicd-pipeline/ci-cd-github-actions.md)
+  * [GitHub actions](getting-started/cicd-pipeline/ci-cd-github-actions.md)
 * [Streamlining Local Development](getting-started/streamlining-local-development.md)
 * [Configuration](getting-started/deploy-settings.md)
 

10/umbraco-deploy/deployment-workflow/README.md

@@ -19,7 +19,7 @@ Umbraco Deploy uses a two-part deployment approach where we keep meta data (Docu
 
 In summary:
 
-1. Meta data such as Document Types, Templates, Forms, Views and config files are stored in a repository and are **deployed** between environments. This can be achieved using a CI/CD deployment pipeline with something like Github Actions or Azure DevOps.
+1. Meta data such as Document Types, Templates, Forms, Views and config files are stored in a repository and are **deployed** between environments. This can be achieved using a CI/CD deployment pipeline with something like GitHub Actions or Azure DevOps.
 2. Content and Media items are **not** stored in the repository. These need to be **transferred** directly from the Umbraco backoffice using the _"Queue for Transfer"_ option. Once a content editor has all the items needed for a transfer they will use the Deployment Dashboard in the Content section to transfer the items in the queue.
 
 ### Deploying meta data

10/umbraco-deploy/getting-started/cicd-pipeline/README.md

@@ -10,7 +10,7 @@ The build server will extract the changes that has been pushed to the repository
 
 This is something that can be done in many different ways depending on where your website is hosted and your setup.
 
-Umbraco Deploy does not require the use of any particular build or deployment tools and hence we expect that you should be able to continue using the tool or tools of your choice. Any that have support for .NET website deployments and the running of Powershell scripts. such as Azure DevOps or Github Actions, would be appropriate.
+Umbraco Deploy does not require the use of any particular build or deployment tools and hence we expect that you should be able to continue using the tool or tools of your choice. Any that have support for .NET website deployments and the running of Powershell scripts. such as Azure DevOps or GitHub Actions, would be appropriate.
 
 Above and beyond the normal steps of a build pipeline for a .NET web application - tasks like NuGet restore, solution build, running of tests etc. - Umbraco Deploy requires three additional steps.
 
@@ -34,9 +34,9 @@ Umbraco Deploy On-Premises also ships with a Powershell script, that when execut
 
 So while it may be possible to have the CI/CD step directly write the file or call the endpoint, so long as the build used supports running Powershell scripts this is the method we’d recommend, as it has some necessary error checking and retry logic built-in.
 
-## [Setting up CI/CD pipeline with Github Actions](ci-cd-github-actions.md)
+## [Setting up CI/CD pipeline with GitHub Actions](ci-cd-github-actions.md)
 
-Details the setup of a CI/CD pipeline using Github Actions.
+Details the setup of a CI/CD pipeline using GitHub Actions.
 
 ## [Setting up CI/CD pipeline with Azure DevOps](ci-cd-azure-dev-ops.md)