diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
index e2c1b3fe75..b2bfd8d5fd 100644
--- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
+++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md
@@ -9,17 +9,40 @@ products:
 
 # Skip rollover [skipping-rollover]
 
-When `index.lifecycle.indexing_complete` is set to `true`, {{ilm-init}} won’t perform the rollover action on an index, even if it otherwise meets the rollover criteria. It’s set automatically by {{ilm-init}} when the rollover action completes successfully.
+You can use {{ilm}} to manage index lifecycle transitions without rolling over your indices. For example, when working with data that isn't continuously ingested, you might prefer to create a new index on a set schedule, such as the first Monday of each month. In this case, you can still use an {{ilm-init}} policy to automatically move indices through [lifecycle phases](/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md#ilm-phase-transitions) as they age and control when new indices are created by disabling the rollover action.
 
-You can set it manually to skip rollover if you need to make an exception to your normal lifecycle policy and update the alias to force a roll over, but want {{ilm-init}} to continue to manage the index. If you use the rollover API, it is not necessary to configure this setting manually.
+You can configure indices to skip rollover either as part of an {{ilm-init}} policy or manually by adjusting the index settings.
+
+
+## Skip rollover through an {{ilm-init}} policy
+
+When you [configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) in {{kib}}, you can choose whether or not rollover is enabled.
+
+To update the automatic rollover setting in an {{ilm-init}} policy:
+
+1. Go to **Stack Management > Index Lifecycle Policies**.
+
+1. Select a policy to update, and from the **Actions** menu select **Edit**.
+
+1. In the **Hot phase** section, expand the advanced settings.
+
+1. Update the **Enable rollover** option to enable or disable automatic rollover.
+
+    ![Create policy page](/manage-data/images/elasticsearch-reference-create-policy.png "")
+
+
+## Skip rollover manually
+
+When the [`index.lifecycle.indexing_complete`](elasticsearch://reference/elasticsearch/configuration-reference/index-lifecycle-management-settings.md#_index_level_settings_2) setting is `true`, {{ilm-init}} won’t perform the rollover action on an index, even if it otherwise meets the rollover criteria. This setting is updated to `true` automatically by {{ilm-init}} when the rollover action completes successfully.
+
+You can update this setting manually to skip rollover if, for instance, you need to make an exception to your normal lifecycle policy and update the alias to force a rollover, but you want {{ilm-init}} to continue to manage the index. If you use the rollover API rather than an {{ilm-init}} policy to roll over indices, it is not necessary to configure this setting manually.
 
 If an index’s lifecycle policy is removed, this setting is also removed.
 
 ::::{important} 
-When `index.lifecycle.indexing_complete` is `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md).
+When `index.lifecycle.indexing_complete` is set to `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md).
 ::::
 
-
 For example, if you need to change the name of new indices in a series while retaining previously-indexed data in accordance with your configured policy, you can:
 
 1. Create a template for the new index pattern that uses the same policy.