Fix typo (#2407) (#2408)

pingcap · Jul 11, 2023 · 63aa4e4 · 63aa4e4
1 parent f42f72e
commit 63aa4e4
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 12 deletions.
diff --git a/en/deploy-tidb-monitor-across-multiple-kubernetes.md b/en/deploy-tidb-monitor-across-multiple-kubernetes.md
@@ -65,12 +65,12 @@ For the deployment instructions of Thanos Receiver, refer to [kube-thanos](https
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer:
@@ -152,12 +152,12 @@ For the deployment instructions of Thanos Query, refer to [kube-thanos](https://
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer:
@@ -241,12 +241,12 @@ You need to configure the network and DNS of the Kubernetes clusters so that the
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer:

diff --git a/zh/deploy-tidb-monitor-across-multiple-kubernetes.md b/zh/deploy-tidb-monitor-across-multiple-kubernetes.md
@@ -65,12 +65,12 @@ Push 方式指利用 Prometheus remote-write 的特性，使位于不同 Kuberne
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer:
@@ -149,12 +149,12 @@ Pull 方式是指从不同 Kubernetes 集群的 Prometheus 实例中拉取监控
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer:
@@ -235,12 +235,12 @@ Pull 方式是指从不同 Kubernetes 集群的 Prometheus 实例中拉取监控
       - name: ${cluster_name}
         namespace: ${cluster_namespace}
       externalLabels:
-        # k8s_clsuter indicates the k8s cluster name, you can change
+        # k8s_cluster indicates the k8s cluster name, you can change
         # the label's name on your own, but you should notice that the
         # "cluster" label has been used by the TiDB metrics already.
         # For more information, please refer to the issue
         # https://github.com/pingcap/tidb-operator/issues/4219.
-        k8s_clsuter: ${kubernetes_cluster_name}
+        k8s_cluster: ${kubernetes_cluster_name}
         # add other meta labels here
         #region: us-east-1
       initializer: