fix lint

Signed-off-by: LiZhenCheng9527 <lizhencheng6@huawei.com>

Author: LiZhenCheng9527

docs/content/en/docs/Integrations/karmada.md

@@ -18,7 +18,7 @@ cd kurator
 hack/local-dev-setup.sh
 ```
 
-> `fs.inotify.max_user_watches` and `fs.inotify.max_user_instances` may need to be adjusted as described [here](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files)
+> `fs.inotify.max_user_watches` and `fs.inotify.max_user_instances` may need to be adjusted as [described](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files)
 
 ### Deploy Karmada
 

docs/content/en/docs/Integrations/pixie-vizier.md

@@ -33,7 +33,7 @@ After sign in, visit [pixie admin page](https://work.withpixie.ai/admin) for nex
 
 ## Create deployment key
 
-Create a deployment key following the directions [here](https://docs.pixielabs.ai/reference/admin/deploy-keys/#create-a-deploy-key-using-the-live-ui).
+Create a deployment key following the [direction](https://docs.pixielabs.ai/reference/admin/deploy-keys/#create-a-deploy-key-using-the-live-ui).
 
 ## Install Pixie Vizier
 

docs/content/en/docs/Integrations/thanos.md

@@ -20,7 +20,7 @@ Kurator provides a very simple command to install Thanos and add karmada-apiserv
 
 - `--kubeconfig` and `--context` specifies the cluster where Karmada Apiserver, Kurator use Karmada to orchestrate Thanos application.
 - `--host-kubeconfig` and `--host-context` specifies the cluster where to deploy Thanos itself, it is the host cluster that hold Thanos.
-- `--object-store-config` specifies the object store configuration used by Thanos, more details can be found [here](https://prometheus-operator.dev/docs/operator/thanos/#configuring-thanos-object-storage).
+- `--object-store-config` specifies the object store configuration used by Thanos, more details can be found in [Thanos docs](https://prometheus-operator.dev/docs/operator/thanos/#configuring-thanos-object-storage).
 
 ```bash
 kurator install thanos --host-kubeconfig /root/.kube/kurator-host.config --host-context kurator-host --object-store-config /root/thanos/thanos-config.yaml

docs/content/en/docs/cluster-operator/aws-irsa.md

@@ -10,7 +10,7 @@ In this tutorial we’ll cover the basics of how to use [Cluster API](https://gi
 
 ## Setup a cluster on AWS with IRSA enabled
 
-IRSA(IAM roles for service accounts) allows applications in a pod's containers can use an AWS SDK or the AWS CLI to make API requests to AWS services using AWS Identity and Access Management (IAM) permissions. More details can be found [here](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html).
+IRSA(IAM roles for service accounts) allows applications in a pod's containers can use an AWS SDK or the AWS CLI to make API requests to AWS services using AWS Identity and Access Management (IAM) permissions. More details can be found [EKS IAM roles for service accounts documentatio](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html).
 
 ### Setup cluster
 

docs/content/en/docs/cluster-operator/on-premise-cluster-lifecycle.md

@@ -79,7 +79,7 @@ ssh-privatekey:  2590 bytes
 
 ### Customize your cluster configuration
 
-You can find custom cluster examples [here](https://github.com/kurator-dev/kurator/tree/main/examples/infra/customcluster).
+You can find custom cluster [examples](https://github.com/kurator-dev/kurator/tree/main/examples/infra/customcluster).
 
 Here are the four types of resources needed for on-premise Kubernetes cluster provision：
 

docs/content/en/docs/fleet-manager/submariner-plugin.md

@@ -26,7 +26,7 @@ kubectl label node kurator-member2-control-plane submariner.io/gateway=true --ku
 
 ### Create a fleet with metric plugin enabled
 
-`SUBMARINER_PSK` needs to be set as described in [here](https://submariner.io/operations/deployment/helm/).
+`SUBMARINER_PSK` needs to be set as [described](https://submariner.io/operations/deployment/helm/).
 
 ```bash
 export SUBMARINER_PSK=$(LC_CTYPE=C tr -dc 'a-zA-Z0-9' < /dev/urandom | fold -w 64 | head -n 1)
@@ -77,7 +77,7 @@ Guides for you to clean up the fleets and plugins.
 
 ### 1. Cleanup the Submariner Plugin
 
-Tutorial for manual uninstallation can be found in Sumariner Documatation [here](https://submariner.io/operations/cleanup/#manual-uninstall).
+Tutorial for manual uninstallation can be found in [Sumariner Documatation](https://submariner.io/operations/cleanup/#manual-uninstall).
 
 > Deleting the cluster to start from scratch is **recommended** because potential crd dependencies conflicts and some hard-to-find legacy resources or settings.
 

docs/content/en/docs/setup/install-fleet-manager.md

@@ -12,7 +12,7 @@ Fleet manager depends on cluster operator, so refer to [Cluster operator install
 
 ## Install FluxCD with Helm
 
-Fleet manager depends on [Fluxcd](https://fluxcd.io/flux/), Kurator use helm chart from fluxcd community, more details can be found [here](https://github.com/fluxcd-community/helm-charts).
+Fleet manager depends on [Fluxcd](https://fluxcd.io/flux/), Kurator use helm chart from fluxcd community, more [details](https://github.com/fluxcd-community/helm-charts) can be found.
 
 Setup with following command:
 

docs/content/en/docs/setup/install-minio.md

@@ -8,7 +8,7 @@ description: >
 
 ## Install Minio with Helm
 
-Kurator use helm chart from bitnami, more details can be found [here](https://github.com/bitnami/charts).
+Kurator use helm chart from bitnami, more [details](https://github.com/bitnami/charts) can be found here.
 
 Setup [Minio](https://min.io/) with following command:
 

docs/content/en/references/backups_v1alpha1_types.html

@@ -213,8 +213,6 @@ <h3 id="backup.kurator.dev/v1alpha1.BackupPolicy">BackupPolicy
 </p>
 <p>Note: This code partly copied from <a href="https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/backup_types.go">https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/backup_types.go</a>
 Refer to: vmware-tanzu/velero
-Original license: Apache-2.0
-Copyright: Copyright &copy; 2017-2023 velero, Inc. All Rights Reserved.
 BackupPolicy defines the specification for a backup policy.</p>
 <div class="md-typeset__scrollwrap">
 <div class="md-typeset__table td-content">
@@ -865,9 +863,7 @@ <h3 id="backup.kurator.dev/v1alpha1.ResourceFilter">ResourceFilter
 <a href="#backup.kurator.dev/v1alpha1.RestorePolicy">RestorePolicy</a>)
 </p>
 <p>Note: partly copied from <a href="https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/backup_types.go">https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/backup_types.go</a>
-Refer to: vmware-tanzu/velero
-Original license: Apache-2.0
-Copyright: Copyright &copy; 2017-2023 velero, Inc. All Rights Reserved.</p>
+Refer to: vmware-tanzu/velero</p>
 <div class="md-typeset__scrollwrap">
 <div class="md-typeset__table td-content">
 <table>
@@ -1214,8 +1210,6 @@ <h3 id="backup.kurator.dev/v1alpha1.RestorePolicy">RestorePolicy
 </p>
 <p>Note: partly copied from <a href="https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/restore_types.go">https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/restore_types.go</a>
 Refer to: vmware-tanzu/velero
-Original license: Apache-2.0
-Copyright: Copyright &copy; 2017-2023 velero, Inc. All Rights Reserved.
 RestorePolicy defines the specification for a Velero restore.</p>
 <div class="md-typeset__scrollwrap">
 <div class="md-typeset__table td-content">

pkg/apis/backups/v1alpha1/backup_type.go

@@ -66,8 +66,6 @@ type BackupSpec struct {
 
 // Note: This code partly copied from https://github.com/vmware-tanzu/velero/blob/v1.11.1/pkg/apis/velero/v1/backup_types.go
 // Refer to: vmware-tanzu/velero
-// Original license: Apache-2.0
-// Copyright: Copyright (c) 2017-2023 velero, Inc. All Rights Reserved.
 // BackupPolicy defines the specification for a backup policy.
 type BackupPolicy struct {
 	// ResourceFilter specifies which resources should be included in the backup.