anchor.diff:  properties of the default number of routing shards will then apply to the
   newly split index.
   
  -[float]
  -==== How does splitting work?
  -
  -Splitting works as follows:
  -
  -* First, it creates a new target index with the same definition as the source
  +
  +[[how-split-works]]
  +===== How splitting works
  +
  +A split operation:
  +
  +. Creates a new target index with the same definition as the source
     index, but with a larger number of primary shards.
   
  -* Then it hard-links segments from the source index into the target index. (If
  +. Hard-links segments from the source index into the target index. (If
     the file system doesn't support hard-linking, then all segments are copied
     into the new index, which is a much more time consuming process.)
   
  -* Once the low level files are created all documents will be `hashed` again to delete
  +. Hashes all documents again, after low level files are created, to delete
     documents that belong to a different shard.
   
  -* Finally, it recovers the target index as though it were a closed index which
  +. Recovers the target index as though it were a closed index which
     had just been re-opened.
   
  -[float]
  +
   [[incremental-resharding]]
  -==== Why doesn't Elasticsearch support incremental resharding?
  +===== Why doesn't Elasticsearch support incremental resharding?
   
   Going from `N` shards to `N+1` shards, aka. incremental resharding, is indeed a
   feature that is supported by many key-value stores. Adding a new shard and
  
positive.code: become `active`. At that  point, Elasticsearch will try to allocate any
  replicas and may decide to relocate the primary shard to another node.
  
  [float]
  ==== Wait For Active Shards
  
  Because the split operation creates a new index to split the shards to,
  the <<create-index-wait-for-active-shards,wait for active shards>> setting
  on index creation applies to the split index action as well.
  
negative.code: 
  [source,console]
  --------------------------------------------------
  POST /my_source_index/_split/my_target_index
  {
    "settings": {
      "index.number_of_shards": 5 <1>
  