summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdamDang <adam.dang@daocloud.io>2018-04-29 14:00:59 +0800
committerGitHub <noreply@github.com>2018-04-29 14:00:59 +0800
commitda68dcc55b077778bb6a3bdf1f91a52e60e6231c (patch)
tree6cd0072e35518a93ea37c45e3375f1a2ffc76a2b
parent5ef70dffbe17f1d54c976c78064d109465d7503b (diff)
Typo fix: we wil->we will
we wil->we will
-rw-r--r--contributors/design-proposals/scheduling/rescheduling.md2
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.