Skip to content

Commit 5fcc71a

Browse files
committed
[en] Correct incorrect expressions
Signed-off-by: xin.li
1 parent 2df0642 commit 5fcc71a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/en/docs/tasks/debug/debug-application/debug-pods.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -109,15 +109,15 @@ If your pod is not behaving as you expected, it may be that there was an error i
109109
pod description (e.g. `mypod.yaml` file on your local machine), and that the error
110110
was silently ignored when you created the pod. Often a section of the pod description
111111
is nested incorrectly, or a key name is typed incorrectly, and so the key is ignored.
112-
For example, if you misspelled `command` as `command` then the pod will be created but
112+
For example, if you misspelled `command` as `commnd` then the pod will be created but
113113
will not use the command line you intended it to use.
114114

115115
The first thing to do is to delete your pod and try creating it again with the `--validate` option.
116116
For example, run `kubectl apply --validate -f mypod.yaml`.
117-
If you misspelled `command` as `command` then will give an error like this:
117+
If you misspelled `command` as `commnd` then will give an error like this:
118118

119119
```shell
120-
I0805 10:43:25.129850 46757 schema.go:126] unknown field: command
120+
I0805 10:43:25.129850 46757 schema.go:126] unknown field: commnd
121121
I0805 10:43:25.129973 46757 schema.go:129] this may be a false alarm, see https://github.com/kubernetes/kubernetes/issues/6842
122122
pods/mypod
123123
```

0 commit comments

Comments
 (0)