From 6a53b19abe3701cf5c8dbaadb5c1c41af43c1a5c Mon Sep 17 00:00:00 2001
From: wwgfhf <51694849+wwgfhf@users.noreply.github.com>
Date: Wed, 29 Apr 2020 11:18:13 +0800
Subject: [PATCH] Update apparmor.md

---
 content/zh/docs/tutorials/clusters/apparmor.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh/docs/tutorials/clusters/apparmor.md b/content/zh/docs/tutorials/clusters/apparmor.md
index 204ce7964e..655eec5db1 100644
--- a/content/zh/docs/tutorials/clusters/apparmor.md
+++ b/content/zh/docs/tutorials/clusters/apparmor.md
@@ -214,7 +214,7 @@ specifies the profile to apply. The `profile_ref` can be one of: -->
 <!-- Kubernetes AppArmor enforcement works by first checking that all the prerequisites have been
 met, and then forwarding the profile selection to the container runtime for enforcement. If the
 prerequisites have not been met, the Pod will be rejected, and will not run. -->
-Kubernetes AppArmor 强制首先通过检查所有先决条件都已满足，然后将配置文件选择转发到容器运行时进行强制。如果未满足先决条件， Pod 将被拒绝，并且不会运行。
+Kubernetes AppArmor 强制执行方式首先通过检查所有先决条件都已满足，然后将配置文件选择转发到容器运行时进行强制执行。如果未满足先决条件， Pod 将被拒绝，并且不会运行。
 
 <!-- To verify that the profile was applied, you can look for the AppArmor security option listed in the container created event: -->
 要验证是否应用了配置文件，可以查找容器创建事件中列出的 AppArmor 安全选项：