From 177a1318ed3d785f236be281b118b5af4aa00532 Mon Sep 17 00:00:00 2001 From: Ader Date: Fri, 1 Jan 2021 11:35:26 +0800 Subject: [PATCH] Fix some typo in runtime-class.md . Uniform case and adjustment description for smoother writing. Signed-off-by: ydFu --- content/en/docs/concepts/containers/runtime-class.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/containers/runtime-class.md b/content/en/docs/concepts/containers/runtime-class.md index 1ba631e350..cb82d05f24 100644 --- a/content/en/docs/concepts/containers/runtime-class.md +++ b/content/en/docs/concepts/containers/runtime-class.md @@ -37,10 +37,10 @@ but with different settings. Ensure the RuntimeClass feature gate is enabled (it is by default). See [Feature Gates](/docs/reference/command-line-tools-reference/feature-gates/) for an explanation of enabling -feature gates. The `RuntimeClass` feature gate must be enabled on apiservers _and_ kubelets. +feature gates. The `RuntimeClass` feature gate must be enabled on API server _and_ kubelets. -1. Configure the CRI implementation on nodes (runtime dependent) -2. Create the corresponding RuntimeClass resources +1. Configure the CRI implementation on nodes (runtime dependent). +2. Create the corresponding RuntimeClass resources. ### 1. Configure the CRI implementation on nodes @@ -98,7 +98,7 @@ spec: # ... ``` -This will instruct the Kubelet to use the named RuntimeClass to run this pod. If the named +This will instruct the kubelet to use the named RuntimeClass to run this pod. If the named RuntimeClass does not exist, or the CRI cannot run the corresponding handler, the pod will enter the `Failed` terminal [phase](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase). Look for a corresponding [event](/docs/tasks/debug-application-cluster/debug-application-introspection/) for an