From 19d5558bf515aca14440e5852c35d5672dab60ca Mon Sep 17 00:00:00 2001
From: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Date: Tue, 15 Jun 2021 16:38:36 -0400
Subject: [PATCH] [DOCS] Clone index API doesn't apply index templates or
 settings (#74138)

Changes:
* Notes that Elasticsearch doesn't apply index templates to cloned indices.
* Notes the clone API doesn't copy index settings.
---
 docs/reference/indices/clone-index.asciidoc | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/reference/indices/clone-index.asciidoc b/docs/reference/indices/clone-index.asciidoc
index 5ad9fd8d2c58f..5b824bfff24ae 100644
--- a/docs/reference/indices/clone-index.asciidoc
+++ b/docs/reference/indices/clone-index.asciidoc
@@ -56,10 +56,11 @@ and then the previous write index can be cloned.
 Use the clone index API to clone an existing index into a new index, where each
 original primary shard is cloned into a new primary shard in the new index.
 
-IMPORTANT: Cloning doesn't copy index metadata. This metadata includes aliases,
-{ilm-init} phase definitions, and {ccr-init} follower information. For example,
-if you clone a {ccr-init} follower index, the resulting clone won't be a
-follower index.
+IMPORTANT: {es} doesn't apply index templates to the resulting index. The API
+also doesn't copy index settings or metadata from the original index. Index
+metadata includes aliases, {ilm-init} phase definitions, and {ccr-init} follower
+information. For example, if you clone a {ccr-init} follower index, the
+resulting clone won't be a follower index.
 
 [[cloning-works]]
 ===== How cloning works