Fix design doc link

kubernetes · Jul 2, 2018 · 2761b5f · 2761b5f
1 parent f37c746
commit 2761b5f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/contributors/design-proposals/storage/csi-snapshot.md b/contributors/design-proposals/storage/csi-snapshot.md
@@ -278,7 +278,7 @@ type StorageClass struct {
 ![CSI Snapshot Diagram](csi-snapshot_diagram.png?raw=true "CSI Snapshot Diagram")
 
 
-External snapshotter is part of Kubernetes implementation of [Container Storage Interface (CSI)](https://github.com/container-storage-interface/spec). It is an external controller that monitors `VolumeSnapshot` and `VolumeSnapshotData` objects and creates/deletes snapshot from volumes. The original CSI design can be found at Kubernetes proposal at https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md.
+External snapshotter is part of Kubernetes implementation of [Container Storage Interface (CSI)](https://github.com/container-storage-interface/spec). It is an external controller that monitors `VolumeSnapshot` and `VolumeSnapshotData` objects and creates/deletes snapshot from volumes. The original Kubernetes CSI design can be found at Kubernetes [design proposal](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md).
 
 External snapshotter follows [controller](https://github.com/kubernetes/community/blob/master/contributors/devel/controllers.md) pattern and uses informers to watch for `VolumeSnapshot` and `VolumeSnapshotData` create/update/delete events. It filters out `VolumeSnapshot` instances with `Snapshotter==<CSI driver name>` and processes these events in workqueues with exponential backoff. Real handling is deferred to the `Handler` interface.