fix typo

contributors/design-proposals/node-allocatable.md

@@ -326,7 +326,7 @@ for overflow and the node should continue to function. If the node has been sche
 situation.
 
 A recommended alternative is to enforce KubeReserved once Kubelet supports it (Phase 2).
-In the [future](#future-work) we may set a parent cgroup for kubernetes components, with limits set
+In the future we may set a parent cgroup for kubernetes components, with limits set
 according to `KubeReserved`.
 
 ### 3rd party schedulers

contributors/design-proposals/resource-qos.md

@@ -20,7 +20,7 @@ Borg increased utilization by about 20% when it started allowing use of such non
 
 ## Requests and Limits
 
-For each resource, containers can specify a resource request and limit, `0 <= request <= `[`Node Allocatable`](../proposals/node-allocatable.md) & `request <= limit <= Infinity`.
+For each resource, containers can specify a resource request and limit, `0 <= request <= `[`Node Allocatable`](../design-proposals/node-allocatable.md) & `request <= limit <= Infinity`.
 If a pod is successfully scheduled, the container is guaranteed the amount of resources requested.
 Scheduling is based on `requests` and not `limits`.
 The pods and its containers will not be allowed to exceed the specified limit.

contributors/design-proposals/resources.md

@@ -302,8 +302,8 @@ where a `<CPU-info>` or `<memory-info>` structure looks like this:
 ```yaml
 {
     mean: <value>    # arithmetic mean
-    max: <value>     # minimum value
-    min: <value>     # maximum value
+    max: <value>     # maximum value
+    min: <value>     # minimum value
     count: <value>   # number of data points
     percentiles: [   # map from %iles to values
       "10": <10th-percentile-value>,