From b4b21fe2d8733d5d3ab98219d9ab4ff230fa2d3f Mon Sep 17 00:00:00 2001
From: Kostas Krikellas <131142368+kkrik-es@users.noreply.github.com>
Date: Tue, 1 Apr 2025 09:29:52 +0300
Subject: [PATCH] Fix notes header

---
 manage-data/data-store/data-streams/logs-data-stream.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manage-data/data-store/data-streams/logs-data-stream.md b/manage-data/data-store/data-streams/logs-data-stream.md
index b75d8dd719..d4f5ad1cb3 100644
--- a/manage-data/data-store/data-streams/logs-data-stream.md
+++ b/manage-data/data-store/data-streams/logs-data-stream.md
@@ -179,6 +179,6 @@ The `logsdb` index mode uses the following settings:
 * **`index.mapping.total_fields.ignore_dynamic_beyond_limit`**: `true`
 
 
-## Notes about upgrading to Logsdb [upgrade-to-logsdb-notes]
+## Upgrade to logsdb [upgrade-to-logsdb]
 
 Starting with version `9.0`, `logsdb` index mode is automatically applied to data streams with names matching the pattern `logs-*-*`. This default applies to Elasticsearch instances created in version `9.0` or later, as well as older instances that had no data streams matching the pattern `logs-*-*`. For the latter, you can still [configure `logsdb` index mode manually](#how-to-use-logsds).