From c6694718235f435214384892e4431097a152a799 Mon Sep 17 00:00:00 2001
From: ydFu <ader.ydfu@gmail.com>
Date: Tue, 26 Jan 2021 09:12:56 +0800
Subject: [PATCH] [zh] update Sync concepts pages for secret and ingress

* sync with english version in secret.md and ingress.md
---
 content/zh/docs/concepts/configuration/secret.md        | 2 +-
 content/zh/docs/concepts/services-networking/ingress.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh/docs/concepts/configuration/secret.md b/content/zh/docs/concepts/configuration/secret.md
index e4c1abd2275f5..f1f950ac3e929 100644
--- a/content/zh/docs/concepts/configuration/secret.md
+++ b/content/zh/docs/concepts/configuration/secret.md
@@ -494,7 +494,7 @@ SSH 私钥自身无法建立 SSH 客户端与服务器端之间的可信连接
 <!--
 ### TLS secrets
 
-Kubernetes provides a builtin Secret type `kubernetes.io/tls` for to storing
+Kubernetes provides a builtin Secret type `kubernetes.io/tls` for storing
 a certificate and its associated key that are typically used for TLS . This
 data is primarily used with TLS termination of the Ingress resource, but may
 be used with other resources or directly by a workload.
diff --git a/content/zh/docs/concepts/services-networking/ingress.md b/content/zh/docs/concepts/services-networking/ingress.md
index e3dd00dede437..97304e33cccfa 100644
--- a/content/zh/docs/concepts/services-networking/ingress.md
+++ b/content/zh/docs/concepts/services-networking/ingress.md
@@ -651,12 +651,12 @@ Ingress 控制器 IP 地址的任何网络流量，而无需基于名称的虚
 
 <!-- 
 For example, the following Ingress routes traffic
-requested for `first.bar.com` to `service1`, `second.foo.com` to `service2`, and any traffic
+requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic
 to the IP address without a hostname defined in request (that is, without a request header being
 presented) to `service3`.
 -->
 例如，以下 Ingress 会将针对 `first.bar.com` 的请求流量路由到 `service1`，
-将针对 `second.foo.com` 的请求流量路由到 `service2`，
+将针对 `second.bar.com` 的请求流量路由到 `service2`，
 而针对该 IP 地址的、没有在请求中定义主机名的请求流量会被路由（即，不提供请求标头）
 到 `service3`。