Merge pull request #29476 from liggitt/podsecurity-audit-annotations

Clarify audit annotation destination

Author: k8s-ci-robot

content/en/docs/concepts/security/pod-security-admission.md

@@ -62,9 +62,9 @@ takes if a potential violation is detected:
 {{< table caption="Pod Security Admission modes" >}}
 Mode | Description
 :---------|:------------
-**`enforce`** | Policy violations will cause the pod to be rejected.
-**`audit`** | Policy violations will trigger the addition of an audit annotation, but are otherwise allowed.
-**`warn`** | Policy violations will trigger a user-facing warning, but are otherwise allowed.
+**enforce** | Policy violations will cause the pod to be rejected.
+**audit** | Policy violations will trigger the addition of an audit annotation to the event recorded in the [audit log](/docs/tasks/debug-application-cluster/audit/), but are otherwise allowed.
+**warn** | Policy violations will trigger a user-facing warning, but are otherwise allowed.
 {{< /table >}}
 
 A namespace can configure any or all modes, or even set a different level for different modes.