From a66263c857ecfa9927cdb4361a3303b73ceb81a2 Mon Sep 17 00:00:00 2001
From: shenshaojun1993 <137772740@qq.com>
Date: Fri, 13 May 2022 11:12:55 +0800
Subject: [PATCH] Update logging.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

“使用节点级日志代理” 章节存在错误词，“群集级”应为“集群级”
---
 content/zh/docs/concepts/cluster-administration/logging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh/docs/concepts/cluster-administration/logging.md b/content/zh/docs/concepts/cluster-administration/logging.md
index a4732cbe61..2442b0506c 100644
--- a/content/zh/docs/concepts/cluster-administration/logging.md
+++ b/content/zh/docs/concepts/cluster-administration/logging.md
@@ -280,7 +280,7 @@ While Kubernetes does not provide a native solution for cluster-level logging, t
 <!--
 You can implement cluster-level logging by including a _node-level logging agent_ on each node. The logging agent is a dedicated tool that exposes logs or pushes logs to a backend. Commonly, the logging agent is a container that has access to a directory with log files from all of the application containers on that node.
 -->
-你可以通过在每个节点上使用 _节点级的日志记录代理_ 来实现群集级日志记录。
+你可以通过在每个节点上使用 _节点级的日志记录代理_ 来实现集群级日志记录。
 日志记录代理是一种用于暴露日志或将日志推送到后端的专用工具。
 通常，日志记录代理程序是一个容器，它可以访问包含该节点上所有应用程序容器的日志文件的目录。