From 6f9b4ab4b695e4730529031d37c8edcfa048c7cb Mon Sep 17 00:00:00 2001 From: James Rodewig <40268737+jrodewig@users.noreply.github.com> Date: Thu, 14 Jan 2021 10:07:34 -0500 Subject: [PATCH] [DOCS] Fix ILM user note --- docs/reference/ilm/apis/put-lifecycle.asciidoc | 4 ++-- docs/reference/ilm/ilm-index-lifecycle.asciidoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/ilm/apis/put-lifecycle.asciidoc b/docs/reference/ilm/apis/put-lifecycle.asciidoc index c30c9367d50..f5361820437 100644 --- a/docs/reference/ilm/apis/put-lifecycle.asciidoc +++ b/docs/reference/ilm/apis/put-lifecycle.asciidoc @@ -21,8 +21,8 @@ definitions of policy components. cluster privilege to use this API. You must also have the `manage` index privilege on all indices being managed by `policy`. {ilm-init} performs operations as the user who last updated the policy. {ilm-init} only has the -<> assigned to the user at the time of the -last policy update. +<> assigned to the user at the time of the last policy +update. [[ilm-put-lifecycle-desc]] ==== {api-description-title} diff --git a/docs/reference/ilm/ilm-index-lifecycle.asciidoc b/docs/reference/ilm/ilm-index-lifecycle.asciidoc index 864af2e647a..30b6aaf7862 100644 --- a/docs/reference/ilm/ilm-index-lifecycle.asciidoc +++ b/docs/reference/ilm/ilm-index-lifecycle.asciidoc @@ -26,8 +26,8 @@ When an index rolls over, a manually-applied policy isn't automatically applied If you use {es}'s security features, {ilm-init} performs operations as the user who last updated the policy. {ilm-init} only has the -<> assigned to the user at the time of the -last policy update. +<> assigned to the user at the time of the last policy +update. [discrete] [[ilm-phase-transitions]]