Replace Github with GitHub everywhere

.github/workflows/deploy.yml

@@ -71,7 +71,7 @@ jobs:
       - name: check dev azure connection string
         if: env.AIO_AZURE_DEV_CONNECTION_STRING == null
         run: |
-          echo "::error::Please set the Azure Blob Storage connection string as AIO_AZURE_DEV_CONNECTION_STRING in Github Secrets"
+          echo "::error::Please set the Azure Blob Storage connection string as AIO_AZURE_DEV_CONNECTION_STRING in GitHub Secrets"
           exit 1
         env:
           AIO_AZURE_DEV_CONNECTION_STRING: ${{ secrets.AIO_AZURE_DEV_CONNECTION_STRING }}
@@ -175,7 +175,7 @@ jobs:
       - name: check prod azure connection string
         if: env.AIO_AZURE_PROD_CONNECTION_STRING == null
         run: |
-          echo "::error::Please set the Azure Blob Storage connection string as AIO_AZURE_PROD_CONNECTION_STRING in Github Secrets"
+          echo "::error::Please set the Azure Blob Storage connection string as AIO_AZURE_PROD_CONNECTION_STRING in GitHub Secrets"
           exit 1
         env:
           AIO_AZURE_PROD_CONNECTION_STRING: ${{ secrets.AIO_AZURE_PROD_CONNECTION_STRING }}

.github/workflows/github-pages.yml

@@ -1,5 +1,5 @@
 ---
-name: Github Pages
+name: GitHub Pages
 on:
   workflow_dispatch:
   push:

src/pages/getting_started/first_app.md

@@ -168,7 +168,7 @@ There are a few sample flows listed below. Some developers may not have access t
     e2e   node_modules  package.json  web-src
     ```
 
-1. Note that you still can add/remove the extension points, back-end actions, SPA front-end or Github workflows from your application later by respectively using the `aio app <add|delete> ext`, `aio app <add|delete> action`, `aio app <add|delete> web-assets` and `aio app <add|delete> ci` commands within your application folder.
+1. Note that you still can add/remove the extension points, back-end actions, SPA front-end or GitHub workflows from your application later by respectively using the `aio app <add|delete> ext`, `aio app <add|delete> action`, `aio app <add|delete> web-assets` and `aio app <add|delete> ci` commands within your application folder.
 
 1. Optionally, you can install an App Builder template using Template Registry. Discover available templates in the App Builder template registry with the following command:
 
@@ -229,7 +229,7 @@ There are a few sample flows listed below. Some developers may not have access t
     - **Actions: Deploy Runtime actions:** adding the boilerplate for backend serverless actions on [Adobe I/O Runtime](/runtime)
     - **Events: Publish to Adobe I/O Events:** adding the boilerplate for a serverless action that publishes [Custom I/O Events](/events/docs/guides/using/custom_events/)
     - **Web Assets: Deploy hosted static assets:** adding the boilerplate for frontend [React-Spectrum](https://react-spectrum.adobe.com/) SPA and static assets
-    - **CI/CD: Include GitHub Actions based workflows for Build, Test and Deploy:** adding the boilerplate for Github Actions supporting CI/CD process of the application
+    - **CI/CD: Include GitHub Actions based workflows for Build, Test and Deploy:** adding the boilerplate for GitHub Actions supporting CI/CD process of the application
 
 1. If you included `Actions` in your last selection, you will be asked to select one or more sample actions to be generated along with the new app.
 
@@ -299,7 +299,7 @@ Note that you may not see all the options listed below on your command line, bec
     actions   e2e   node_modules  package.json  web-src
     ```
 
-1. Note that you still can add/remove the back-end actions, SPA front-end or Github workflows from your application later by respectively using the `aio app <add|delete> action`, `aio app <add|delete> web-assets` and `aio app <add|delete> ci` commands within your application folder.
+1. Note that you still can add/remove the back-end actions, SPA front-end or GitHub workflows from your application later by respectively using the `aio app <add|delete> action`, `aio app <add|delete> web-assets` and `aio app <add|delete> ci` commands within your application folder.
 
 ### 4.2 Developer is not Logged in as Enterprise Organization user
 

src/pages/guides/deployment/ci_cd_for_firefly_apps.md

@@ -40,19 +40,19 @@ Upon bootstrapping of a new App Builder Application from the [CLI](https://githu
 
 If the developer selects this option, the application code will be initialized with an additional `.github` folder at its root. This folder contains default [GitHub Workflows](https://github.com/adobe/generator-aio-app/tree/master/generators/add-ci/.github/workflows) that can be extended at application level depending on the developer's needs.
 
-### Github Workflows
+### GitHub Workflows
 
-The default GitHub Workflows enable the following actions based on specific Github events triggered on the application repository:
+The default GitHub Workflows enable the following actions based on specific GitHub events triggered on the application repository:
 
 - On `Pull Request`, the application unit tests are executed by calling `aio app test` against the requested changes. See the [PR workflow](https://github.com/adobe/generator-aio-app/blob/master/generators/add-ci/.github/workflows/pr_test.yml).
 
 - On `Branch Merge`, the application gets deployed to the `Stage` workspace by calling `aio app deploy`. The back-end serverless actions get deployed to Runtime, while the SPA gets deployed to the out-of-the-box CDN if the application has a web UI. See the [Deploy Stage workflow](https://github.com/adobe/generator-aio-app/blob/master/generators/add-ci/.github/workflows/deploy_stage.yml).
 
 - On `Repository Release`, the application gets deployed to the `Production` workspace by calling `aio app deploy`. The back-end serverless actions get deployed to Runtime, while the SPA gets deployed to the out-of-the-box CDN if the application has a web UI. See the [Deploy Prod workflow](https://github.com/adobe/generator-aio-app/blob/master/generators/add-ci/.github/workflows/deploy_prod.yml).
 
-Each of the default [Github Workflows](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow) leverages two core features provided by Github: [Github Actions](https://github.com/features/actions) and [Github Secrets](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets).
+Each of the default [GitHub Workflows](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow) leverages two core features provided by GitHub: [GitHub Actions](https://github.com/features/actions) and [GitHub Secrets](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets).
 
-![CI/CD with Github Actions](../../images/ci-cd-github-actions-architecture.png)
+![CI/CD with GitHub Actions](../../images/ci-cd-github-actions-architecture.png)
 
 ### GitHub Actions for AIO CLI
 

src/pages/guides/index.md

@@ -129,9 +129,9 @@ It enables developers to perform the following actions on behalf of their App Bu
 
 The [out-of-the-box CI/CD support](./deployment/ci_cd_for_firefly_apps.md) for App Builder Applications consists in:
 
-- [Github Actions](https://github.com/features/actions) to [setup the CLI](https://github.com/adobe/aio-cli-setup-action) and use it to [perform actions](https://github.com/adobe/aio-apps-action) such as application testing, build and deployment.
-- [Github Workflows](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow) to orchestrate the Github Actions upon specific events triggered against the application repository.
-- [Github Secrets](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to store application secrets required for the execution of the Github Workflows against specific environments.
+- [GitHub Actions](https://github.com/features/actions) to [setup the CLI](https://github.com/adobe/aio-cli-setup-action) and use it to [perform actions](https://github.com/adobe/aio-apps-action) such as application testing, build and deployment.
+- [GitHub Workflows](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow) to orchestrate the GitHub Actions upon specific events triggered against the application repository.
+- [GitHub Secrets](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to store application secrets required for the execution of the GitHub Workflows against specific environments.
 
 ### Webpack 
 

src/pages/guides/reference_documentation/index.md

@@ -31,7 +31,7 @@ title: Reference Documentation
       * [Configuration Library](https://github.com/adobe/aio-lib-core-config)
       * [Networking Library](https://github.com/adobe/aio-lib-core-networking)
       * [Token-Vending Machine Client Library](https://github.com/adobe/aio-lib-core-tvm)
-* [Github Actions Support](https://github.com/features/actions)
-    * [Github Action to setup the CLI](https://github.com/adobe/aio-cli-setup-action)
-    * [Github Action to use the CLI](https://github.com/adobe/aio-apps-action)
-    * [Github workflow generator for App Builder Apps](https://github.com/adobe/generator-aio-app/tree/master/generators/add-ci/.github/workflows)
+* [GitHub Actions Support](https://github.com/features/actions)
+    * [GitHub Action to setup the CLI](https://github.com/adobe/aio-cli-setup-action)
+    * [GitHub Action to use the CLI](https://github.com/adobe/aio-apps-action)
+    * [GitHub workflow generator for App Builder Apps](https://github.com/adobe/generator-aio-app/tree/master/generators/add-ci/.github/workflows)

src/pages/resources/ci-cd/index.md

@@ -20,7 +20,7 @@ App Builder allows you to manage multiple environments called workspaces. Each w
 
 We recommend to go through the [App Builder CI/CD documentation](../../guides/deployment/ci_cd_for_firefly_apps.md) to learn more about the architectural details.
 
-This codelab will show you how to create a CI/CD worflow for a stage and production environment using [Github actions](https://github.com/features/actions) within an App Builder App.   
+This codelab will show you how to create a CI/CD worflow for a stage and production environment using [GitHub actions](https://github.com/features/actions) within an App Builder App.   
 
 For that, we'll use the default bootstrapped App Builder project provided via the [CLI](https://github.com/adobe/aio-cli) which provides a sample CI/CD workflow out-of-the-box.  
 

src/pages/resources/videos/exploring/ci-cd.md

@@ -1,6 +1,6 @@
 ---
 title: Exploring App Builder - CI/CD
-description: Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up Github CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation. 
+description: Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up GitHub CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation. 
 keywords:
   - Adobe I/O
   - Extensibility
@@ -10,7 +10,7 @@ keywords:
 
 # Exploring App Builder - CI/CD
 
-Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up Github CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation.
+Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up GitHub CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation.
 
 <Media slots="video"/>
 

src/pages/resources/videos/index.md

@@ -100,7 +100,7 @@ Join us as we dive deep into the topic of Adobe I/O Events including our new fea
 
 [Watch (51mins)](exploring/ci-cd.md)
 
-Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up Github CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation.
+Manik Jindal, App Builder Product Manager, will dive into CI/CD. You'll learn how to set up GitHub CI/CD we include with App Builder. In addition, we'll cover how to setup  a custom CI/CD pipeline with your tool of choice. Bring your questions and the App Builder team will be happy to answer any and all after the presentation.