Merge pull request #246 from kakabisht/fix-minor-typos-links

Fixing broken links

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.
 

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)
 

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.
 

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.
 

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.
 

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)
 

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.
 

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.
 

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.
 

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.