From 19fb0d0948ac3c7960c8bf7540419b13484e2b39 Mon Sep 17 00:00:00 2001
From: Omurbek <omurbek.jk@gmail.com>
Date: Mon, 4 Oct 2021 12:30:23 +0300
Subject: [PATCH] Update policies.md

---
 _im-plugin/ism/policies.md | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/_im-plugin/ism/policies.md b/_im-plugin/ism/policies.md
index afad9396..29ac228b 100644
--- a/_im-plugin/ism/policies.md
+++ b/_im-plugin/ism/policies.md
@@ -560,7 +560,7 @@ The following sample template policy is for a rollover use case.
      "index_patterns": ["log*"],
      "template": {
       "settings": {
-       "opendistro.index_state_management.rollover_alias": "log"
+       "plugins.index_state_management.rollover_alias": "log"
       }
     }
    }
@@ -588,12 +588,6 @@ The following sample template policy is for a rollover use case.
    }
    ```
 
-5. Verify if the policy is attached to the `log-000001` index:
-
-   ```json
-   GET _opendistro/_ism/explain/log-000001?pretty
-   ```
-
 ## Example policy
 
 The following example policy implements a `hot`, `warm`, and `delete` workflow. You can use this policy as a template to prioritize resources to your indices based on their levels of activity.