From 50f62637fb987a3e3509f206b01c493c40d05c6b Mon Sep 17 00:00:00 2001
From: Ruofeng Lei <lrf0829@126.com>
Date: Fri, 8 May 2020 16:48:17 +0800
Subject: [PATCH] fix typo in static-pod.md

---
 content/zh/docs/tasks/configure-pod-container/static-pod.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh/docs/tasks/configure-pod-container/static-pod.md b/content/zh/docs/tasks/configure-pod-container/static-pod.md
index 1b28a77379..80178eb3fc 100644
--- a/content/zh/docs/tasks/configure-pod-container/static-pod.md
+++ b/content/zh/docs/tasks/configure-pod-container/static-pod.md
@@ -163,7 +163,7 @@ For example, this is how to start a simple web server as a static Pod:
 
 <!--
 1. Restart the kubelet. On Fedora, you would run:
-   
+
     ```shell
     # Run this command on the node where the kubelet is running
     systemctl restart kubelet
@@ -185,7 +185,7 @@ Similar to how [filesystem-hosted manifests](#configuration-files) work, the kub
 refetches the manifest on a schedule. If there are changes to the list of static
 Pods, the kubelet applies them.
 
-To use this approach: 
+To use this approach:
 -->
 
 ### Web 网上的静态 Pod 声明文件 {#pods-created-via-http}
@@ -262,7 +262,7 @@ The output might be something like:
 
 当 kubelet 启动时，会自动启动所有定义的静态 Pod。当定义了一个静态 Pod 并重新启动 kubelet 时，新的静态 Pod 就应该已经在运行了。
 
-可以在节点上云心下面的命令来看运行的容器（包括静态 Pod）：
+可以在节点上运行下面的命令来看运行的容器（包括静态 Pod）：
 ```shell
 # 在 kubelet 运行的节点上执行以下命令
 docker ps