diff --git a/docs/scheduler/strategy.md b/docs/scheduler/strategy.md
index 20f0de01e1..666e1ded76 100644
--- a/docs/scheduler/strategy.md
+++ b/docs/scheduler/strategy.md
@@ -35,7 +35,7 @@ Under the `spread` strategy, Swarm optimizes for the node with the least number
 of containers. The `binpack` strategy causes Swarm to optimize for the
 node which is most packed. Note that a container occupies resource during its life
 cycle, including `exited` state. Users should be aware of this condition to schedule
-containers. For exmaple, `spread` strategy only checks number of containers
+containers. For example, `spread` strategy only checks number of containers
 disregarding their states. A node with no active containers but high number of
 stopped containers may not be selected, defeating the purpose of load sharing.
 User could either remove stopped containers, or start stopped containers to achieve