anchor.diff:  --------------------------------------------------
   
   [[multiple-component-templates]]
  -===== Composing multiple component templates
  +===== Composing aliases, mappings, and settings
   
   When multiple component templates are specified in the `composed_of` field for an index template,
   they are merged in the order specified, meaning that later component templates override earlier
  -component templates.
  -
  -For two component templates, the order they are specified changes the number of shards for an index:
  +component templates. Any mappings, settings, or aliases from the parent index template are merged
  +in next. Finally, any configuration on the index request itself is merged.
  +
  +In this example, the order of the two component templates changes the number of shards for an
  +index:
   
   [source,console]
   --------------------------------------------------
  
positive.code: `composed_of`::
  (Optional, array of strings)
  An ordered list of component template names. Component templates are merged in the order
  specified, meaning that the last component template specified has the highest precedence. See 
  <<multiple-component-templates,Composing multiple component templates>> for an example.
  
  `priority`::
  
negative.code: [source,console]
  --------------------------------------------------
  GET /_index_template
  --------------------------------------------------
  