[zh-cn] sync volume-snapshot-classes.md

content/zh-cn/docs/concepts/storage/persistent-volumes.md

@@ -1114,7 +1114,7 @@ The access modes are:
 
 `ReadWriteOnce`
 : the volume can be mounted as read-write by a single node. ReadWriteOnce access
-  mode still can allow multiple pods to access (read from or write to) that volume when the pods are
+  mode still can allow multiple pods to access the volume when the pods are
   running on the same node. For single pod access, please see ReadWriteOncePod.
 
 `ReadOnlyMany`
@@ -1133,7 +1133,7 @@ The access modes are:
 
 `ReadWriteOnce`
 : 卷可以被一个节点以读写方式挂载。
-  ReadWriteOnce 访问模式仍然可以在同一节点上运行的多个 Pod 访问（读取或写入）该卷。
+  ReadWriteOnce 访问模式仍然可以在同一节点上运行的多个 Pod 访问该卷。
   对于单个 Pod 的访问，请参考 ReadWriteOncePod 访问模式。
 
 `ReadOnlyMany`
@@ -1475,23 +1475,6 @@ consumption of the volume as either a filesystem or block device.
 申领使用[与卷相同的约定](#volume-mode)来表明是将卷作为文件系统还是块设备来使用。
 
 <!--
-### Volume Name
-
-Claims can use the `volumeName` field to explicitly bind to a specific PersistentVolume. You can also leave
-`volumeName` unset, indicating that you'd like Kubernetes to set up a new PersistentVolume
-that matches the claim.
-If the specified PV is already bound to another PVC, the binding will be stuck
-in a pending state.
--->
-
-### 卷名称    {#volume-name}
-
-申领可以使用 `volumeName` 字段显式绑定到特定的 PersistentVolume。
-你也可以不设置 `volumeName` 字段，这表示你希望 Kubernetes 设置一个与申领匹配的新 PersistentVolume。
-如果指定的 PV 已经绑定到另一个 PVC，则绑定操作将卡在 Pending 状态。
-
-<!--
-
 ### Resources
 
 Claims, like Pods, can request specific quantities of a resource. In this case,

content/zh-cn/docs/concepts/storage/volume-snapshot-classes.md

@@ -91,6 +91,41 @@ deletionPolicy: Delete
 parameters:
 ```
 
+<!--
+If multiple CSI drivers exist, a default VolumeSnapshotClass can be specified
+for each of them.
+-->
+
+如果存在多个 CSI 驱动程序，可以为每个驱动程序指定一个默认的 VolumeSnapshotClass。
+
+<!--
+### VolumeSnapshotClass dependencies
+
+When you create a VolumeSnapshot without specifying a VolumeSnapshotClass, Kubernetes
+automatically selects a default VolumeSnapshotClass that has a CSI driver matching
+the CSI driver of the PVC’s StorageClass.
+
+This behavior allows multiple default VolumeSnapshotClass objects to coexist in a cluster, as long as
+each one is associated with a unique CSI driver.
+
+Always ensure that there is only one default VolumeSnapshotClass for each CSI driver. If
+multiple default VolumeSnapshotClass objects are created using the same CSI driver,
+a VolumeSnapshot creation will fail because Kubernetes cannot determine which one to use.
+-->
+
+### VolumeSnapshotClass 依赖关系
+
+当你创建一个 VolumeSnapshot 且未指定 VolumeSnapshotClass 时，
+Kubernetes 会自动选择一个默认的 VolumeSnapshotClass，
+该类与 PVC 的 StorageClass 所使用的 CSI 驱动程序匹配。
+
+这种行为允许多个默认的 VolumeSnapshotClass 对象在集群中共存，
+只要每个默认类都与一个且唯一的 CSI 驱动程序关联。
+
+始终确保每个 CSI 驱动程序只有一个默认的 VolumeSnapshotClass。
+如果使用相同的 CSI 驱动程序创建了多个默认的 VolumeSnapshotClass 对象，
+则创建 VolumeSnapshot 时会失败，因为 Kubernetes 无法确定使用哪个类。
+
 <!--
 ### Driver