summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxiangpengzhao <zhao.xiangpeng@zte.com.cn>2016-12-19 04:19:17 -0500
committerxiangpengzhao <zhao.xiangpeng@zte.com.cn>2016-12-19 04:19:17 -0500
commit77d4ae6dbc5b285ab93351e34e2f816caf69d5ec (patch)
treec7695a9d6d2cba21a25c4f5cd9557df2d847ec7b
parent7c3e8af9802c27d3f148cf1876a40c3a96c0e9df (diff)
Fix incorrect link
-rw-r--r--contributors/design-proposals/node-allocatable.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node-allocatable.md b/contributors/design-proposals/node-allocatable.md
index ac9f46c4..12f244eb 100644
--- a/contributors/design-proposals/node-allocatable.md
+++ b/contributors/design-proposals/node-allocatable.md
@@ -99,7 +99,7 @@ behavior is equivalent to the 1.1 behavior with scheduling based on Capacity.
#### System-Reserved
In the initial implementation, `SystemReserved` will be functionally equivalent to
-[`KubeReserved`](#system-reserved), but with a different semantic meaning. While KubeReserved
+[`KubeReserved`](#kube-reserved), but with a different semantic meaning. While KubeReserved
designates resources set aside for kubernetes components, SystemReserved designates resources set
aside for non-kubernetes components (currently this is reported as all the processes lumped
together in the `/system` raw container).