From 8e0cab2d649c3453de2a13a66a2b76ed5e589967 Mon Sep 17 00:00:00 2001
From: Kohei Toyoda <k-toyoda@pi.jp.nec.com>
Date: Thu, 9 May 2019 14:22:48 +0900
Subject: [PATCH] consistent order in yaml and json for multiple-zones.md
 (#14242)

---
 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 4beab2b3b9..3b2f75fa4f 100644
--- a/content/en/docs/setup/multiple-zones.md
+++ b/content/en/docs/setup/multiple-zones.md
@@ -191,8 +191,8 @@ Create a volume using the dynamic volume creation (only PersistentVolumes are su
 ```json
 kubectl apply -f - <<EOF
 {
-  "kind": "PersistentVolumeClaim",
   "apiVersion": "v1",
+  "kind": "PersistentVolumeClaim",
   "metadata": {
     "name": "claim1",
     "annotations": {
@@ -241,8 +241,8 @@ this means that this pod can only be created in the same zone as the volume:
 
 ```yaml
 kubectl apply -f - <<EOF
-kind: Pod
 apiVersion: v1
+kind: Pod
 metadata:
   name: mypod
 spec: