GitHub

docusaurus/docs/cypress/cookbook.md

@@ -59,7 +59,7 @@ You should replace `$MY_CI_BUILD_ID` with the correct environment variable provi
 | Codeship Pro   | `CI_BUILD_ID`            |
 | Drone          | `DRONE_BUILD_NUMBER`     |
 | Gitlab         | `CI_PIPELINE_ID`         |
-| Github Actions | `GITHUB_RUN_ID`          |
+| GitHub Actions | `GITHUB_RUN_ID`          |
 | Heroku         | `HEROKU_TEST_RUN_ID`     |
 | Jenkins        | `BUILD_NUMBER`           |
 | Semaphore 1.0  | `SEMAPHORE_BUILD_NUMBER` |

docusaurus/docs/ruby/puffing-billy.md

@@ -11,7 +11,7 @@ This is needed only if you are using Knapsack Pro in [Queue Mode](../overview/in
 
 :::
 
-If you use the [puffing-billy](https://github.com/oesmith/puffing-billy) gem and encounter the crash described in this [Github issue](https://github.com/oesmith/puffing-billy/issues/253), apply the following patch:
+If you use the [puffing-billy](https://github.com/oesmith/puffing-billy) gem and encounter the crash described in this [GitHub issue](https://github.com/oesmith/puffing-billy/issues/253), apply the following patch:
 
 ```ruby
 # rails_helper.rb or spec_helper.rb

docusaurus/docs/ruby/rspec.mdx

@@ -102,7 +102,7 @@ You need to install the [`rspec_junit_formatter`](https://github.com/sj26/rspec_
       end
       ```
 
-      `FINAL_REPORT` will contain all the tests run on the CI node (not just the last subset). For more information, you can read this [Github issue](https://github.com/KnapsackPro/knapsack_pro-ruby/issues/40).
+      `FINAL_REPORT` will contain all the tests run on the CI node (not just the last subset). For more information, you can read this [GitHub issue](https://github.com/KnapsackPro/knapsack_pro-ruby/issues/40).
 
       If your CI nodes write to the same disk, you need to append the CI node index to the solution presented above to avoid conflicts:
 
@@ -159,7 +159,7 @@ You need to install the [`rspec_junit_formatter`](https://github.com/sj26/rspec_
       end
       ```
 
-      `FINAL_REPORT` will contain all the tests run on the CI node (not just the last subset). For more information, you can read this [Github issue](https://github.com/KnapsackPro/knapsack_pro-ruby/issues/40).
+      `FINAL_REPORT` will contain all the tests run on the CI node (not just the last subset). For more information, you can read this [GitHub issue](https://github.com/KnapsackPro/knapsack_pro-ruby/issues/40).
 
       If your CI nodes write to the same disk, you need to append the CI node index to the solution presented above to avoid conflicts:
 

docusaurus/docs/ruby/troubleshooting.mdx

@@ -183,7 +183,7 @@ For example, you could use 600 seconds (10 minutes) if you know that your tests
 
 :::tip
 
-Check your CI provider documentation to configure a timeout if you worry about wasting resources on the hanging CI node. For example, Github Actions uses:
+Check your CI provider documentation to configure a timeout if you worry about wasting resources on the hanging CI node. For example, GitHub Actions uses:
 
 * [`jobs.<job_id>.timeout-minutes`](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) - The maximum number of minutes to let a job run before GitHub automatically cancels it.
 * [`jobs.<job_id>.steps[*].timeout-minutes`](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes) - The maximum number of minutes to run the step before killing the process.