anchor.diff:  `path.data` setting pointing at a separate data path.
   
   9. Start the new nodes and follow the rest of the
  -<<restart-cluster-rolling,rolling restart process>> for them.
  +{ref}/restart-cluster.html#restart-cluster-rolling[rolling restart process] for 
  +them.
   
   10. Ensure your cluster health is `green`, so that every shard has been
   assigned.
   
   You can alternatively add some number of single-data-path nodes to your
   cluster, migrate all your data over to these new nodes using
  -<<cluster-shard-allocation-filtering,allocation filters>>, and then remove the
  -old nodes from the cluster. This approach will temporarily double the size of
  -your cluster so it will only work if you have the capacity to expand your
  -cluster like this.
  +{ref}/modules-cluster.html#cluster-shard-allocation-filtering[allocation filters], 
  +and then remove the old nodes from the cluster. This approach will temporarily 
  +double the size of your cluster so it will only work if you have the capacity to 
  +expand your cluster like this.
   
   If you currently use multiple data paths but your cluster is not highly
   available then the you can migrate to a non-deprecated configuration by taking
  
positive.code: single machine then you must run one node for each data path.
  
  If you currently use multiple data paths in a
  <<high-availability-cluster-design,highly available cluster>> then you can
  migrate to a setup that uses a single path for each node without downtime using
  a process similar to a <<restart-cluster-rolling,rolling restart>>: shut each
  node down in turn and replace it with one or more nodes each configured to use
  a single data path. In more detail, for each node that currently has multiple
  data paths you should follow the following process. In principle you can
  
negative.code: 1. Take a snapshot to protect your data in case of disaster.
  
  2. Optionally, migrate the data away from the target node by using an
  {ref}/modules-cluster.html#cluster-shard-allocation-filtering[allocation filter]:
  +
  [source,console]
  --------------------------------------------------
  