summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorDaniel <dani07@users.noreply.github.com>2018-06-05 11:48:53 +0530
committerGitHub <noreply@github.com>2018-06-05 11:48:53 +0530
commit5f6eb26d5a2389f4fa83d34e8eea2613f0f20fe5 (patch)
tree6e298954c64d617c059ebabf839890378545d6fa /contributors
parent920d87ea659ca1fe238b3bdb9c94e4d834451fdb (diff)
Update vertical-pod-autoscaler.md
Minor spelling mistake
Diffstat (limited to 'contributors')
-rw-r--r--contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
index 13d235f8..d990d7db 100644
--- a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
+++ b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
@@ -558,7 +558,7 @@ VPA controls the request (memory and CPU) of containers. In MVP it always sets
the limit to infinity. It is not yet clear whether there is a use-case for VPA
setting the limit.
-The request is calculated based on analysis of the current and revious runs of
+The request is calculated based on analysis of the current and previous runs of
the container and other containers with similar properties (name, image,
command, args).
The recommendation model (MVP) assumes that the memory and CPU consumption are