Fixing links

Author: kosabogi

deploy-manage/tools/snapshot-and-restore.md

@@ -81,7 +81,7 @@ By default, a snapshot of a cluster contains the cluster state, all regular data
 - [Ingest pipelines](/manage-data/ingest/transform-enrich/ingest-pipelines.md)
 - [ILM policies](/manage-data/lifecycle/index-lifecycle-management.md)
 - [Stored scripts](/explore-analyze/scripting/modules-scripting-using.md#script-stored-scripts)
-- For snapshots taken after 7.12.0, [feature states](#feature-states)
+- For snapshots taken after 7.12.0, [feature states](#feature-state)
 
 You can also take snapshots of only specific data streams or indices in the cluster. A snapshot that includes a data stream or index automatically includes its aliases. When you restore a snapshot, you can choose whether to restore these aliases.
 
@@ -159,7 +159,7 @@ Reindexing from remote can take significantly longer than restoring a snapshot.
 
 A copy of the data directories of a cluster’s nodes does not work as a backup because it is not a consistent representation of their contents at a single point in time. You cannot fix this by shutting down nodes while making the copies, nor by taking atomic filesystem-level snapshots, because Elasticsearch has consistency requirements that span the whole cluster. You must use the built-in snapshot functionality for cluster backups.
 
-### Repository contents
+### Repository contents [snapshot-repository-contents]
 
 **Don’t modify anything within the repository or run processes that might interfere with its contents.** If something other than Elasticsearch modifies the contents of the repository then future snapshot or restore operations may fail, reporting corruption or other data inconsistencies, or may appear to succeed having silently lost some of your data.
 

deploy-manage/tools/snapshot-and-restore/restore-snapshot.md

@@ -14,7 +14,7 @@ This guide shows you how to restore a snapshot. Snapshots are a convenient way t
 In this guide, you’ll learn how to:
 
 - [Get a list of available snapshots](#get-a-list-of-available-snapshots)
-- [Restore an index or data stream from a snapshot](#restore-an-index-or-data-stream)
+- [Restore an index or data stream from a snapshot](#restore-index-data-stream)
 - [Restore a feature state](#restore-feature-state)
 - [Restore an entire cluster](#restore-entire-cluster)
 - [Monitor the restore operation](#monitor-restore)
@@ -70,7 +70,7 @@ By default, a restore request attempts to restore all regular indices and regula
 
 If you’re restoring data to a pre-existing cluster, use one of the following methods to avoid conflicts with existing indices and data streams:
 
-- [Delete and restore](#delete-and-restore)
+- [Delete and restore](#delete-restore)
 - [Rename on restore](#rename-on-restore)
 
 ### Delete and restore [delete-restore]

raw-migrated-files/elasticsearch/elasticsearch-reference/snapshot-restore.md

@@ -109,9 +109,7 @@ Any index you restore from a snapshot must also be compatible with the current c
 | 7.2–7.17              | ❌  | ❌      | ✅      | ✅      | ✅      |
 | 8.0–8.17              | ❌  | ❌      | ❌      | ✅      | ✅      |
 
-[1] Supported with [archive indices](../../../deploy-manage/tools/snapshot-and-restore.md#fn-archive).
-
-1. Supported with [archive indices](../../../deploy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md).
+[1] Supported with [archive indices](../../../deploy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md).
 
 You can’t restore an index to an earlier version of {{es}}. For example, you can’t restore an index created in 7.6.0 to a cluster running 7.5.0.