summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuang Ya Liu <gyliu513@gmail.com>2017-04-10 13:46:00 +0800
committerGitHub <noreply@github.com>2017-04-10 13:46:00 +0800
commit07286f934f4b2e110bb00a440bb86e53f7447bd1 (patch)
tree0b975e426eb9534af343afd79c0aba0a4c29fb88
parentffaeca51c5bcfd20cd9432080371defa4eb47552 (diff)
parentd237df0b0117db64cd3b616ca0f54d0e8f671a5b (diff)
Merge pull request #522 from wanghaoran1988/fix_link
fix link of multiple-scheduler
-rw-r--r--contributors/devel/mesos-style.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/mesos-style.md b/contributors/devel/mesos-style.md
index 81554ce8..53ee139e 100644
--- a/contributors/devel/mesos-style.md
+++ b/contributors/devel/mesos-style.md
@@ -61,7 +61,7 @@ machine manages the collection during their lifetimes
Out-of-the-box Kubernetes has *workload-specific* abstractions (ReplicaSet, Job,
DaemonSet, etc.) and corresponding controllers, and in the future may have
-[workload-specific schedulers](../../docs/proposals/multiple-schedulers.md),
+[workload-specific schedulers](../design-proposals/multiple-schedulers.md),
e.g. different schedulers for long-running services vs. short-running batch. But
these abstractions, controllers, and schedulers are not *application-specific*.