From b57d4ca91f6acffe776f3edd5042a0a31f7aa58a Mon Sep 17 00:00:00 2001 From: hridyesh bisht Date: Mon, 12 May 2025 13:39:01 +0530 Subject: [PATCH] Fixing broken links --- docs/cluster-registration.md | 2 +- docs/uninstall.md | 2 +- versioned_docs/version-0.10/cluster-registration.md | 2 +- versioned_docs/version-0.11/cluster-registration.md | 2 +- versioned_docs/version-0.12/cluster-registration.md | 2 +- versioned_docs/version-0.12/uninstall.md | 2 +- versioned_docs/version-0.6/cluster-registration.md | 2 +- versioned_docs/version-0.7/cluster-registration.md | 2 +- versioned_docs/version-0.8/cluster-registration.md | 2 +- versioned_docs/version-0.9/cluster-registration.md | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/cluster-registration.md b/docs/cluster-registration.md index 25b20063a..f57749d73 100644 --- a/docs/cluster-registration.md +++ b/docs/cluster-registration.md @@ -172,7 +172,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/docs/uninstall.md b/docs/uninstall.md index c07c8ee43..f32a7a3d8 100644 --- a/docs/uninstall.md +++ b/docs/uninstall.md @@ -59,5 +59,5 @@ kubectl delete ns -l "fleet.cattle.io/managed=true" Fleet in Rancher cannot be uninstalled, without uninstalling Rancher. However, the GitOps feature can be disabled. When disabled, the gitjob deployment is no longer deployed into the Rancher server’s local cluster, and continuous-delivery is not shown in the Rancher UI. -More information can be found in the Rancher docs, e.g. https://documentation.suse.com/cloudnative/rancher-manager/latest/en/rancher-admin/experimental-features/continuous-delivery.html +For more information, refer to [Continuous Delivery in Rancher](https://documentation.suse.com/cloudnative/rancher-manager/latest/en/rancher-admin/experimental-features/continuous-delivery.html) diff --git a/versioned_docs/version-0.10/cluster-registration.md b/versioned_docs/version-0.10/cluster-registration.md index 5104405bc..c84261f13 100644 --- a/versioned_docs/version-0.10/cluster-registration.md +++ b/versioned_docs/version-0.10/cluster-registration.md @@ -170,7 +170,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.11/cluster-registration.md b/versioned_docs/version-0.11/cluster-registration.md index 25b20063a..f57749d73 100644 --- a/versioned_docs/version-0.11/cluster-registration.md +++ b/versioned_docs/version-0.11/cluster-registration.md @@ -172,7 +172,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.12/cluster-registration.md b/versioned_docs/version-0.12/cluster-registration.md index 25b20063a..f57749d73 100644 --- a/versioned_docs/version-0.12/cluster-registration.md +++ b/versioned_docs/version-0.12/cluster-registration.md @@ -172,7 +172,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.12/uninstall.md b/versioned_docs/version-0.12/uninstall.md index c07c8ee43..f32a7a3d8 100644 --- a/versioned_docs/version-0.12/uninstall.md +++ b/versioned_docs/version-0.12/uninstall.md @@ -59,5 +59,5 @@ kubectl delete ns -l "fleet.cattle.io/managed=true" Fleet in Rancher cannot be uninstalled, without uninstalling Rancher. However, the GitOps feature can be disabled. When disabled, the gitjob deployment is no longer deployed into the Rancher server’s local cluster, and continuous-delivery is not shown in the Rancher UI. -More information can be found in the Rancher docs, e.g. https://documentation.suse.com/cloudnative/rancher-manager/latest/en/rancher-admin/experimental-features/continuous-delivery.html +For more information, refer to [Continuous Delivery in Rancher](https://documentation.suse.com/cloudnative/rancher-manager/latest/en/rancher-admin/experimental-features/continuous-delivery.html) diff --git a/versioned_docs/version-0.6/cluster-registration.md b/versioned_docs/version-0.6/cluster-registration.md index bd992418b..5b358c396 100644 --- a/versioned_docs/version-0.6/cluster-registration.md +++ b/versioned_docs/version-0.6/cluster-registration.md @@ -162,7 +162,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.7/cluster-registration.md b/versioned_docs/version-0.7/cluster-registration.md index 3a7b78a0c..a5966b44f 100644 --- a/versioned_docs/version-0.7/cluster-registration.md +++ b/versioned_docs/version-0.7/cluster-registration.md @@ -170,7 +170,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.8/cluster-registration.md b/versioned_docs/version-0.8/cluster-registration.md index 5104405bc..c84261f13 100644 --- a/versioned_docs/version-0.8/cluster-registration.md +++ b/versioned_docs/version-0.8/cluster-registration.md @@ -170,7 +170,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID. diff --git a/versioned_docs/version-0.9/cluster-registration.md b/versioned_docs/version-0.9/cluster-registration.md index 5104405bc..c84261f13 100644 --- a/versioned_docs/version-0.9/cluster-registration.md +++ b/versioned_docs/version-0.9/cluster-registration.md @@ -170,7 +170,7 @@ spec: clientID: "really-random" ``` -Second, follow the [cluster registration token instructions]((#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. +Second, follow the [cluster registration token instructions](#create-cluster-registration-tokens) to obtain the `values.yaml` file to be used. Third, setup your environment to use the client ID.