diff --git a/docs/migrating.md b/docs/migrating.md
index 3e1f85c461..524b67444d 100644
--- a/docs/migrating.md
+++ b/docs/migrating.md
@@ -55,10 +55,11 @@ Instead of removing Deployment you can scale it down to zero and reference it fr
 1. Create a Rollout resource.
 1. Reference an existing Deployment using `workloadRef` field.
 1. In the `workloadRef` field set the `scaleDown` attribute, which specifies how the Deployment should be scaled down. There are three options available:
-* "never": the Deployment is not scaled down
-* "onsuccess": the Deployment is scaled down after the Rollout becomes healthy
-* "progressively": as the Rollout is scaled up the Deployment is scaled down.
-Alternatively, manually scale down an existing Deployment by changing replicas field of an existing Deployment to zero.
+   * `never`: the Deployment is not scaled down
+   * `onsuccess`: the Deployment is scaled down after the Rollout becomes healthy
+   * `progressively`: as the Rollout is scaled up the Deployment is scaled down.
+
+   Alternatively, manually scale down an existing Deployment by changing replicas field of an existing Deployment to zero.
 1. To perform an update, the change should be made to the Pod template field of the Deployment.
 
 Below is an example of a Rollout resource referencing a Deployment.