From c739e66c5af91ef5f6aa153675ff339a12ee595e Mon Sep 17 00:00:00 2001
From: Kenichi Omichi <ken-oomichi@wx.jp.nec.com>
Date: Thu, 9 May 2019 18:17:58 -0700
Subject: [PATCH] Fix orders of yaml of custom-resource-definitions (#14254)

The orders of kind and metadata were inconsistent, and that made the
doc unreadable.
This fixes the orders in consistent way.
---
 .../custom-resources/custom-resource-definitions.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md b/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md
index 29af0df9d8..00b9a7919b 100644
--- a/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md
+++ b/content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions.md
@@ -142,6 +142,7 @@ from the yaml you used to create it:
 
 ```console
 apiVersion: v1
+kind: List
 items:
 - apiVersion: stable.example.com/v1
   kind: CronTab
@@ -156,7 +157,6 @@ items:
   spec:
     cronSpec: '* * * * */5'
     image: my-awesome-cron-image
-kind: List
 metadata:
   resourceVersion: ""
   selfLink: ""