Don't reference csi-lvm anymore. (#38)

Author: Gerrit91

blog/2019/01-why-metal-stack/index.md

@@ -116,7 +116,7 @@ Essentially this agent does two things:
 
 To provide storage for our environment, we chose to equip each server with local NVMe or SATA drives. We make these
 drives accessible as local persistent volumes from Kubernetes by integrating our
-[LVM CSI driver](https://github.com/metal-stack/csi-lvm) as a Gardener extension.
+[csi-driver-lvm](https://github.com/metal-stack/csi-driver-lvm) as a Gardener extension ([gardener-extension-csi-driver-lvm](https://github.com/metal-stack/gardener-extension-csi-driver-lvm)).
 
 To make sure, that data stored on these drives is erased before handing over the node to a cluster, the
 [metal-hammer](https://github.com/metal-stack/metal-hammer) either can erase the disks properly (which can take long)

docs/docs/05-Concepts/04-Kubernetes/07-storage.md

@@ -39,7 +39,7 @@ spec:
   resources:
     requests:
       storage: 100Mi
-  storageClassName: csi-lvm-sc-linear
+  storageClassName: csi-driver-lvm-linear
 ```
 
-The solution does not provide cloud-storage or whatsoever, but it improves the user's accessibility of local storage on bare-metal machines through Kubernetes. Check out the driver's documentation [here](../../08-References/Storage/csi-lvm/csi-lvm.md).
+The solution does not provide cloud-storage or whatsoever, but it improves the user's accessibility of local storage on bare-metal machines through Kubernetes. Check out the driver's documentation [here](../../08-References/Storage/csi-driver-lvm/csi-driver-lvm.md).