concepts/configuration/manage-compute-resources-container.md: fix a conversion (#4952)

Rewrite the description for spec.containers[].resources.limits.cpu

docs/concepts/configuration/manage-compute-resources-container.md

@@ -135,14 +135,12 @@ When using Docker:
   [`--cpu-shares`](https://docs.docker.com/engine/reference/run/#/cpu-share-constraint)
   flag in the `docker run` command.
 
-- The `spec.containers[].resources.limits.cpu` is converted to its millicore value,
+- The `spec.containers[].resources.limits.cpu` is converted to its millicore value and
-  multiplied by 100000, and then divided by 1000. This number is used as the value
+  multiplied by 100. The resulting value is the total amount of CPU time that a container can use
-  of the [`--cpu-quota`](https://docs.docker.com/engine/reference/run/#/cpu-quota-constraint)
+  every 100ms. A container cannot use more than its share of CPU time during this interval.
-  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
+  **Note**: The default quota period is 100ms. The minimum resolution of CPU quota is 1ms.
-   kubelet enforces cpu limits if it is started with the
+  {: .note}
-  [`--cpu-cfs-quota`] flag set to true. As of Kubernetes version 1.2, this flag
-  defaults to true.
 
 - The `spec.containers[].resources.limits.memory` is converted to an integer, and
   used as the value of the
@@ -434,4 +432,3 @@ consistency across providers and platforms.
 {% endcapture %}
 
 {% include templates/concept.md %}
-