diff --git a/docs/features/anti-affinity/anti-affinity.md b/docs/features/anti-affinity/anti-affinity.md
index 3c46171d70..2a547c9c07 100644
--- a/docs/features/anti-affinity/anti-affinity.md
+++ b/docs/features/anti-affinity/anti-affinity.md
@@ -31,6 +31,7 @@ You can learn more about anti-affinity [here](https://kubernetes.io/docs/concept
 
 Repeating the above example with anti-affinity enabled, here is what happens when the `.spec.template` of the Rollout changes. Due to anti-affinity, the new pods cannot be scheduled on nodes which run the old ReplicaSet's pods.
 As a result, the cluster auto-scaler must create 2 nodes to host the new ReplicaSet's pods. In this case, pods won't be started since the scaled-down nodes are guaranteed to not have the new pods.
+
 ![ Original Rollout is running, spread across two nodes](images/solution.png)
 
 ## Enabling Anti-Affinity in Rollouts