Merge pull request #36530 from jpreese/patch-2

Update topology-aware-hints.md

Author: k8s-ci-robot

content/en/docs/concepts/services-networking/topology-aware-hints.md

@@ -59,7 +59,7 @@ when this feature is enabled. The controller allocates a proportional amount of
 endpoints to each zone. This proportion is based on the
 [allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)
 CPU cores for nodes running in that zone. For example, if one zone had 2 CPU
-cores and another zone only had 1 CPU core, the controller would allocated twice
+cores and another zone only had 1 CPU core, the controller would allocate twice
 as many endpoints to the zone with 2 CPU cores.
 
 The following example shows what an EndpointSlice looks like when hints have
@@ -148,7 +148,7 @@ zone.
   portion of nodes are unready.
 
 * The EndpointSlice controller does not take into account {{< glossary_tooltip
-  text="tolerations" term_id="toleration" >}} when deploying calculating the
+  text="tolerations" term_id="toleration" >}} when deploying or calculating the
   proportions of each zone. If the Pods backing a Service are limited to a
   subset of Nodes in the cluster, this will not be taken into account.