Update VReplication Related User Guides

content/en/docs/16.0/reference/vreplication/materialize.md

@@ -33,12 +33,13 @@ Be careful to avoid using the `INSTANT ADD COLUMN` feature in [MySQL 8.0+](https
 A comma-separated list of cell names or cell aliases. This list is used by VReplication to determine which
 cells should be used to pick a tablet for selecting data from the source keyspace.<br><br>
 
+</div>
+
 ###### Uses
 
 * Improve performance by using picking a tablet in cells in network proximity with the target
 * To reduce bandwidth costs by skipping cells that are in different availability zones
 * Select cells where replica lags are lower
-</div>
 
 #### --tablet_types 
 **optional**\
@@ -47,7 +48,8 @@ cells should be used to pick a tablet for selecting data from the source keyspac
 
 <div class="cmd">
 
-Source tablet types to replicate from (e.g. PRIMARY, REPLICA, RDONLY).
+Source tablet types to replicate from (e.g. PRIMARY, REPLICA, RDONLY). The value
+specified impacts [tablet selection](../tablet_selection/) for the workflow.
 
 </div>
 
@@ -56,8 +58,6 @@ Source tablet types to replicate from (e.g. PRIMARY, REPLICA, RDONLY).
 * To reduce the load on PRIMARY tablets by using REPLICAs or RDONLYs
 * Reducing lag by pointing to PRIMARY
 
-</div>
-
 #### JSON spec details
 <div class="cmd">
 
@@ -89,7 +89,6 @@ Materialize '{"workflow": "product_sales", "source_keyspace": "commerce", "targe
     "cell": "zone1", "tablet_types": "REPLICA"}'
 ```
 
-
 ### A Materialize Workflow
 
 Once you decide on your materialization requirements, you need to initiate a VReplication workflow as follows:

content/en/docs/16.0/reference/vreplication/movetables.md

@@ -233,9 +233,9 @@ in the replication stream from the source. The values can be as follows:
 
 {{< warning >}}
 We caution against against using `EXEC` or `EXEC_IGNORE` for the following reasons:
-  * You may want a different schema on the target.
-  * You may want to apply the DDL in a different way on the target.
-  * The DDL may take a long time to apply on the target and may disrupt replication, performance, and query execution (if serving  traffic from the target) while it is being applied.
+  * You may want a different schema on the target
+  * You may want to apply the DDL in a different way on the target
+  * The DDL may take a long time to apply on the target and may disrupt replication, performance, and query execution (if serving  traffic from the target) while it is being applied
 
 If you do use one of these two DDL actions then you should also enable the [VReplication Schema Tracking](../../../../design-docs/vreplication/vstream/tracker/).
 {{< /warning >}}

content/en/docs/16.0/reference/vreplication/reshard.md

@@ -223,9 +223,9 @@ in the replication stream from the source. The values can be as follows:
 
 {{< warning >}}
 We caution against against using `EXEC` or `EXEC_IGNORE` for the following reasons:
-  * You may want a different schema on the target.
-  * You may want to apply the DDL in a different way on the target.
-  * The DDL may take a long time to apply on the target and may disrupt replication, performance, and query execution (if serving  traffic from the target) while it is being applied.
+  * You may want a different schema on the target
+  * You may want to apply the DDL in a different way on the target
+  * The DDL may take a long time to apply on the target and may disrupt replication, performance, and query execution (if serving  traffic from the target) while it is being applied
 
 If you do use one of these two DDL actions then you should also enable the [VReplication Schema Tracking](../../../../design-docs/vreplication/vstream/tracker/).
 {{< /warning >}}

content/en/docs/16.0/reference/vreplication/vreplication.md

@@ -154,6 +154,15 @@ in the replication stream from the source. The values can be as follows:
 * `EXEC`: Apply the DDL, but stop if an error is encountered while applying it.
 * `EXEC_IGNORE`: Apply the DDL, but ignore any errors and continue replicating.
 
+{{< warning >}}
+We caution against against using `EXEC` or `EXEC_IGNORE` for the following reasons:
+  * You may want a different schema on the target
+  * You may want to apply the DDL in a different way on the target
+  * The DDL may take a long time to apply on the target and may disrupt replication, performance, and query execution (if serving  traffic from the target) while it is being applied
+
+If you do use one of these two DDL actions then you should also enable the [VReplication Schema Tracking](../../../../design-docs/vreplication/vstream/tracker/).
+{{< /warning >}}
+
 ### Failover Continuation
 
 If a failover is performed on the target keyspace/shard, the new primary will

content/en/docs/16.0/user-guides/migration/_index.md

@@ -1,5 +1,5 @@
 ---
 title: Migration
-description: User guides covering migration to Vitess
+description: User guides covering data migrations into Vitess
 weight: 3
 ---