Remove the Used on information and replace caution tag with note

Author: mtardy

content/en/docs/reference/labels-annotations-taints.md

@@ -455,28 +455,24 @@ for more information.
 
 Example: `pod-security.kubernetes.io/exempt: namespace`
 
-Used on: `audit.k8s.io/Event`
-
 Value **must** be one of `user`, `namespace`, or `runtimeClass` which correspond to
 [Pod Security Exemption](/docs/concepts/security/pod-security-admission/#exemptions)
 dimensions. This annotation indicates on which dimension was based the exemption
 from the PodSecurity enforcement.
 
-{{< caution >}}
+{{< note >}}
 This annotation is not used within the Kubernetes API. When you
 [enable auditing](/docs/tasks/debug-application-cluster/audit/) in your cluster,
 audit event data is written using `Event` from API group `audit.k8s.io`.
 The annotation applies to audit events. Audit events are different from objects in the
 [Event API](/docs/reference/kubernetes-api/cluster-resources/event-v1/) (API group
 `events.k8s.io`).
-{{< /caution >}}
+{{< /note >}}
 
 ## pod-security.kubernetes.io/enforce-policy
 
 Example: `pod-security.kubernetes.io/enforce-policy: restricted:latest`
 
-Used on: `audit.k8s.io/Event`
-
 Value **must** be `privileged:<version>`, `baseline:<version>`,
 `restricted:<version>` which correspond to [Pod Security
 Standard](/docs/concepts/security/pod-security-standards) levels accompanied by
@@ -487,23 +483,21 @@ allowed or denied the pod during PodSecurity admission.
 See [Pod Security Standards](/docs/concepts/security/pod-security-standards/)
 for more information.
 
-{{< caution >}}
+{{< note >}}
 This annotation is not used within the Kubernetes API. When you
 [enable auditing](/docs/tasks/debug-application-cluster/audit/) in your cluster,
 audit event data is written using `Event` from API group `audit.k8s.io`.
 The annotation applies to audit events. Audit events are different from objects in the
 [Event API](/docs/reference/kubernetes-api/cluster-resources/event-v1/) (API group
 `events.k8s.io`).
-{{< /caution >}}
+{{< /note >}}
 
 ## pod-security.kubernetes.io/audit-violations
 
 Example:  `pod-security.kubernetes.io/audit-violations: would violate
 PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container
 "example" must set securityContext.allowPrivilegeEscalation=false), ...`
 
-Used on: `audit.k8s.io/Event`
-
 Value details an audit policy violation, it contains the
 [Pod Security Standard](/docs/concepts/security/pod-security-standards/) level
 that was transgressed as well as the specific policies on the fields that were
@@ -512,14 +506,14 @@ violated from the PodSecurity enforcement.
 See [Pod Security Standards](/docs/concepts/security/pod-security-standards/)
 for more information.
 
-{{< caution >}}
+{{< note >}}
 This annotation is not used within the Kubernetes API. When you
 [enable auditing](/docs/tasks/debug-application-cluster/audit/) in your cluster,
 audit event data is written using `Event` from API group `audit.k8s.io`.
 The annotation applies to audit events. Audit events are different from objects in the
 [Event API](/docs/reference/kubernetes-api/cluster-resources/event-v1/) (API group
 `events.k8s.io`).
-{{< /caution >}}
+{{< /note >}}
 
 ## seccomp.security.alpha.kubernetes.io/pod (deprecated) {#seccomp-security-alpha-kubernetes-io-pod}