From 3d68ac0f75502435c3363ca1bdbb88d092500caa Mon Sep 17 00:00:00 2001
From: Ran <huangran.alex@gmail.com>
Date: Thu, 25 Jan 2024 11:09:08 +0800
Subject: [PATCH] Update zh/deploy-tiproxy.md

---
 zh/deploy-tiproxy.md | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/zh/deploy-tiproxy.md b/zh/deploy-tiproxy.md
index 127a22e1e..8162ca9a5 100644
--- a/zh/deploy-tiproxy.md
+++ b/zh/deploy-tiproxy.md
@@ -59,20 +59,20 @@ summary: 了解如何在 Kubernetes 上为已有 TiDB 集群部署负载均衡 T
 
     + 如果开启了[集群 TLS](enable-tls-between-components.md)，则跳过这一步；如果没有开启集群 TLS，还需要生成自签名证书，并手动配置 TiDB 的 [`session-token-signing-cert`](https://docs.pingcap.com/zh/tidb/stable/tidb-configuration-file#session-token-signing-cert-从-v640-版本开始引入) 和 [`session-token-signing-key`](https://docs.pingcap.com/zh/tidb/stable/tidb-configuration-file#session-token-signing-key-从-v640-版本开始引入)：
 
-       ```yaml
-       spec:
-         tidb:
-           additionalVolumes:
-             - name: sessioncert
-               secret:
-                 secretName: sessioncert-secret
-           additionalVolumeMounts:
-             - name: sessioncert
-               mountPath: /var/session
-           config: |
-             session-token-signing-cert = "/var/session/tls.crt"
-             session-token-signing-key = "/var/session/tls.key"
-       ```
+        ```yaml
+        spec:
+          tidb:
+            additionalVolumes:
+              - name: sessioncert
+                secret:
+                  secretName: sessioncert-secret
+            additionalVolumeMounts:
+              - name: sessioncert
+                mountPath: /var/session
+            config: |
+              session-token-signing-cert = "/var/session/tls.crt"
+              session-token-signing-key = "/var/session/tls.key"
+        ```
 
        详见 TiDB 配置文档 [`session-token-signing-key`](https://docs.pingcap.com/zh/tidb/v7.6/tidb-configuration-file#session-token-signing-cert-从-v640-版本开始引入)。