Addressed comments.

Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com>

content/en/docs/concepts/workloads/controllers/daemonset.md

@@ -118,14 +118,12 @@ node that a Pod runs on is selected by the Kubernetes scheduler. However,
 DaemonSet pods are created and scheduled by the DaemonSet controller instead.
 That introduces the following issues:
 
- * A DaemonSet cannot respect a Node’s resource changes, such as the node
-   having more free resources after other Pods exit ([#46935](https://github.com/kubernetes/kubernetes/issues/46935)
  * Inconsistent Pod behavior: Normal Pods waiting to be scheduled are created
    and in `Pending` state, but DaemonSet pods are not created in `Pending`
    state. This is confusing to the user.
- * With preemption, different components, such as DaemonSets and the default
-   scheduler, may make different preemption decisions, which can cause
-   unexpected behaviorss.
+ * [Pod preemption](/docs/concepts/configuration/pod-priority-preemption/)
+   is handled by default scheduler. When preemption is enabled, the DaemonSet controller
+   will make scheduling decisions without considering pod priority and preemption.
 
 `ScheduleDaemonSetPods` allows you to schedule DaemonSets using the default
 scheduler instead of the DaemonSet controller, by adding the `NodeAffinity` term