Merge pull request #1383 from btat/typo

Fix Tabs groupId typo + other typos
2026-05-01 18:53:13 +00:00 · 2024-07-15 17:15:57 -07:00
parent d754e9d5ee 822f8f4974
commit 2458b04c66
41 changed files with 52 additions and 52 deletions
@@ -214,7 +214,7 @@ kubectl -n cattle-system apply -R -f ./rancher

 ### E. For Rancher versions before v2.3.0, Configure System Charts

-If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../../resources/local-system-charts.md).
+If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in GitHub, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../../resources/local-system-charts.md).

 ### Additional Resources

@@ -334,7 +334,7 @@ docker run -d --restart=unless-stopped \

 If you are installing Rancher v2.3.0+, the installation is complete.

-If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../../resources/local-system-charts.md).
+If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in GitHub, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../../resources/local-system-charts.md).

 </TabItem>
 </Tabs>
@@ -221,7 +221,7 @@ kubectl -n cattle-system apply -R -f ./rancher

 ## 5. For Rancher versions before v2.3.0, Configure System Charts

-If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../resources/local-system-charts.md).
+If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in GitHub, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../resources/local-system-charts.md).

 ## Additional Resources

@@ -357,7 +357,7 @@ If you are installing Rancher v2.3.0+, the installation is complete.

 > **Note:** If you don't intend to send telemetry data, opt out [telemetry](../../../../faq/telemetry.md) during the initial login.

-If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../resources/local-system-charts.md).
+If you are installing Rancher versions before v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in GitHub, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts](../../resources/local-system-charts.md).

 </TabItem>
 </Tabs>
@@ -103,7 +103,7 @@ Rancher Server is distributed as a Docker image, which have tags attached to the
 | -------------------------- | ------ |
 | `rancher/rancher:latest`   | Our latest development release. These builds are validated through our CI automation framework. These releases are not recommended for production environments. |
 | `rancher/rancher:stable`   | Our newest stable release. This tag is recommended for production.                                                                                              |
-| `rancher/rancher:<v2.X.X>` | You can install specific versions of Rancher by using the tag from a previous release. See what's available at DockerHub.                                       |
+| `rancher/rancher:<v2.X.X>` | You can install specific versions of Rancher by using the tag from a previous release. See what's available at Docker Hub.                                       |

 > **Notes:**
 >
@@ -34,7 +34,7 @@ Currently, deployments pull the private registry credentials automatically only

 1. Select a **Scope** for the registry. You can either make the registry available for the entire project or a single namespace.

-1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry. For example, if you use DockerHub, provide your DockerHub username and password.
+1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry. For example, if you use Docker Hub, provide your Docker Hub username and password.

 1. Click **Save**.

@@ -542,7 +542,7 @@ For your convenience, the following variables are available for your pipeline co

 Variable Name           | Description
 ------------------------|------------------------------------------------------------
-`CICD_GIT_REPO_NAME`      | Repository name (Github organization omitted).
+`CICD_GIT_REPO_NAME`      | Repository name (GitHub organization omitted).
 `CICD_GIT_URL`            | URL of the Git repository.
 `CICD_GIT_COMMIT`         | Git commit ID being executed.
 `CICD_GIT_BRANCH`         | Git branch of this event.
@@ -86,7 +86,7 @@ Select your provider's tab below and follow the directions.

 1. Select **Tools > Pipelines** in the navigation bar. In versions before v2.2.0, you can select **Resources > Pipelines**.

-1. Follow the directions displayed to **Setup a Github application**. Rancher redirects you to Github to setup an OAuth App in Github.
+1. Follow the directions displayed to **Setup a GitHub application**. Rancher redirects you to GitHub to setup an OAuth App in GitHub.

 1. From GitHub, copy the **Client ID** and **Client Secret**. Paste them into Rancher.

@@ -111,7 +111,7 @@ For your convenience the following environment variables are available in your b

 Variable Name           | Description
 ------------------------|------------------------------------------------------------
-CICD_GIT_REPO_NAME      | Repository Name (Stripped of Github Organization)
+CICD_GIT_REPO_NAME      | Repository Name (Stripped of GitHub Organization)
 CICD_PIPELINE_NAME      | Name of the pipeline
 CICD_GIT_BRANCH         | Git branch of this event
 CICD_TRIGGER_TYPE       | Event that triggered the build