update v4.10.0 docs

Author: cabbetlong

content/en/docs/_index.md

@@ -7,6 +7,6 @@ weight: 20
 
 You can get the PDF version of the user guide from the following link：
 
-<a class="btn btn-lg btn-secondary me-3 mb-4" href="https://github.com/Huawei/eSDK_K8S_Plugin/blob/master/docs/eSDK%20Huawei%20Storage%20Kubernetes%20CSI%20Plugins%20V4.9.0%20User%20Guide%2001.pdf">
+<a class="btn btn-lg btn-secondary me-3 mb-4" href="https://github.com/Huawei/eSDK_K8S_Plugin/blob/v4.10.0/docs/eSDK%20Huawei%20Storage%20Kubernetes%20CSI%20Plugins%20V4.10.0%20User%20Guide%2001.pdf">
   PDF Download <i class="fa-solid fa-file-pdf"></i>
 </a>

content/en/docs/basic-services/persistent-volume-management/configuring-pvs/configuring-a-static-pv.md

@@ -252,7 +252,7 @@ A storage resource, such as a LUN or file system, required by the PV to be creat
 
 After a PV is created in static volume provisioning mode, you can create a PVC based on the PV for containers.
 
-1.  Prepare the PVC configuration file  **mypv.yaml**. The following is an example. For details about other parameters, see  [Table 2](#table195731435604).
+1.  Prepare the PVC configuration file  **mypvc.yaml**. The following is an example. For details about other parameters, see  [Table 2](#table195731435604).
 
     ```yaml
     kind: PersistentVolumeClaim
@@ -322,7 +322,7 @@ After a PV is created in static volume provisioning mode, you can create a PVC b
 <tr id="row10874152212484"><td class="cellrowborder" valign="top" width="13.47865213478652%" headers="mcps1.2.6.1.1 "><p id="p0833642172413"><a name="p0833642172413"></a><a name="p0833642172413"></a>spec.accessModes</p>
 </td>
 <td class="cellrowborder" valign="top" width="30.12698730126987%" headers="mcps1.2.6.1.2 "><p id="p2083384212416"><a name="p2083384212416"></a><a name="p2083384212416"></a>Access mode of the volume.</p>
-<a name="ul18620120655"></a><a name="ul18620120655"></a><ul id="ul18620120655"><li><strong id="b867730246"><a name="b867730246"></a><a name="b867730246"></a>RWO</strong> (ReadWriteOnce): A volume can be mounted to a node in read/write mode. This mode also allows multiple Pods running on the same node to access the volume.</li><li><strong id="b1082229233"><a name="b1082229233"></a><a name="b1082229233"></a>ROX</strong> (ReadOnlyMany): A volume can be mounted to multiple nodes in read-only mode.</li><li><strong id="b2062668684"><a name="b2062668684"></a><a name="b2062668684"></a>RWX</strong> (ReadWriteMany): A volume can be mounted to multiple nodes in read/write mode.</li><li><strong id="b1069207748"><a name="b1069207748"></a><a name="b1069207748"></a>RWOP</strong> (ReadWriteOncePod): A volume can only be mounted to a single Pod in read/write mode. Kubernetes 1.22 and later versions support this feature.</li></ul>
+<a name="ul18620120655"></a><a name="ul18620120655"></a><ul id="ul18620120655"><li><strong id="b1920971745"><a name="b1920971745"></a><a name="b1920971745"></a>RWO</strong> (ReadWriteOnce): A volume can be mounted to a node in read/write mode. This mode also allows multiple Pods running on the same node to access the volume.</li><li><strong id="b1245755049"><a name="b1245755049"></a><a name="b1245755049"></a>ROX</strong> (ReadOnlyMany): A volume can be mounted to multiple nodes in read-only mode.</li><li><strong id="b890416672"><a name="b890416672"></a><a name="b890416672"></a>RWX</strong> (ReadWriteMany): A volume can be mounted to multiple nodes in read/write mode.</li><li><strong id="b1190976238"><a name="b1190976238"></a><a name="b1190976238"></a>RWOP</strong> (ReadWriteOncePod): A volume can only be mounted to a single Pod in read/write mode. Kubernetes 1.22 and later versions support this feature.</li></ul>
 </td>
 <td class="cellrowborder" valign="top" width="5.899410058994099%" headers="mcps1.2.6.1.3 "><p id="p1823972854011"><a name="p1823972854011"></a><a name="p1823972854011"></a>Yes</p>
 </td>

content/en/docs/basic-services/persistent-volume-management/configuring-pvs/configuring-dynamic-pvs.md

@@ -21,21 +21,10 @@ Before configuring dynamic PVs, configure StorageClass by referring to  [Configu
 
 ## Configuring a PVC{#section10939415153713}
 
-1.  Prepare the PVC configuration file  **mypv.yaml**. The following is an example. For details about other parameters, see  [Table 1](#en-us_topic_0150885187_table195731435604).
+1.  Prepare the PVC configuration file  **mypvc.yaml**. The following is an example. For details about other parameters, see  [Table 1](#en-us_topic_0150885187_table195731435604).
 
-    ```yaml
-    kind: PersistentVolumeClaim
-    apiVersion: v1
-    metadata:
-      name: mypvc
-    spec:
-      accessModes:
-        - ReadWriteOnce
-      volumeMode: Filesystem
-      storageClassName: mysc
-      resources:
-        requests:
-          storage: 100Gi
+    ```
+    kind: PersistentVolumeClaimapiVersion: v1metadata:  name: mypvcspec:  accessModes:    - ReadWriteOnce  volumeMode: Filesystem  storageClassName: mysc  resources:    requests:      storage: 100Gi
     ```
 
 2.  Run the following command to create a PVC using the configuration file.
@@ -53,8 +42,7 @@ Before configuring dynamic PVs, configure StorageClass by referring to  [Configu
     The following is an example of the command output. If the PVC status is  **Bound**, the PVC has been created and can be used by a Pod.
 
     ```
-    NAME        STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
-    mypvc       Bound    pvc-840054d3-1d5b-4153-b73f-826f980abf9e   100Gi      RWO            mysc           12s
+    NAME        STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGEmypvc       Bound    pvc-840054d3-1d5b-4153-b73f-826f980abf9e   100Gi      RWO            mysc           12s
     ```
 
     >![](/css-docs/public_sys-resources/en-us/icon-notice.gif)  
@@ -229,32 +217,8 @@ Before configuring dynamic PVs, configure StorageClass by referring to  [Configu
 
 After a PVC is created, you can use the PVC to create a Pod. The following is a simple example of using a PVC. In this example, the created Pod uses the newly created  _mypvc_.
 
-```yaml
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  selector:
-    matchLabels:
-      app: nginx
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers: 
-      - image: nginx:alpine
-        name: container-0 
-        volumeMounts: 
-        - mountPath: /tmp
-          name: pvc-mypvc 
-      restartPolicy: Always 
-      volumes: 
-      - name: pvc-mypvc 
-        persistentVolumeClaim: 
-          claimName:  mypvc  # name of PVC
+```
+apiVersion: apps/v1kind: Deploymentmetadata:  name: nginx-deploymentspec:  selector:    matchLabels:      app: nginx  replicas: 2  template:    metadata:      labels:        app: nginx    spec:      containers:       - image: nginx:alpine        name: container-0         volumeMounts:         - mountPath: /tmp          name: pvc-mypvc       restartPolicy: Always       volumes:       - name: pvc-mypvc         persistentVolumeClaim:           claimName:  mypvc  # name of PVC
 ```
 
 >![](/css-docs/public_sys-resources/en-us/icon-note.gif)  

content/en/docs/basic-services/persistent-volume-management/configuring-pvs/managing-pvs.md

@@ -14,7 +14,7 @@ Manage Volume Provisioning allows administrators to use resources created on sto
 >![](/css-docs/public_sys-resources/en-us/icon-note.gif)  
 >Manage Volume Provisioning allows existing storage resources to be managed by Kubernetes. You are not allowed to manage a storage resource for multiple times and concurrently delete or create a storage resource.
 >When a storage resource is managed by multiple clusters, operations on the managed volume in a single cluster take effect only in the cluster and will not be synchronized to other clusters. Instead, you need to perform these operations on the managed volume in other clusters.
->For example, when you expand the capacity of a PVC in a cluster, the capacity of the corresponding PVC in other clusters will not be automatically expanded. In this case, you need to manually expand the capacity in other clusters by running the expansion commands in  [Expanding the Capacity of a PV](/docs/basic-services/persistent-volume-management/managing-pvs-73/expanding-the-capacity-of-a-pv).
+>For example, when you expand the capacity of a PVC in a cluster, the capacity of the corresponding PVC in other clusters will not be automatically expanded. In this case, you need to manually expand the capacity in other clusters by running the expansion commands in  [Expanding the Capacity of a PV](/docs/basic-services/persistent-volume-management/managing-pvs-87/expanding-the-capacity-of-a-pv).
 
 ## Configuration Description{#section121779524353}
 
@@ -32,7 +32,7 @@ Perform the following steps to manage and use PVs:
 
 ## Configuring a PVC{#section979723473817}
 
-1.  Prepare the PVC configuration file  **mypv.yaml**. The following is an example. For details about other parameters, see  [Table 1](#en-us_topic_0150885187_table195731435604).
+1.  Prepare the PVC configuration file  **mypvc.yaml**. The following is an example. For details about other parameters, see  [Table 1](#en-us_topic_0150885187_table195731435604).
 
     ```yaml
     kind: PersistentVolumeClaim