merge: distributed provisioning - doc fixes

docs/design.md

@@ -5,7 +5,6 @@
     - [LVM device mode](#lvm-device-mode)
     - [Direct device mode](#direct-device-mode)
     - [Kata Containers support](#kata-containers-support)
-    - [Driver modes](#driver-modes)
     - [Dynamic provisioning of local volumes](#dynamic-provisioning-of-local-volumes)
     - [Communication between components](#communication-between-components)
     - [Security](#security)
@@ -165,7 +164,7 @@ creates volumes locally on a node.
 
 PMEM-CSI solves this problem by deploying `external-provisioner`
 alongside each node driver and enabling ["distributed
-provisioning"](https://github.com/kubernetes-csi/external-provisioner/issues/487):
+provisioning"](https://github.com/kubernetes-csi/external-provisioner/tree/v2.1.0#deployment-on-each-node):
 - For volumes with storage classes that use late binding (aka "wait
   for first consumer"), a volume is tentatively assigned to a node
   before creating it, in which case the `external-provisioner` running

docs/install.md

@@ -8,7 +8,7 @@
     - [Install PMEM-CSI driver](#install-pmem-csi-driver)
       - [Install using the operator](#install-using-the-operator)
       - [Install from source](#install-from-source)
-    - [Expose volumes to applications](#expose-volumes-to-applications)
+    - [Volume parameters](#volume-parameters)
     - [Kata Containers support](#kata-containers-support)
     - [Ephemeral inline volumes](#ephemeral-inline-volumes)
     - [Raw block volumes](#raw-block-volumes)
@@ -76,8 +76,8 @@ release notes.
 When using YAML files, the only reliable way of up- or downgrading is
 to remove the installation and install anew.
 
-Users can then create PMEM volumes via [volume
-claims](#expose-persistent-and-cache-volumes-to-applications) that
+Users can then create PMEM volumes via [persistent volume
+claims](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) that
 reference the storage classes or via [ephemeral inline
 volumes](#ephemeral-inline-volumes).