From 0a33b3e910e98b67bba27c75d1d83b1d7a1b393e Mon Sep 17 00:00:00 2001 From: wenlxie Date: Sat, 18 Mar 2017 22:23:30 +0800 Subject: [PATCH] Update manage-compute-resources-container.md Change "he" to "The" --- .../configuration/manage-compute-resources-container.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/configuration/manage-compute-resources-container.md b/docs/concepts/configuration/manage-compute-resources-container.md index 2754260d65..5f99b966f2 100644 --- a/docs/concepts/configuration/manage-compute-resources-container.md +++ b/docs/concepts/configuration/manage-compute-resources-container.md @@ -138,7 +138,7 @@ When using Docker: - The `spec.containers[].resources.limits.cpu` is converted to its millicore value, multiplied by 100000, and then divided by 1000. This number is used as the value of the [`--cpu-quota`](https://docs.docker.com/engine/reference/run/#/cpu-quota-constraint) - flag in the `docker run` command. he [`--cpu-period`] flag is set to 100000, + flag in the `docker run` command. The [`--cpu-period`] flag is set to 100000, which represents the default 100ms period for measuring quota usage. The kubelet enforces cpu limits if it is started with the [`--cpu-cfs-quota`] flag set to true. As of Kubernetes version 1.2, this flag