typo

Signed-off-by: Byonggon Chun <[email protected]>

keps/sig-node/20190129-hugepages.md

@@ -43,7 +43,7 @@ superseded-by:
       - [cAdvisor changes(Phase 1)](#cadvisor-changes(Phase-1))
     - [Phase 2](#Phase-2)
       - [Support container isolation of huge pages](#support-container-isolation-of-huge-pages)
-      - [Support reserve huge pages for system on Node Allocatable feature](#support-reserve-huge-pages-for-system-on-node-allocatable-feature)
+      - [Enhance Node Allocatable feature to reserve huge pages for system](#Enhance-node-allocatable-feature--to-reserve-huge-pages-for-system)
       - [cAdviser changes(Phase 2)](#cAdviser-changes(Phase-2))
     - [Phase 3](#Phase-3)
       - [Update LinuxContainerResources(CRI) to support specifying huge page limits](#update-linuxcontainerresources(cri)-to-support-specifying-huge-page-limits)
@@ -338,10 +338,10 @@ calculate allocatable values on the node.
 Container isolation of huge pages should be supported to avoid competition between containers to consume huge pages. Currently, `kubelet` sets the agregated huge pages limits on pod's cgroup of hugetlb subsystem. This should be enhanced to set limits on container's cgroup.
 
 #### cAdviser changes(Phase 2)
-To support NUMA, `cAdviser` should collect and store pre-allocated huge pages per NUMA node.
+To support NUMA, `cAdviser` should discover and store pre-allocated huge pages per NUMA node.
 
 
-#### Support reserve huge pages for system on Node Allocatable feature
+#### Enhance Node Allocatable feature to reserve huge pages for system
 Some system services like `OVS-DPDK` comsume huge pages per NUMA node, to determine allocatalbe number of huge pages in `kubelet`, `Node Allocatable feature` should support to reserve huge pages per NUMA node. 
 
 ### Phase 3