From 1eb44e04c2c630ca44ec12438eb84181967e4597 Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Thu, 30 Nov 2023 12:16:49 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Tim Bannister --- content/en/docs/concepts/security/pod-security-standards.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/security/pod-security-standards.md b/content/en/docs/concepts/security/pod-security-standards.md index 67b8d9012cec9..2fdd2638367f5 100644 --- a/content/en/docs/concepts/security/pod-security-standards.md +++ b/content/en/docs/concepts/security/pod-security-standards.md @@ -485,11 +485,11 @@ Restrictions on the following controls are only required if `.spec.os.name` is n - Seccomp - Linux Capabilities -## User Namespaces +## User namespaces User Namespaces are a Linux-only feature to run workloads with increased isolation. How they work together with Pod Security Standards is described in -the [corresponding feature documentation](/docs/concepts/workloads/pods/user-namespaces#integration-with-pod-security-admission-checks). +the [documentation](/docs/concepts/workloads/pods/user-namespaces#integration-with-pod-security-admission-checks) for Pods that use user namespaces. ## FAQ