Fix SeccompDefault feature name

We should mention the feature `SeccompDefault` rather than "Seccomp defaulting" to not confuse readers. Signed-off-by: Sascha Grunert <[email protected]>
kubernetes · Jul 18, 2022 · 0280fe7 · 0280fe7
1 parent 27658d9
commit 0280fe7
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/content/en/docs/tutorials/security/seccomp.md b/content/en/docs/tutorials/security/seccomp.md
@@ -201,14 +201,14 @@ You can find more detailed information about a possible upgrade and downgrade st
 in the related Kubernetes Enhancement Proposal (KEP):
 [Enable seccomp by default](https://github.com/kubernetes/enhancements/tree/9a124fd29d1f9ddf2ff455c49a630e3181992c25/keps/sig-node/2413-seccomp-by-default#upgrade--downgrade-strategy).
 
-Seccomp defaulting for Pods is a beta feature in Kubernetes {{< skew currentVersion >}}, 
+SeccompDefault for Pods is a beta feature in Kubernetes {{< skew currentVersion >}}, 
 and the corresponding `SeccompDefault` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
 is enabled by default. However, you still need to enable this defaulting for each node where
 you would like to use it.
 
 If you are running a Kubernetes {{< skew currentVersion >}} cluster and want to enable Seccomp
 defaulting, either run the kubelet with the `--seccomp-default` command line flag, or enable
-Seccomp defaulting through the
+SeccompDefault through the
 [kubelet
 configuration file](/docs/tasks/administer-cluster/kubelet-config-file/). To enable the
 feature gate in [kind](https://kind.sigs.k8s.io), ensure that `kind` provides