diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-05-01 03:38:16 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-05-01 03:38:16 -0700 |
| commit | 92839e86313922d0070c824feab44fa564c7359f (patch) | |
| tree | fbd8a0f1eee0b47d9cc34b21f301b03d5b424034 | |
| parent | 78e49b9a26895c0162cec6acbe456484badf7b3c (diff) | |
| parent | da68dcc55b077778bb6a3bdf1f91a52e60e6231c (diff) | |
Merge pull request #2089 from AdamDang/patch-4
Typo fix: we wil->we will
| -rw-r--r-- | contributors/design-proposals/scheduling/rescheduling.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/scheduling/rescheduling.md b/contributors/design-proposals/scheduling/rescheduling.md index db960934..32d86a27 100644 --- a/contributors/design-proposals/scheduling/rescheduling.md +++ b/contributors/design-proposals/scheduling/rescheduling.md @@ -28,7 +28,7 @@ implied. However, describing the process as "moving" the pod is approximately ac and easier to understand, so we will use this terminology in the document. We use the term "rescheduling" to describe any action the system takes to move an -already-running pod. The decision may be made and executed by any component; we wil +already-running pod. The decision may be made and executed by any component; we will introduce the concept of a "rescheduler" component later, but it is not the only component that can do rescheduling. |