Merge pull request #585 from maoyangLiu/master

fix typo mistake

Author: k8s-ci-robot

kep/2-lightweight-coscheduling/README.md

@@ -41,7 +41,7 @@ When running a Tensorflow/MPI job, all tasks must start before they can do any w
 ## Terms
 
 - **pgPod**: pod belongs to some `PodGroup`.
-- **regularPod**: a regular `Pod` (which doesn't have `PodGropuName` set).
+- **regularPod**: a regular `Pod` (which doesn't have `PodGroupName` set).
 
 ## Proposal
 

kep/399-sysched-scoring/README.md

@@ -58,7 +58,7 @@ While pod-centric security schemes such as seccomp are necessary, they alone are
 ## User Stories
 
 1. As a user of the cloud, I would like to be scheduled with neighbors who do not have, or less likely to have, the abilities to compromise my security via the shared kernel on the host.
-2. As a developer, I would like the users of my applications to be rewarded for my conscientious and judicious use of system calls by being scheduled on a node with neighboring applicaitons who are similarly limited in their system call usage, hence reducing the user's chance to being compromised by those neighbors via system call-based host exploits.
+2. As a developer, I would like the users of my applications to be rewarded for my conscientious and judicious use of system calls by being scheduled on a node with neighboring applications who are similarly limited in their system call usage, hence reducing the user's chance to being compromised by those neighbors via system call-based host exploits.
 3. As a cloud provider, we want to enable multitenancy but minimize the impact of a compromised or malicious pod on our users. Hence, we want to minimize the number of victim pods and victim nodes in a cluster from some pods exploiting system call-based host exploits.
 
 ### Notes/Constraints/Caveats