Update volume mode change annotation in documentation

content/en/docs/concepts/storage/volume-snapshots.md

@@ -227,7 +227,7 @@ $ kubectl get crd volumesnapshotcontent -o yaml
 
 If you want to allow users to create a `PersistentVolumeClaim` from an existing
 `VolumeSnapshot`, but with a different volume mode than the source, the annotation
-`snapshot.storage.kubernetes.io/allowVolumeModeChange: "true"`needs to be added to
+`snapshot.storage.kubernetes.io/allow-volume-mode-change: "true"`needs to be added to
 the `VolumeSnapshotContent` that corresponds to the `VolumeSnapshot`.
 
 For pre-provisioned snapshots, `spec.sourceVolumeMode` needs to be populated
@@ -241,7 +241,7 @@ kind: VolumeSnapshotContent
 metadata:
   name: new-snapshot-content-test
   annotations:
-    - snapshot.storage.kubernetes.io/allowVolumeModeChange: "true"
+    - snapshot.storage.kubernetes.io/allow-volume-mode-change: "true"
 spec:
   deletionPolicy: Delete
   driver: hostpath.csi.k8s.io

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

@@ -844,9 +844,9 @@ you through the steps you follow to apply a seccomp profile to a Pod or to one o
 its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes,
 based on setting `securityContext` within the Pod's `.spec`.
 
-### snapshot.storage.kubernetes.io/allowVolumeModeChange
+### snapshot.storage.kubernetes.io/allow-volume-mode-change
 
-Example: `snapshot.storage.kubernetes.io/allowVolumeModeChange: "true"`
+Example: `snapshot.storage.kubernetes.io/allow-volume-mode-change: "true"`
 
 Used on: VolumeSnapshotContent