From 5ab0bff6eb9d245e2c7b04949f4572df1f37ee0d Mon Sep 17 00:00:00 2001 From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Date: Mon, 16 Sep 2024 16:37:09 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Nathan Bower Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --- _im-plugin/index-context.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_im-plugin/index-context.md b/_im-plugin/index-context.md index a892516159..be0dbd527d 100644 --- a/_im-plugin/index-context.md +++ b/_im-plugin/index-context.md @@ -40,7 +40,7 @@ Use the `context` setting with the Index API to add use-case-specific context. Consider the following when using the `context` parameter during index creation: 1. If you use the `context` parameter to create an index, you cannot include any settings declared in the index context during index creation or dynamic settings updates. -2. Context becomes permanent when set on an index or index-template. +2. The index context becomes permanent when set on an index or index template. When you adhere to these limitations, suggested configurations or mappings are uniformly applied on indexed data within the specified context. @@ -106,7 +106,7 @@ GET /my-metrics-index ``` -#### Create an index templates +#### Create an index template You can also use the `context` parameter when creating an index template. The following example request creates an index template with the context information as `logs`: