[DOCS] Fix redirects and anchors (#65472)

docs/reference/datatiers.asciidoc

@@ -106,7 +106,7 @@ If you set the tier preference to `null`, {es} ignores the data tier roles durin
 === Automatic data tier migration
 
 {ilm-init} automatically transitions managed
-indices through the available data tiers using the <<ilm-migrate-action, migrate>> action. 
+indices through the available data tiers using the <<ilm-migrate, migrate>> action. 
 By default, this action is automatically injected in every phase. 
 You can explicitly specify the migrate action to override the default behavior, 
-or use the <<ilm-allocate-action, allocate action>> to manually specify allocation rules.
+or use the <<ilm-allocate, allocate action>> to manually specify allocation rules.

docs/reference/how-to/size-your-shards.asciidoc

@@ -260,7 +260,7 @@ POST /my-index-000001/_shrink/my-shrunken-index-000001
 ----
 // TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":2,"blocks.write":true}}\n/]
 
-{ilm-init} also has a <<ilm-shrink-action,shrink action>> for indices in the
+{ilm-init} also has a <<ilm-shrink,shrink action>> for indices in the
 warm phase.
 
 [discrete]

docs/reference/ilm/actions/ilm-delete.asciidoc

@@ -14,7 +14,7 @@ beta:[]
 (Optional, Boolean)
 Deletes the searchable snapshot created in the cold phase. 
 Defaults to `true`.
-This option is applicable when the <<ilm-searchable-snapshot-action,searchable
+This option is applicable when the <<ilm-searchable-snapshot,searchable
 snapshot>> action is used in the cold phase.
 
 [[ilm-delete-action-ex]]

docs/reference/ilm/actions/ilm-rollover.asciidoc

@@ -10,7 +10,7 @@ IMPORTANT: If the rollover action is used on a <<ccr-put-follow,follower index>>
 policy execution waits until the leader index rolls over (or is
 <<skipping-rollover, otherwise marked complete>>),
 then converts the follower index into a regular index with the
-<<ilm-unfollow-action, Unfollow action>>.
+<<ilm-unfollow, Unfollow action>>.
 
 A rollover target can be a <<data-streams, data stream>> or an <<indices-aliases, index alias>>.
 When targeting a data stream, the new index becomes the data stream's

docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc

@@ -21,7 +21,7 @@ Using a policy that makes use of the <<ilm-rollover, rollover>> action
 in the hot phase will avoid this situation and the need for a manual rollover for future
 managed indices.
 
-By default, this snapshot is deleted by the <<ilm-delete-action, delete action>> in the delete phase.
+By default, this snapshot is deleted by the <<ilm-delete, delete action>> in the delete phase.
 To keep the snapshot, set `delete_searchable_snapshot` to `false` in the delete action.
 
 [[ilm-searchable-snapshot-options]]

docs/reference/ilm/actions/ilm-shrink.asciidoc

@@ -19,7 +19,7 @@ If the shrink action is used on a <<ccr-put-follow,follower index>>,
 policy execution waits until the leader index rolls over (or is
 <<skipping-rollover, otherwise marked complete>>), 
 then converts the follower index into a regular index with the 
-<<ilm-unfollow-action,the Unfollow action>> before performing the shrink operation.
+<<ilm-unfollow,the Unfollow action>> before performing the shrink operation.
 
 If the managed index is part of a <<data-streams, data stream>>,
 the shrunken index replaces the original index in the data stream.

docs/reference/ilm/actions/ilm-unfollow.asciidoc

@@ -11,9 +11,9 @@ You can also use unfollow directly when moving follower indices through the life
 Has no effect on indices that are not followers, phase execution just moves to the next action.
 
 [NOTE]
-This action is triggered automatically by the <<ilm-rollover-action, rollover>>,
-<<ilm-shrink-action, shrink>>, and
-<<ilm-searchable-snapshot-action, searchable snapshot>> actions when they are
+This action is triggered automatically by the <<ilm-rollover, rollover>>,
+<<ilm-shrink, shrink>>, and
+<<ilm-searchable-snapshot, searchable snapshot>> actions when they are
 applied to follower indices.
 
 This action waits until is it safe to convert a follower index into a regular index. 
@@ -21,7 +21,7 @@ The following conditions must be met:
 
 * The leader index must have `index.lifecycle.indexing_complete` set to `true`.
 This happens automatically if the leader index is rolled over using the
-<<ilm-rollover-action, rollover>> action, and can be set manually using
+<<ilm-rollover, rollover>> action, and can be set manually using
 the <<indices-update-settings,index settings>> API.
 * All operations performed on the leader index have been replicated to the follower index. 
 This ensures that no operations are lost when the index is converted.

docs/reference/ilm/ilm-actions.asciidoc

@@ -3,49 +3,48 @@
 [[ilm-actions]]
 == Index lifecycle actions
 
-[[ilm-allocate-action]]
 <<ilm-allocate,Allocate>>::
 Move shards to nodes with different performance characteristics
 and reduce the number of replicas. 
 
-[[ilm-delete-action]]<<ilm-delete,Delete>>::
+<<ilm-delete,Delete>>::
 Permanently remove the index.
 
-[[ilm-forcemerge-action]]<<ilm-forcemerge,Force merge>>::
+<<ilm-forcemerge,Force merge>>::
 Reduce the number of index segments and purge deleted documents.
 Makes the index read-only.
 
-[[ilm-freeze-action]]<<ilm-freeze,Freeze>>::
+<<ilm-freeze,Freeze>>::
 Freeze the index to minimize its memory footprint.
 
-[[ilm-migrate-action]]<<ilm-migrate,Migrate>>::
+<<ilm-migrate,Migrate>>::
 Move the index shards to the <<data-tiers, data tier>> that corresponds
 to the current {ilm-init] phase.
 
-[[ilm-readonly-action]]<<ilm-readonly,Read only>>::
+<<ilm-readonly,Read only>>::
 Block write operations to the index. 
   
-[[ilm-rollover-action]]<<ilm-rollover,Rollover>>::
+<<ilm-rollover,Rollover>>::
 Remove the index as the write index for the rollover alias and 
 start indexing to a new index.
 
-[[ilm-searchable-snapshot-action]]<<ilm-searchable-snapshot, Searchable snapshot>>::
+<<ilm-searchable-snapshot, Searchable snapshot>>::
 beta:[]
 Take a snapshot of the managed index in the configured repository
 and mount it as a searchable snapshot.
 
-[[ilm-set-priority-action]]<<ilm-set-priority,Set priority>>::
+<<ilm-set-priority,Set priority>>::
 Lower the priority of an index as it moves through the lifecycle
 to ensure that hot indices are recovered first. 
 
-[[ilm-shrink-action]]<<ilm-shrink,Shrink>>::
+<<ilm-shrink,Shrink>>::
 Reduce the number of primary shards by shrinking the index into a new index.
 
-[[ilm-unfollow-action]]<<ilm-unfollow,Unfollow>>::
+<<ilm-unfollow,Unfollow>>::
 Convert a follower index to a regular index.
 Performed automatically before a rollover, shrink, or searchable snapshot action. 
 
-[[ilm-wait-for-snapshot-action]]<<ilm-wait-for-snapshot,Wait for snapshot>>::
+<<ilm-wait-for-snapshot,Wait for snapshot>>::
 Ensure that a snapshot exists before deleting the index. 
 
 include::actions/ilm-allocate.asciidoc[]

docs/reference/ilm/ilm-index-lifecycle.asciidoc

@@ -87,12 +87,12 @@ the rollover criteria, it could be 20 minutes before the rollover is complete.
   - <<ilm-shrink,Shrink>>
   - <<ilm-forcemerge,Force Merge>>
 * Cold
-  - <<ilm-set-priority-action,Set Priority>>
-  - <<ilm-unfollow-action,Unfollow>>
+  - <<ilm-set-priority,Set Priority>>
+  - <<ilm-unfollow,Unfollow>>
   - <<ilm-allocate,Allocate>>
   - <<ilm-freeze,Freeze>>
   - <<ilm-searchable-snapshot, Searchable Snapshot>>
 * Delete
-  - <<ilm-wait-for-snapshot-action,Wait For Snapshot>>
+  - <<ilm-wait-for-snapshot,Wait For Snapshot>>
   - <<ilm-delete,Delete>>
   

docs/reference/redirects.asciidoc

@@ -611,6 +611,11 @@ See <<snapshot-restore>>.
 
 See <<snapshots-repository-plugins>>.
 
+[role="exclude",id="_changing_index_settings_during_restore"]
+==== Change index settings during restore
+
+See <<change-index-settings-during-restore>>.
+
 [role="exclude",id="restore-snapshot"]
 === Restore snapshot
 
@@ -1249,7 +1254,7 @@ See <<transforms>>.
 
 See <<search-aggregations-matrix-stats-aggregation>>.
 
-[[fielddata]]
+[role="exclude",id="fielddata"]
 === `fielddata` mapping parameter
 
 See <<fielddata-mapping-param>>.

docs/reference/snapshot-restore/restore-snapshot.asciidoc

@@ -122,6 +122,7 @@ restored in this case and all missing shards will be recreated empty.
 
 
 [discrete]
+[[change-index-settings-during-restore]]
 === Changing index settings during restore
 
 Use the <<restore-snapshot-api-index-settings,`index_settings`>> parameter