From 57a4c073518400b5af25d558ccb8494390a45ae5 Mon Sep 17 00:00:00 2001 From: Vladimir Rutsky Date: Wed, 24 Feb 2016 17:19:42 +0300 Subject: [PATCH] fix identation in list tabs were replaces with 4 spaces --- docs/user-guide/kubectl-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/kubectl-overview.md b/docs/user-guide/kubectl-overview.md index afac897efaa..4fb305a6dfa 100644 --- a/docs/user-guide/kubectl-overview.md +++ b/docs/user-guide/kubectl-overview.md @@ -82,12 +82,12 @@ where `command`, `TYPE`, `NAME`, and `flags` are: When performing an operation on multiple resources, you can specify each resource by type and name or specify one or more files: * To specify resources by type and name: - * To group resources if they are all the same type: `TYPE1 name1 name2 name<#>`
+ * To group resources if they are all the same type: `TYPE1 name1 name2 name<#>`
Example: `$ kubectl get pod example-pod1 example-pod2` * To specify multiple resource types individually: `TYPE1/name1 TYPE1/name2 TYPE2/name3 TYPE<#>/name<#>`
Example: `$ kubectl get pod/example-pod1 replicationcontroller/example-rc1` * To specify resources with one or more files: `-f file1 -f file2 -f file<#>` - [Use YAML rather than JSON](config-best-practices.md#general-config-tips) since YAML tends to be more user-friendly, especially for configuration files.
+ [Use YAML rather than JSON](config-best-practices.md#general-config-tips) since YAML tends to be more user-friendly, especially for configuration files.
Example: `$ kubectl get pod -f ./pod.yaml` * `flags`: Specifies optional flags. For example, you can use the `-s` or `--server` flags to specify the address and port of the Kubernetes API server.
**Important**: Flags that you specify from the command line override default values and any corresponding environment variables.