From 8537e3d552611c235839a23398bec7aa190c5684 Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Fri, 1 Jun 2018 15:03:52 -0700 Subject: [PATCH] Copyedit --- content/en/docs/reference/kubectl/overview.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/content/en/docs/reference/kubectl/overview.md b/content/en/docs/reference/kubectl/overview.md index 4f0a4cca56269..1d88c3cab8745 100644 --- a/content/en/docs/reference/kubectl/overview.md +++ b/content/en/docs/reference/kubectl/overview.md @@ -203,15 +203,18 @@ submit-queue 610995 This means that for any given resource, the server will return columns and rows relevant to that resource, for the client to print. This allows for consistent human-readable output across clients used against the same cluster, by having the server encapsulate the details of printing. -This feature is enabled by default as of `kubectl` v1.11, and can be optionally disabled by adding the `--server-print=false` flag to `kubectl get`. +This feature is enabled by default in `kubectl` 1.11 and higher. To disable it, add the +`--server-print=false` flag to the `kubectl get` command. ##### Examples +To print information about the status of a pod, use a command like the following: + ```shell -$ kubectl get pods --server-print=false +kubectl get pods --server-print=false ``` -The result of running this command is: +Output looks like this: ```shell NAME READY STATUS RESTARTS AGE