Replace GitHub actions with GitHub Actions

Author: ronaldbarendse

.github/workflows/Vale-Linter.yml

@@ -11,6 +11,6 @@ jobs:
         with:
           fail_on_error: true
         env:
-          # Required, set by GitHub actions automatically:
+          # Required, set by GitHub Actions automatically:
           # https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

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

@@ -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
 
 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:
 

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/getting-started/cicd-pipeline/ci-cd-github-actions.md

@@ -2,7 +2,7 @@
 description: Steps and examples on how to setup a build and deployment pipeline for Umbraco Deploy using GitHub Actions.
 ---
 
-# GitHub actions
+# GitHub Actions
 
 {% hint style="info" %}
 In this example we will show how you can set up a CI/CD build server using GitHub Actions in Azure Web Apps.

10/umbraco-deploy/installation/install-configure.md

@@ -24,7 +24,7 @@ Here we will cover how to install and set up Umbraco Deploy on a new website.
 
 **Set up the Git repository and Umbraco project**
 
-The first step to get Umbraco Deploy up and running is to set up a GitHub repository. This will be where source code is stored, and, following the GitHub actions example, act as our environment where we will set up a CI/CD pipeline.
+The first step to get Umbraco Deploy up and running is to set up a GitHub repository. This will be where source code is stored, and, following the GitHub Actions example, act as our environment where we will set up a CI/CD pipeline.
 
 1. Using the Visual Studio template, set up a GitHub repository with a .gitignore file.
 2. Clone down the repository to your local machine.

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

@@ -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
 
 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:
 

13/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)
 

13/umbraco-deploy/getting-started/cicd-pipeline/ci-cd-github-actions.md

@@ -4,7 +4,7 @@ description: >-
   Deploy using GitHub Actions.
 ---
 
-# GitHub actions
+# GitHub Actions
 
 {% hint style="info" %}
 In this example we will show how you can set up a CI/CD build server using GitHub Actions in Azure Web Apps.

13/umbraco-deploy/installation/install-configure.md

@@ -24,7 +24,7 @@ Here we will cover how to install and set up Umbraco Deploy on a new website.
 
 **Set up the Git repository and Umbraco project**
 
-The first step to get Umbraco Deploy up and running is to set up a GitHub repository. This will be where source code is stored, and, following the GitHub actions example, act as our environment where we will set up a CI/CD pipeline.
+The first step to get Umbraco Deploy up and running is to set up a GitHub repository. This will be where source code is stored, and, following the GitHub Actions example, act as our environment where we will set up a CI/CD pipeline.
 
 1. Using the Visual Studio template, set up a GitHub repository with a .gitignore file.
 2. Clone down the repository to your local machine.

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

@@ -398,15 +398,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
 
 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: