Update k8s-best-practices-linux-capabilities.adoc

Author: mwlinca

modules/k8s-best-practices-linux-capabilities.adoc

@@ -18,7 +18,7 @@ The capabilities associated with a new container are determined as follows:
 
 * If the container has the UID 0 (root) its Effective capability set is determined according to the capability attributes requested by the pod or container security context and allowed by the SCC assigned to the pod. In this case, the SCC provides a way to limit the capabilities of a root container.
 
-* If the container has a UID non 0 (non root), the new container has an empty Effective capability set (see link:https://github.com/kubernetes/kubernetes/issues/56374#[]). In this case the SCC assigned to the pod controls only the capabilities the container may acquire through the file capabilities of binaries it will execute.
+* If the container has a UID non 0 (non root), the new container has an empty Effective capability set (see link:https://github.com/kubernetes/kubernetes/issues/56374#[Kubernetes should configure the ambient capability set]). In this case the SCC assigned to the pod controls only the capabilities the container may acquire through the file capabilities of binaries it will execute.
 
 Considering the general recommendation to avoid running root containers, capabilities required by non-root containers are controlled by the pod or container security context and the SCC capability attributes but can only be acquired by properly setting the file capabilities of the container binaries.