anchor.diff:  
   A lifecycle policy specifies the phases in the index lifecycle
   and the actions to perform in each phase. A lifecycle can have up to four phases:
  -`hot`, `warm`, `cold`, and `delete`. Policies are defined in JSON 
  -and added through the {ilm-init} put policy API. 
  -
  -For example, the following request creates a `datastream_policy` with two phases:
  - 
  -* The `hot` phase defines a `rollover` action to specify that an index rolls over when it 
  +`hot`, `warm`, `cold`, and `delete`. Policies are defined in JSON
  +and added through the {ilm-init} put policy API.
  +
  +For example, the following request creates a `timeseries_policy` with two phases:
  +
  +* The `hot` phase defines a `rollover` action to specify that an index rolls over when it
   reaches either a `max_size` of 50 gigabytes or a `max_age` of 30 days.
   * The `delete` phase uses `min_age` to remove the index 90 days after rollover.
  -Note that this value is relative to the rollover time, not the index creation time. 
  +Note that this value is relative to the rollover time, not the index creation time.
   
   [source,console]
   ------------------------
  -PUT _ilm/policy/datastream_policy 
  -{
  -  "policy": {                       
  +PUT _ilm/policy/timeseries_policy
  +{
  +  "policy": {
       "phases": {
         "hot": {                      <1>
           "actions": {
  -          "rollover": {             
  +          "rollover": {
               "max_size": "50GB",     <2>
               "max_age": "30d"
             }
  
positive.code: [[ilm-gs-apply-policy]]
  === Create an index template to apply the lifecycle policy
  
  To automaticaly apply a lifecycle policy to the new write index on rollover, 
  specify the policy in the index template used to create new indices.
  
  For example, the following request creates a `datastream_template` that is applied to new indices
  whose names match the `datastream-*` index pattern. 
  The template configures two {ilm-init} settings:
  
  * `index.lifecycle.name` specifies the name of the lifecycle policy to apply to all new indices that match 
  the index pattern.  
  * `index.lifecycle.rollover_alias` specifies the index alias to be rolled over 
  when the rollover action is triggered for an index.
  
  [source,console]
  -----------------------
  PUT _template/datastream_template
  {
    "index_patterns": ["datastream-*"],                 <1>
    "settings": {
      "number_of_shards": 1,
      "number_of_replicas": 1,
      "index.lifecycle.name": "datastream_policy",      <2>
      "index.lifecycle.rollover_alias": "datastream"    <3>
    }
  }
  -----------------------
  // TEST[continued]
  
  <1> Apply the template to a new index if its name starts with `datastream-`. 
  <2> The name of the lifecycle policy to apply to each new index.
  <3> The name of the alias used to reference these indices. 
  Required for policies that use the rollover action.
  
  //////////////////////////
  
  [source,console]
  --------------------------------------------------
  DELETE /_template/datastream_template
  --------------------------------------------------
  // TEST[continued]
  
  
negative.code: [[ilm-gs-bootstrap]]
  === Bootstrap the initial time-series index
  
  To get things started, you need to bootstrap an initial index and
  designate it as the write index for the rollover alias specified in your index template.
  The name of this index must match the template's index pattern and end with a number.
  On rollover, this value is incremented to generate a name for the new index.
  
  For example, the following request creates an index called `timeseries-000001`
  and makes it the write index for the `timeseries` alias.
  
  [source,console]
  -----------------------
  PUT timeseries-000001
  {
    "aliases": {
      "timeseries": {
        "is_write_index": true
      }
    }
  