From e4e7da3010eb44adfc0e5fbcf2620631219250b6 Mon Sep 17 00:00:00 2001
From: tanshanshan <tan.shanshan@zte.com.cn>
Date: Fri, 14 Sep 2018 11:30:27 +0800
Subject: [PATCH] fix the command output (#10285)

---
 content/en/docs/setup/multiple-zones.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/setup/multiple-zones.md b/content/en/docs/setup/multiple-zones.md
index 2a9c097cb1..70ca0fcf06 100644
--- a/content/en/docs/setup/multiple-zones.md
+++ b/content/en/docs/setup/multiple-zones.md
@@ -208,8 +208,8 @@ Now lets validate that Kubernetes automatically labeled the zone & region the PV
 
 ```shell
 > kubectl get pv --show-labels
-NAME           CAPACITY   ACCESSMODES   STATUS    CLAIM            REASON    AGE       LABELS
-pv-gce-mj4gm   5Gi        RWO           Bound     default/claim1             46s       failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a
+NAME           CAPACITY   ACCESSMODES   RECLAIM POLICY   STATUS    CLAIM            STORAGECLASS    REASON    AGE       LABELS
+pv-gce-mj4gm   5Gi        RWO           Retain           Bound     default/claim1   manual                    46s       failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a
 ```
 
 So now we will create a pod that uses the persistent volume claim.