fix space problems which ide results in

Signed-off-by: tim-zju <21651152@zju.edu.cn>
2016-12-22 20:01:22 +08:00
parent 1f7b3148f2
commit df7eb8128d
5 changed files with 42 additions and 42 deletions
@@ -194,7 +194,7 @@ Ideally, the rolling update controller would take application readiness into acc
 The two replication controllers would need to create pods with at least one differentiating label, such as the image tag of the primary container of the pod, since it is typically image updates that motivate rolling updates.

 Rolling update is implemented in the client tool
-[`kubectl rolling-update`](/docs/user-guide/kubectl/kubectl_rolling-update). Visit [`kubectl rolling-update` tutorial](/docs/user-guide/rolling-updates/) for more concrete examples.
+[`kubectl rolling-update`](/docs/user-guide/kubectl/kubectl_rolling-update). Visit [`kubectl rolling-update` tutorial](/docs/user-guide/rolling-updates/) for more concrete examples. 

 ### Multiple release tracks

@@ -239,7 +239,7 @@ Note that we recommend using Deployments instead of directly using Replica Sets,
 ### Deployment (Recommended)

 [`Deployment`](/docs/user-guide/deployments/) is a higher-level API object that updates its underlying Replica Sets and their Pods
-in a similar fashion as `kubectl rolling-update`. Deployments are recommended if you want this rolling update functionality,
+in a similar fashion as `kubectl rolling-update`. Deployments are recommended if you want this rolling update functionality, 
 because unlike `kubectl rolling-update`, they are declarative, server-side, and have additional features.

 ### Bare Pods