Additional changes to PodAffinity/PodAntiAffinity Use-Case

kubernetes · Nov 13, 2017 · de1e88b · de1e88b
1 parent 0792881
commit de1e88b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md
@@ -286,7 +286,7 @@ spec:
         image: nginx:1.12-alpine
 ```
 
-if we create the above two deployments, our three node cluster could look like below.
+If we create the above two deployments, our three node cluster should look like below.
 
 |       node-1         |       node-2        |       node-3       |
 |:--------------------:|:-------------------:|:------------------:|
@@ -306,7 +306,7 @@ web-server-1287567482-6f7v5    1/1       Running   0          7m        10.192.4
 web-server-1287567482-s330j    1/1       Running   0          7m        10.192.3.2   kube-node-2
 ```
 
-Best practice is to configure these highly available stateful workloads such as redis with AntiAffinity rules for more guaranteed spreading, which we will see in the next section.
+Best practice is to configure these highly available stateful workloads such as redis with AntiAffinity rules for more guaranteed spreading.
 
 ##### Never co-located in the same node