From 400cdbf068256ec8fa6d64f77ac726707946a614 Mon Sep 17 00:00:00 2001 From: Pablo Guerrero Date: Fri, 25 Aug 2017 19:37:09 +0200 Subject: [PATCH] typo: duplicate "to" (#5200) --- docs/tasks/configure-pod-container/assign-memory-resource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/configure-pod-container/assign-memory-resource.md b/docs/tasks/configure-pod-container/assign-memory-resource.md index 73d0481fa2..d717828345 100644 --- a/docs/tasks/configure-pod-container/assign-memory-resource.md +++ b/docs/tasks/configure-pod-container/assign-memory-resource.md @@ -129,7 +129,7 @@ kubectl delete pod memory-demo --namespace=mem-example A Container can exceed its memory request if the Node has memory available. But a Container is not allowed to use more than its memory limit. If a Container allocates more memory than its limit, the Container becomes a candidate for termination. If the Container continues to -to consume memory beyond its limit, the Container is terminated. If a terminated Container is +consume memory beyond its limit, the Container is terminated. If a terminated Container is restartable, the kubelet will restart it, as with any other type of runtime failure. In this exercise, you create a Pod that attempts to allocate more memory than its limit.