fix2

Author: mochizuki875

content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md

@@ -133,17 +133,17 @@ your cluster. Those fields are:
 
 - **matchLabelKeys** is a list of pod label keys to select the group of pods over which 
   the spreading skew will be calculated. At a pod creation, 
-  apiserver will use those keys to lookup values from the incoming pod labels,
-  and those key-value labels will be merged with existing `labelSelector`. 
+  the kube-apiserver uses those keys to lookup values from the incoming pod labels,
+  and those key-value labels will be merged with any existing `labelSelector`.
   The same key is forbidden to exist in both `matchLabelKeys` and `labelSelector`. 
   `matchLabelKeys` cannot be set when `labelSelector` isn't set. 
   Keys that don't exist in the pod labels will be ignored. 
   A null or empty list means only match against the `labelSelector`.
 
-  {{< warning >}}
+  {{< caution >}}
   It's not recommended to use `matchLabelKeys` with labels that might be updated 
   because the update of the label isn't reflected onto the merged `labelSelector`.
-  {{< /warning >}}
+  {{< /caution >}}
 
   With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
   The controller/operator just needs to set different values to the same label key for different