diff --git a/docs/tasks/administer-cluster/highly-available-master.md b/docs/tasks/administer-cluster/highly-available-master.md
index e15a769770..f6519fad53 100644
--- a/docs/tasks/administer-cluster/highly-available-master.md
+++ b/docs/tasks/administer-cluster/highly-available-master.md
@@ -92,11 +92,11 @@ $ KUBE_GCE_ZONE=replica-zone KUBE_REPLICATE_EXISTING_MASTER=true ./cluster/kube-
 
 ## Best practices for replicating masters for HA clusters
 
-* Try to place masters replicas in different zones. During a zone failure, all master placed inside the zone will fail.
+* Try to place master replicas in different zones. During a zone failure, all masters placed inside the zone will fail.
 To survive zone failure, also place nodes in multiple zones
 (see [multiple-zones](/docs/admin/multiple-zones/) for details).
 
-* Do not use a cluster with two master replicas. Consensus on a two replica cluster requires both replicas running when changing persistent state.
+* Do not use a cluster with two master replicas. Consensus on a two-replica cluster requires both replicas running when changing persistent state.
 As a result, both replicas are needed and a failure of any replica turns cluster into majority failure state.
 A two-replica cluster is thus inferior, in terms of HA, to a single replica cluster.