added link to spec.minReadySeconds and maxUnavailable for clarity (#9194)

* added link to minReadySeconds

* link for max unavailable

* used relative path

content/en/docs/tasks/manage-daemon/update-daemon-set.md

@@ -39,8 +39,8 @@ DaemonSet has two update strategy types:
 To enable the rolling update feature of a DaemonSet, you must set its
 `.spec.updateStrategy.type` to `RollingUpdate`.
 
-You may want to set `.spec.updateStrategy.rollingUpdate.maxUnavailable` (default
-to 1) and `.spec.minReadySeconds` (default to 0) as well.
+You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) (default
+to 1) and [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) as well.
 
 
 ### Step 1: Checking DaemonSet `RollingUpdate` update strategy
@@ -191,6 +191,3 @@ progress.
 * See [Concepts: Creating a DaemonSet to adopt existing DaemonSet pods](/docs/concepts/workloads/controllers/daemonset/)
 
 {{% /capture %}}
-
-
-