[zh] fix links in concept section

content/zh/docs/concepts/cluster-administration/logging.md

@@ -274,7 +274,7 @@ Using a node-level logging agent is the most common and encouraged approach for
 Kubernetes doesn't specify a logging agent, but two optional logging agents are packaged with the Kubernetes release: [Stackdriver Logging](/docs/user-guide/logging/stackdriver) for use with Google Cloud Platform, and [Elasticsearch](/docs/user-guide/logging/elasticsearch). You can find more information and instructions in the dedicated documents. Both use [fluentd](http://www.fluentd.org/) with custom configuration as an agent on the node.
 -->
 Kubernetes 并不指定日志代理，但是有两个可选的日志代理与 Kubernetes 发行版一起发布。
-[Stackdriver 日志](/zh/docs/tasks/debug-application-cluster/logging-stackdriver/)
+[Stackdriver 日志](/docs/tasks/debug-application-cluster/logging-stackdriver/)
 适用于 Google Cloud Platform，和
 [Elasticsearch](/zh/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/)。
 你可以在专门的文档中找到更多的信息和说明。
@@ -447,7 +447,7 @@ which uses fluentd as a logging agent. Here are two configuration files that
 you can use to implement this approach. The first file contains
 a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) to configure fluentd.
 -->
-例如，你可以使用 [Stackdriver](/zh/docs/tasks/debug-application-cluster/logging-stackdriver/)，
+例如，你可以使用 [Stackdriver](/docs/tasks/debug-application-cluster/logging-stackdriver/)，
 它使用 fluentd 作为日志记录代理。
 以下是两个可用于实现此方法的配置文件。
 第一个文件包含配置 fluentd 的