From 6b02e280d88c0fc20b18a25edd0355835e4cf92e Mon Sep 17 00:00:00 2001
From: chenhuan12 <Chen.huan@zte.com.cn>
Date: Thu, 30 Mar 2017 15:17:15 +0800
Subject: [PATCH] fix typo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

1、fix command kubectl get crontab output
2、fix command kubectl get crontab -o json output
---
 docs/user-guide/thirdpartyresources.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/user-guide/thirdpartyresources.md b/docs/user-guide/thirdpartyresources.md
index 21728f3021..86f969183b 100644
--- a/docs/user-guide/thirdpartyresources.md
+++ b/docs/user-guide/thirdpartyresources.md
@@ -89,8 +89,8 @@ You can then manage our `CronTab` objects using kubectl. Note that resource name
 
 ```shell
 $ kubectl get crontab
-NAME                 LABELS    DATA
-my-new-cron-object   <none>    {"apiVersion":"stable.example.com/v1","cronSpec":"...
+NAME                 KIND
+my-new-cron-object   CronTab.v1.stable.example.com
 ```
 
 You can also view the raw JSON data. Here you can see that it contains the custom `cronSpec` and `image` fields from the yaml you used to create it:
@@ -98,9 +98,7 @@ You can also view the raw JSON data. Here you can see that it contains the custo
 ```yaml
 $ kubectl get crontab -o json
 {
-    "kind": "List",
     "apiVersion": "v1",
-    "metadata": {},
     "items": [
         {
             "apiVersion": "stable.example.com/v1",
@@ -117,5 +115,9 @@ $ kubectl get crontab -o json
             }
         }
     ]
+    "kind": "List",
+    "metadata": {},
+    "resourceVersion": "",
+    "selfLink": ""
 }
 ```