Minor improvements for Configure a lifecycle policy

Fixes #1553 I've added the note formatting for the section that mentions how time is calculated from rollover, similar to the Phase transitions page and slightly reworded the link text to the rollover action docs, to emphasize the difference between it and the previous link to the rollover conceptual page.

Author: yetanothertw

manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md

@@ -56,8 +56,8 @@ To add an ILM policy to an {{es}} cluster:
 
 1. Specify a name for the lifecycle policy. Later on, when you create an index template to define how indices are created, you'll use this name to assign the lifecycle policy to each index.
 
-1. In the **Hot phase**, by default an ILM-managed index [rolls over](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-rollover.md) when either:
-    * It reaches 30 days of age.
+1. In the **Hot phase**, a [rollover index lifecycle action](elasticsearch://reference/elasticsearch/index-lifecycle-actions/ilm-rollover.md) is executed by default when either:
+    * The index reaches 30 days of age.
     * One or more primary shards reach 50 GB in size.
 
     Disable **Use recommended defaults** to adjust these values or to roll over based on the size of the primary shard, the number of documents in the primary shard, or the total number of documents in the index.
@@ -72,7 +72,9 @@ To add an ILM policy to an {{es}} cluster:
 
     ![Create policy page](/manage-data/images/elasticsearch-reference-create-policy-downsample.png "")
 
+    ::::{note}
     Note that for each phase after the hot phase, you have the option to move the data into the next phase after a certain duration of time. This duration is calculated from the time of the index rollover and not from the time the index is created.
+    ::::
 
 
 1. For the final phase that's enabled, choose to either keep the data in the phase forever or delete the data after a specified period of time.