Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md

Co-authored-by: Alice Gibbons <alicejgibbons@gmail.com>
Signed-off-by: Mirel <15373565+MyMirelHub@users.noreply.github.com>

Author: MyMirelHub

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md

@@ -134,7 +134,7 @@ When running in production, consider:
 1. **Availability zones**: The default topology key spreads pods across zones. This limits the chance that a single zone outage removes multiple Scheduler or Placement pods at the same time.
 2. **Single zone, many nodes**:  Zone labels are often identical across the cluster; set `topologyKey` to `kubernetes.io/hostname` to enable spreading by node.
 3. **Soft spreading**: The default behaviour is recommended here allowing pod scheduling to succeed when the cluster is short on zones or nodes.
-4. **Hard spreading** — Only when you must never place two replicas on the same topology value. You need at least as many distinct values for `topologyKey` as replicas, or pods can stay Pending.
+4. **Hard spreading**: Only use when you must never place two replicas on the same topology value. This requires as many distinct values for `topologyKey` as replicas, or pods will stay `Pending`.
 
 For example, too configure hard spreading by hostname in a single-zone cluster, use the following Helm values: