From 36c8643aa0bf7c72e1c4ea985e442edb94527f94 Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Fri, 4 Oct 2024 22:32:32 +0800
Subject: [PATCH] [zh-cn]sync setup-ha-etcd-with-kubeadm apparmor

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../tools/kubeadm/setup-ha-etcd-with-kubeadm.md      | 12 ------------
 content/zh-cn/docs/tutorials/security/apparmor.md    |  2 +-
 2 files changed, 1 insertion(+), 13 deletions(-)

diff --git a/content/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md b/content/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
index 7d752b1e6bdf9..abf59408acdac 100644
--- a/content/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
+++ b/content/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
@@ -13,18 +13,6 @@ weight: 70
 
 <!-- overview -->
 
-{{< note >}}
-<!--
-While kubeadm is being used as the management tool for external etcd nodes
-in this guide, please note that kubeadm does not plan to support certificate rotation
-or upgrades for such nodes. The long-term plan is to empower the tool
-[etcdadm](https://github.com/kubernetes-sigs/etcdadm) to manage these
-aspects.
--->
-在本指南中，使用 kubeadm 作为外部 etcd 节点管理工具，请注意 kubeadm 不计划支持此类节点的证书更换或升级。
-对于长期规划是使用 [etcdadm](https://github.com/kubernetes-sigs/etcdadm) 增强工具来管理这些方面。
-{{< /note >}}
-
 <!--
 By default, kubeadm runs a local etcd instance on each control plane node.
 It is also possible to treat the etcd cluster as external and provision
diff --git a/content/zh-cn/docs/tutorials/security/apparmor.md b/content/zh-cn/docs/tutorials/security/apparmor.md
index 072ea4b1a76fd..d450b5ab735c7 100644
--- a/content/zh-cn/docs/tutorials/security/apparmor.md
+++ b/content/zh-cn/docs/tutorials/security/apparmor.md
@@ -220,7 +220,7 @@ profile k8s-apparmor-example-deny-write flags=(attach_disconnected) {
 ```
 
 <!--
-The profile needs to loaded onto all nodes, since you don't know where the pod will be scheduled.
+The profile needs to be loaded onto all nodes, since you don't know where the pod will be scheduled.
 For this example we'll use SSH to install the profiles, but other approaches are
 discussed in [Setting up nodes with profiles](#setting-up-nodes-with-profiles).
 -->