diff --git a/content/zh/docs/reference/issues-security/issues.md b/content/zh/docs/reference/issues-security/issues.md
index b225f9cc1f..e43fa3d0e6 100644
--- a/content/zh/docs/reference/issues-security/issues.md
+++ b/content/zh/docs/reference/issues-security/issues.md
@@ -1,7 +1,7 @@
 ---
 title: Kubernetes 问题追踪
 weight: 10
-aliases: [/cve/,/cves/]
+aliases: [cve/,cves/]
 ---
 
 <!--
diff --git a/content/zh/docs/reference/issues-security/security.md b/content/zh/docs/reference/issues-security/security.md
index 2ade5c4691..3d773ab822 100644
--- a/content/zh/docs/reference/issues-security/security.md
+++ b/content/zh/docs/reference/issues-security/security.md
@@ -1,6 +1,6 @@
 ---
 title: Kubernetes 安全和信息披露
-aliases: [/security/]
+aliases: [security/]
 content_template: templates/concept
 weight: 20
 ---
@@ -127,7 +127,7 @@ A public disclosure date is negotiated by the Kubernetes product security team a
 公开披露日期由 Kubernetes 产品安全团队和 bug 提交者协商。我们倾向于在用户缓解措施可用时尽快完全披露该 bug。
 
 <!--
-It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. 
+It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination.
 -->
 当 bug 或其修复还没有被完全理解，解决方案没有经过良好的测试，或者为了处理供应商协调问题时，延迟披露是合理的。