From 5bb121ca5d34de3a32f17bd2abd07b32743e6ea4 Mon Sep 17 00:00:00 2001
From: my-git9 <76980726+my-git9@users.noreply.github.com>
Date: Mon, 7 Mar 2022 21:42:07 +0800
Subject: [PATCH] Update endpoint-slices.md

sync doc about endpoint-slices
Signed-off-by: LI XIN <xin.li@daocloud.io>
---
 .../zh/docs/concepts/services-networking/endpoint-slices.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh/docs/concepts/services-networking/endpoint-slices.md b/content/zh/docs/concepts/services-networking/endpoint-slices.md
index c6d6c62d44..447caae39c 100644
--- a/content/zh/docs/concepts/services-networking/endpoint-slices.md
+++ b/content/zh/docs/concepts/services-networking/endpoint-slices.md
@@ -257,9 +257,9 @@ the dedicated fields `nodeName` and `zone`.
 
 <!--
 Setting arbitrary topology fields on the `endpoint` field of an `EndpointSlice`
-resource has been deprecated and is not be supported in the v1 API. Instead,
-the v1 API supports setting individual `nodeName` and `zone` fields. These
-fields are automatically translated between API versions. For example, the
+resource has been deprecated and is not supported in the v1 API. 
+Instead, the v1 API supports setting individual `nodeName` and `zone` fields. 
+These fields are automatically translated between API versions. For example, the
 value of the `"topology.kubernetes.io/zone"` key in the `topology` field in
 the v1beta1 API is accessible as the `zone` field in the v1 API.
 -->