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

Author: mwlinca

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

@@ -119,8 +119,8 @@ See test case link:https://github.com/test-network-function/cnf-certification-te
 [id="cnf-best-practices-sys_ptrace"]
 == SYS_PTRACE
 
-This capability is required when using Process Namespace Sharing. This is used when processes from one Container need to be exposed to another Container. For example, to send signals like SIGHUP from a process in a Container to another process in another Container. See link:https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/[] for more details.
-For more information on these capabilities refer to link:https://cloud.redhat.com/blog/linux-capabilities-in-openshift[].
+This capability is required when using Process Namespace Sharing. This is used when processes from one Container need to be exposed to another Container. For example, to send signals like SIGHUP from a process in a Container to another process in another Container. See link:https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/[Share Process Namespace between Containers in a Pod] for more details.
+For more information on these capabilities refer to link:https://cloud.redhat.com/blog/linux-capabilities-in-openshift[Linux Capabilities in OpenShift].
 
 See test case link:https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md#access-control-sys-ptrace-capability[access-control-sys-ptrace-capability]