diff --git a/docs/admin/multiple-schedulers.md b/docs/admin/multiple-schedulers.md
index e4f1b4a9f1..30cba6c3ea 100644
--- a/docs/admin/multiple-schedulers.md
+++ b/docs/admin/multiple-schedulers.md
@@ -61,7 +61,7 @@ config. Save it as `my-scheduler.yaml`:
 {% include code.html language="yaml" file="multiple-schedulers/my-scheduler.yaml" ghlink="/docs/admin/multiple-schedulers/my-scheduler.yaml" %}
 
 An important thing to note here is that the name of the scheduler specified as an
-argument to the scheduler command in the container spec should be unique. This is the name that is matched against the value of the optional `spec.schedulername` on pods, to determine whether this scheduler is responsible for scheduling a particular pod.
+argument to the scheduler command in the container spec should be unique. This is the name that is matched against the value of the optional `spec.schedulerName` on pods, to determine whether this scheduler is responsible for scheduling a particular pod.
 
 Please see the
 [kube-scheduler documentation](/docs/admin/kube-scheduler/) for
@@ -112,7 +112,7 @@ scheduler in that pod spec. Let's look at three examples.
 
   {% include code.html language="yaml" file="multiple-schedulers/pod2.yaml" ghlink="/docs/admin/multiple-schedulers/pod2.yaml" %}
 
-  A scheduler is specified by supplying the scheduler name as a value to `spec.schedulername`. In this case, we supply the name of the
+  A scheduler is specified by supplying the scheduler name as a value to `spec.schedulerName`. In this case, we supply the name of the
   default scheduler which is `default-scheduler`.
 
   Save this file as `pod2.yaml` and submit it to the Kubernetes cluster.
@@ -126,7 +126,7 @@ scheduler in that pod spec. Let's look at three examples.
   {% include code.html language="yaml" file="multiple-schedulers/pod3.yaml" ghlink="/docs/admin/multiple-schedulers/pod3.yaml" %}
 
   In this case, we specify that this pod should be scheduled using the scheduler that we
-  deployed - `my-scheduler`. Note that the value of `spec.schedulername` should match the name supplied to the scheduler
+  deployed - `my-scheduler`. Note that the value of `spec.schedulerName` should match the name supplied to the scheduler
   command as an argument in the deployment config for the scheduler.
 
   Save this file as `pod3.yaml` and submit it to the Kubernetes cluster.
diff --git a/docs/admin/multiple-schedulers/pod2.yaml b/docs/admin/multiple-schedulers/pod2.yaml
index 26b0376967..e1e280ff09 100644
--- a/docs/admin/multiple-schedulers/pod2.yaml
+++ b/docs/admin/multiple-schedulers/pod2.yaml
@@ -5,7 +5,7 @@ metadata:
   labels:
     name: multischeduler-example
 spec:
-  schedulername: default-scheduler
+  schedulerName: default-scheduler
   containers:
   - name: pod-with-default-annotation-container
-    image: gcr.io/google_containers/pause:2.0
\ No newline at end of file
+    image: gcr.io/google_containers/pause:2.0
diff --git a/docs/admin/multiple-schedulers/pod3.yaml b/docs/admin/multiple-schedulers/pod3.yaml
index e64070abfa..63be0e0aa3 100644
--- a/docs/admin/multiple-schedulers/pod3.yaml
+++ b/docs/admin/multiple-schedulers/pod3.yaml
@@ -5,7 +5,7 @@ metadata:
   labels:
     name: multischeduler-example
 spec:
-  schedulername: my-scheduler
+  schedulerName: my-scheduler
   containers:
   - name: pod-with-second-annotation-container
-    image: gcr.io/google_containers/pause:2.0
\ No newline at end of file
+    image: gcr.io/google_containers/pause:2.0