From da5872845fbb1f37ed0a6935ceb4b051e119a060 Mon Sep 17 00:00:00 2001
From: Stewart-YU <30410021+stewart-yu@users.noreply.github.com>
Date: Wed, 9 Aug 2017 20:11:33 +0800
Subject: [PATCH] Update daemonset.md

The first letter needs to be capitalized
---
 docs/concepts/workloads/controllers/daemonset.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts/workloads/controllers/daemonset.md b/docs/concepts/workloads/controllers/daemonset.md
index 57b67447ae..ce48aa5213 100644
--- a/docs/concepts/workloads/controllers/daemonset.md
+++ b/docs/concepts/workloads/controllers/daemonset.md
@@ -93,7 +93,7 @@ Normally, the machine that a pod runs on is selected by the Kubernetes scheduler
 created by the Daemon controller have the machine already selected (`.spec.nodeName` is specified
 when the pod is created, so it is ignored by the scheduler).  Therefore:
 
- - the [`unschedulable`](/docs/admin/node/#manual-node-administration) field of a node is not respected
+ - The [`unschedulable`](/docs/admin/node/#manual-node-administration) field of a node is not respected
    by the DaemonSet controller.
  - DaemonSet controller can make pods even when the scheduler has not been started, which can help cluster
    bootstrap.