anchor.diff:  . Activate the warm phase and click **Settings**.
   +
   --
  +.. Set **Move data into phase when** to **30 days**. This moves indices to the
  +warm tier 30 days after rollover.
  +
  +.. Enable **Replicas** and change **Number of replicas** to **1**.
  +
  +.. Enable **Force merge** and set **Number of segments** to **1**.
  +
   [role="screenshot"]
   image::images/ilm/tutorial-ilm-modify-default-warm-phase-rollover.png[Add a warm phase with custom settings]
  -
  -.. Set *Move data into phase when* to *30 days*. This moves indices to the warm
  -tier 30 days after rollover.
  -
  -.. Enable **Replicas** and change *Number of replicas* to *1*.
  -
  -.. Enable *Force merge* and set *Number of segments* to *1*.
   --
   
  -. Activate the delete phase and set *Move data into phase when* to *90* days.
  -This deletes indices 90 days after rollover.
  +. Activate the delete phase and set **Move data into phase when** to **90**
  +days. This deletes indices 90 days after rollover.
   +
   [role="screenshot"]
   image::images/ilm/tutorial-ilm-delete-rollover.png[Add a delete phase]
  
positive.code: . Open the menu and go to **Stack Management > Index Lifecycle Policies**.
  . Select the `logs` policy.
  
  The `logs` policy uses the recommended rollover defaults: start writing to a new
  index when the current write index reaches 50GB or becomes 30 days old.
  
  To view or change the rollover settings, click **Settings** for the hot phase.
  
negative.code: 
  {es} includes the following built-in {ilm-init} policies:
  
  - `logs`
  - `metrics`
  - `synthetics`
  
  The {agent} uses these policies to manage backing indices for its data streams.
  This tutorial shows you how to use {kib}’s **Index Lifecycle Policies** to
  customize these policies based on your application's performance, resilience,
  and retention requirements.
  
  