[DOCS] Cleans up links to security content (#47610) (#47703)

docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc

@@ -41,13 +41,13 @@ DELETE /_ccr/auto_follow/<auto_follow_pattern_name>
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-delete-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
 This API deletes a configured collection of
-{stack-ov}/ccr-auto-follow.html[auto-follow patterns].
+<<ccr-auto-follow,auto-follow patterns>>.
 
 [[ccr-delete-auto-follow-pattern-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc

@@ -53,12 +53,12 @@ GET /_ccr/auto_follow/<auto_follow_pattern_name>
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
-This API gets configured {stack-ov}/ccr-auto-follow.html[auto-follow patterns].
+This API gets configured <<ccr-auto-follow,auto-follow patterns>>.
 This API will return the specified auto-follow pattern collection.
 
 [[ccr-get-auto-follow-pattern-path-parms]]

docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc

@@ -45,14 +45,13 @@ DELETE /_ccr/auto_follow/auto_follow_pattern_name
 * If the {es} {security-features} are enabled, you must have `read` and `monitor`
 index privileges for the leader index patterns. You must also have `manage_ccr`
 cluster privileges on the cluster that contains the follower index. For more
-information, see
+information, see <<security-privileges>>.
-{stack-ov}/security-privileges.html[Security privileges].
 
 [[ccr-put-auto-follow-pattern-desc]]
 ==== {api-description-title}
 
 This API creates a new named collection of
-{stack-ov}/ccr-auto-follow.html[auto-follow patterns] against the remote cluster
+<<ccr-auto-follow,auto-follow patterns>> against the remote cluster
 specified in the request body. Newly created indices on the remote cluster
 matching any of the specified patterns will be automatically configured as follower
 indices.

docs/reference/ccr/apis/follow/get-follow-info.asciidoc

@@ -42,8 +42,7 @@ GET /<index>/_ccr/info
 ==== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
-privileges. For more information, see
+privileges. For more information, see <<security-privileges>>.
-{stack-ov}/security-privileges.html[Security privileges].
 
 [[ccr-get-follow-info-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/get-follow-stats.asciidoc

@@ -43,7 +43,7 @@ GET /<index>/_ccr/stats
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-follow-stats-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-forget-follower.asciidoc

@@ -70,7 +70,7 @@ POST /<leader_index>/_ccr/forget_follower
 
 * If the {es} {security-features} are enabled, you must have `manage_leader_index`
 index privileges for the leader index. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ccr-post-forget-follower-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-pause-follow.asciidoc

@@ -37,7 +37,7 @@ POST /<follower_index>/_ccr/pause_follow
 
 * If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-post-pause-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-resume-follow.asciidoc

@@ -51,7 +51,7 @@ POST /<follower_index>/_ccr/resume_follow
 index privileges for the follower index. You must have `read` and `monitor`
 index privileges for the leader index. You must also have `manage_ccr` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-post-resume-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/post-unfollow.asciidoc

@@ -41,7 +41,7 @@ POST /<follower_index>/_ccr/unfollow
 
 * If the {es} {security-features} are enabled, you must have `manage_follow_index` 
 index privileges for the follower index. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].  
+<<security-privileges>>.  
 
 [[ccr-post-unfollow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/follow/put-follow.asciidoc

@@ -41,8 +41,7 @@ PUT /<follower_index>/_ccr/follow?wait_for_active_shards=1
 and `manage_follow_index` index privileges for the follower index. You must have
 `read` and `monitor` index privileges for the leader index. You must also have
 `manage_ccr` cluster privileges on the cluster that contains the follower index.
-For more information, see
+For more information, see <<security-privileges>>.
-{stack-ov}/security-privileges.html[Security privileges].
 
 [[ccr-put-follow-desc]]
 ==== {api-description-title}

docs/reference/ccr/apis/get-ccr-stats.asciidoc

@@ -42,7 +42,7 @@ GET /_ccr/stats
 
 * If the {es} {security-features} are enabled, you must have `monitor` cluster
 privileges on the cluster that contains the follower index. For more information,
-see {stack-ov}/security-privileges.html[Security privileges].
+see <<security-privileges>>.
 
 [[ccr-get-stats-desc]]
 ==== {api-description-title}

docs/reference/ccr/getting-started.asciidoc

@@ -34,7 +34,7 @@ to control which users have authority to manage {ccr}.
 By default, you can perform all of the steps in this tutorial by
 using the built-in `elastic` user. However, a password must be set for this user
 before the user can do anything. For information about how to set that password,
-see {stack-ov}/security-getting-started.html[Tutorial: Getting started with security].
+see <<security-getting-started>>.
 
 If you are performing these steps in a production environment, take extra care
 because the `elastic` user has the `superuser` role and you could inadvertently

docs/reference/commands/certutil.asciidoc

@@ -224,7 +224,7 @@ Alternatively, you can specify the `--ca-pass`, `--out`, and `--pass` parameters
 By default, this command generates a file called `elastic-certificates.p12`,
 which you can copy to the relevant configuration directory for each Elastic
 product that you want to configure. For more information, see
-{xpack-ref}/ssl-tls.html[Setting Up TLS on a Cluster].
+<<ssl-tls>>.
 
 [float]
 [[certutil-silent]]

docs/reference/commands/setup-passwords.asciidoc

@@ -4,7 +4,7 @@
 == elasticsearch-setup-passwords
 
 The `elasticsearch-setup-passwords` command sets the passwords for the
-{stack-ov}/built-in-users.html[built-in users].
+<<built-in-users,built-in users>>.
 
 [float]
 === Synopsis
@@ -21,7 +21,7 @@ bin/elasticsearch-setup-passwords auto|interactive
 
 This command is intended for use only during the initial configuration of the
 {es} {security-features}. It uses the
-{stack-ov}/built-in-users.html#bootstrap-elastic-passwords[`elastic` bootstrap password]
+<<bootstrap-elastic-passwords,`elastic` bootstrap password>>
 to run user management API requests. After you set a password for the `elastic`
 user, the bootstrap password is no longer active and you cannot use this command.
 Instead, you can change passwords by using the *Management > Users* UI in {kib}
@@ -36,7 +36,7 @@ location, ensure that the *ES_PATH_CONF* environment variable returns the
 correct path before you run the `elasticsearch-setup-passwords` command. You can
 override settings in your `elasticsearch.yml` file by using the `-E` command
 option. For more information about debugging connection failures, see
-{stack-ov}/trb-security-setup.html[`elasticsearch-setup-passwords` command fails due to connection failure].
+<<trb-security-setup>>.
 
 [float]
 === Parameters

docs/reference/commands/users-command.asciidoc

@@ -33,7 +33,7 @@ Leading or trailing whitespace is not allowed.
 
 Passwords must be at least 6 characters long.
 
-For more information, see {xpack-ref}/file-realm.html[File-based User Authentication].
+For more information, see <<file-realm>>.
 
 TIP: To ensure that {es} can read the user and role information at startup, run
 `elasticsearch-users useradd` as the same user you use to run {es}. Running the

docs/reference/glossary.asciidoc

@@ -31,7 +31,7 @@ current master node fails.
 
 The {ccr} feature enables you to replicate indices in remote clusters to your
 local cluster. For more information, see 
-{stack-ov}/xpack-ccr.html[{ccr-cap}].  
+{ref}/xpack-ccr.html[{ccr-cap}].  
   
 [[glossary-ccs]] {ccs} (CCS)::
 

docs/reference/high-availability/backup-and-restore-security-config.asciidoc

@@ -95,7 +95,7 @@ prevent non-administrators exfiltrating data.
 +
 --
 The following example creates a new user `snapshot_user` in the
-{stack-ov}/native-realm.html[native realm], but it is not important which
+<<native-realm,native realm>>, but it is not important which
 realm the user is a member of:
 
 [source,console]
@@ -202,7 +202,7 @@ Then log into one of the node hosts, navigate to {es} installation directory,
 and follow these steps:
 
 . Add a new user with the `superuser` built-in role to the
-{stack-ov}/file-realm.html[file realm].
+<<file-realm,file realm>>.
 +
 --
 For example, create a user named `restore_user`:

docs/reference/high-availability/backup-cluster-data.asciidoc

@@ -22,6 +22,6 @@ It does *not* grant privileges to create repositories, restore snapshots, or
 search within indices. Hence, the user can view and snapshot all indices, but cannot
 access or modify any data.
 
-For more information, see {stack-ov}/security-privileges.html[Security privileges]
+For more information, see <<security-privileges>>
-and {stack-ov}/built-in-roles.html[Built-in roles].
+and <<built-in-roles>>.
 ====

docs/reference/ilm/apis/delete-lifecycle.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/explain.asciidoc

@@ -41,7 +41,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 
 You must have the `view_index_metadata` or `manage_ilm` or both privileges on the indices
 being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/get-lifecycle.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` or `read_ilm` or both cluster privileges to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/get-status.asciidoc

@@ -28,7 +28,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` or `read_ilm` or both cluster privileges to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/move-to-step.asciidoc

@@ -39,7 +39,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/put-lifecycle.asciidoc

@@ -36,7 +36,7 @@ You must have the `manage_ilm` cluster privilege to use this API. You must
 also have the `manage` index privilege on all indices being managed by `policy`.
 All operations executed by {ilm} for a policy are executed as the user that
 put the latest version of a policy.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/remove-policy-from-index.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/retry-policy.asciidoc

@@ -30,7 +30,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` privileges on the indices being managed to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/slm-api.asciidoc

@@ -43,7 +43,7 @@ You must have the `manage_slm` cluster privilege to use this API. You must also
 have the `manage` index privilege on all indices being managed by `policy`. All
 operations executed by {slm} for a policy are executed as the user that put the
 latest version of a policy. For more information, see
-{stack-ov}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 ==== Example
 

docs/reference/ilm/apis/start.asciidoc

@@ -27,7 +27,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/ilm/apis/stop.asciidoc

@@ -32,7 +32,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
 ==== Authorization
 
 You must have the `manage_ilm` cluster privilege to use this API.
-For more information, see {stack-ov}/security-privileges.html[Security Privileges].
+For more information, see <<security-privileges>>.
 
 ==== Examples
 

docs/reference/licensing/delete-license.asciidoc

@@ -17,14 +17,14 @@ This API enables you to delete licensing information.
 ==== Description
 
 When your license expires, {xpack} operates in a degraded mode.  For more
-information, see {xpack-ref}/license-expiration.html[License Expiration].
+information, see {stack-ov}/license-expiration.html[License Expiration].
 
 [float]
 ==== Authorization
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/get-basic-status.asciidoc

@@ -25,8 +25,7 @@ https://www.elastic.co/subscriptions.
 ==== Authorization
 
 You must have `monitor` cluster privileges to use this API.
-For more information, see
+For more information, see <<security-privileges>>.
-{xpack-ref}/security-privileges.html[Security Privileges].
 
 [float]
 ==== Examples

docs/reference/licensing/get-license.asciidoc

@@ -35,8 +35,7 @@ https://www.elastic.co/subscriptions.
 ==== Authorization
 
 You must have `monitor` cluster privileges to use this API.
-For more information, see
+For more information, see <<security-privileges>>.
-{xpack-ref}/security-privileges.html[Security Privileges].
 
 
 [float]

docs/reference/licensing/get-trial-status.asciidoc

@@ -32,7 +32,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `monitor` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/start-basic.asciidoc

@@ -32,7 +32,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/start-trial.asciidoc

@@ -35,7 +35,7 @@ https://www.elastic.co/subscriptions.
 
 You must have `manage` cluster privileges to use this API.
 For more information, see
-{xpack-ref}/security-privileges.html[Security Privileges].
+<<security-privileges>>.
 
 [float]
 ==== Examples

docs/reference/licensing/update-license.asciidoc

@@ -160,4 +160,4 @@ curl -XPUT -u elastic 'http://<host>:<port>/_license?acknowledge=true' -H "Conte
 // NOTCONSOLE
 
 For more information about the features that are disabled when you downgrade
-your license, see {xpack-ref}/license-expiration.html[License Expiration].
+your license, see {stack-ov}/license-expiration.html[License Expiration].

docs/reference/ml/anomaly-detection/apis/close-job.asciidoc

@@ -26,7 +26,7 @@ operations, but you can still explore and navigate results.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-close-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/datafeedresource.asciidoc

@@ -9,7 +9,7 @@ A {dfeed} resource has the following properties:
   (object) If set, the {dfeed} performs aggregation searches.
   Support for aggregations is limited and should only be used with
   low cardinality data. For more information, see
-  {xpack-ref}/ml-configuring-aggregation.html[Aggregating Data for Faster Performance].
+  {stack-ov}/ml-configuring-aggregation.html[Aggregating Data for Faster Performance].
 
 `chunking_config`::
   (object) Specifies how data searches are split into time chunks.
@@ -53,7 +53,7 @@ A {dfeed} resource has the following properties:
   The <<ml-detectorconfig,detector configuration objects>> in a job can contain
   functions that use these script fields.
   For more information, see
-  {xpack-ref}/ml-configuring-transform.html[Transforming Data With Script Fields].
+  {stack-ov}/ml-configuring-transform.html[Transforming Data With Script Fields].
 
 `scroll_size`::
   (unsigned integer) The `size` parameter that is used in {es} searches.

docs/reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc

@@ -18,7 +18,7 @@ Deletes scheduled events from a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-calendar-event-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-calendar-job.asciidoc

@@ -18,7 +18,7 @@ Deletes {anomaly-jobs} from a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-calendar-job-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/delete-calendar.asciidoc

@@ -18,7 +18,7 @@ Deletes a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-calendar-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-datafeed.asciidoc

@@ -22,7 +22,7 @@ Deletes an existing {dfeed}.
 can delete it.
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-datafeed-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/delete-expired-data.asciidoc

@@ -18,7 +18,7 @@ Deletes expired and unused machine learning data.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-expired-data-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-filter.asciidoc

@@ -18,7 +18,7 @@ Deletes a filter.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-filter-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-forecast.asciidoc

@@ -22,7 +22,7 @@ Deletes forecasts from a {ml} job.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-delete-forecast-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-job.asciidoc

@@ -17,8 +17,7 @@ Deletes an existing {anomaly-job}.
 ==== {api-prereq-title}
 
 * If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
-cluster privileges to use this API. See
+cluster privileges to use this API. See <<security-privileges>>.
-{stack-ov}/security-privileges.html[Security privileges].
 
 [[ml-delete-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/delete-snapshot.asciidoc

@@ -17,8 +17,7 @@ Deletes an existing model snapshot.
 ==== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
+`manage` cluster privileges to use this API. See <<security-privileges>>.
-{stack-ov}/security-privileges.html[Security privileges].
 
 [[ml-delete-snapshot-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/eventresource.asciidoc

@@ -24,4 +24,4 @@ An events resource has the following properties:
  in milliseconds since the epoch or ISO 8601 format.
 
 For more information, see
-{xpack-ref}/ml-calendars.html[Calendars and Scheduled Events].
+{stack-ov}/ml-calendars.html[Calendars and Scheduled Events].

docs/reference/ml/anomaly-detection/apis/find-file-structure.asciidoc

@@ -21,7 +21,7 @@ suitable to be ingested into {es}.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml` or
 `monitor` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-find-file-structure-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/flush-job.asciidoc

@@ -18,7 +18,7 @@ Forces any buffered data to be processed by the job.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-flush-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/forecast.asciidoc

@@ -18,7 +18,7 @@ Predicts the future behavior of a time series by using its historical behavior.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-forecast-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-bucket.asciidoc

@@ -23,8 +23,8 @@ Retrieves {anomaly-job} results for one or more buckets.
 need `read` index privilege on the index that stores the results. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
 privileges. For more information, see
-{stack-ov}/security-privileges.html[Security privileges] and
+<<security-privileges>> and
-{stack-ov}/built-in-roles.html[Built-in roles].
+<<built-in-roles>>.
 
 [[ml-get-bucket-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-calendar-event.asciidoc

@@ -20,7 +20,7 @@ Retrieves information about the scheduled events in calendars.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-calendar-event-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-calendar.asciidoc

@@ -20,7 +20,7 @@ Retrieves configuration information for calendars.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-calendar-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-category.asciidoc

@@ -22,8 +22,8 @@ Retrieves {anomaly-job} results for one or more categories.
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
 need `read` index privilege on the index that stores the results. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See {stack-ov}/security-privileges.html[Security privileges] and
+privileges. See <<security-privileges>> and
-{stack-ov}/built-in-roles.html[Built-in roles].
+<<built-in-roles>>.
 
 [[ml-get-category-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-datafeed-stats.asciidoc

@@ -26,7 +26,7 @@ Retrieves usage information for {dfeeds}.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-datafeed-stats-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-datafeed.asciidoc

@@ -26,7 +26,7 @@ Retrieves configuration information for {dfeeds}.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-datafeed-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-filter.asciidoc

@@ -20,7 +20,7 @@ Retrieves filters.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-filter-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-influencer.asciidoc

@@ -20,8 +20,8 @@ Retrieves {anomaly-job} results for one or more influencers.
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
 need `read` index privilege on the index that stores the results. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See {stack-ov}/security-privileges.html[Security privileges] and
+privileges. See <<security-privileges>> and
-{stack-ov}/built-in-roles.html[Built-in roles].
+<<built-in-roles>>.
 
 [[ml-get-influencer-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/get-job-stats.asciidoc

@@ -24,7 +24,7 @@ Retrieves usage information for {anomaly-jobs}.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-job-stats-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-job.asciidoc

@@ -24,7 +24,7 @@ Retrieves configuration information for {anomaly-jobs}.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-ml-info.asciidoc

@@ -21,8 +21,8 @@ Returns defaults and limits used by machine learning.
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See {stack-ov}/security-privileges.html[Security privileges] and
+privileges. See <<security-privileges>> and
-{stack-ov}/built-in-roles.html[Built-in roles].
+<<built-in-roles>>.
 
 [[get-ml-info-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-overall-buckets.asciidoc

@@ -25,8 +25,7 @@ Retrieves overall bucket results that summarize the bucket results of multiple
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
 need `read` index privilege on the index that stores the results. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See {stack-ov}/security-privileges.html[Security privileges] and
+privileges. See <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-get-overall-buckets-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/get-record.asciidoc

@@ -20,8 +20,7 @@ Retrieves anomaly records for an {anomaly-job}.
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
 need `read` index privilege on the index that stores the results. The
 `machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See {stack-ov}/security-privileges.html[Security privileges] and
+privileges. See <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-get-record-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/get-snapshot.asciidoc

@@ -20,7 +20,7 @@ Retrieves information about model snapshots.
 
 * If the {es} {security-features} are enabled, you must have `monitor_ml`,
 `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-get-snapshot-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/jobresource.asciidoc

@@ -33,7 +33,7 @@ so do not set the `background_persist_interval` value too low.
 `custom_settings`::
   (object) Advanced configuration option. Contains custom meta data about the
   job. For example, it can contain custom URL information as shown in
-  {xpack-ref}/ml-configuring-url.html[Adding Custom URLs to Machine Learning Results].
+  {stack-ov}/ml-configuring-url.html[Adding Custom URLs to Machine Learning Results].
 
 `data_description`::
   (object) Describes the data format and how APIs parse timestamp fields.
@@ -110,7 +110,7 @@ An analysis configuration object has the following properties:
   be categorized. The resulting categories must be used in a detector by setting
   `by_field_name`, `over_field_name`, or `partition_field_name` to the keyword
   `mlcategory`. For more information, see
-  {xpack-ref}/ml-configuring-categories.html[Categorizing Log Messages].
+  {stack-ov}/ml-configuring-categories.html[Categorizing Log Messages].
 
 `categorization_filters`::
   (array of strings) If `categorization_field_name` is specified,
@@ -120,7 +120,7 @@ An analysis configuration object has the following properties:
   tune the categorization by excluding sequences from consideration when
   categories are defined. For example, you can exclude SQL statements that
   appear in your log files. For more information, see
-  {xpack-ref}/ml-configuring-categories.html[Categorizing Log Messages].
+  {stack-ov}/ml-configuring-categories.html[Categorizing Log Messages].
   This property cannot be used at the same time as `categorization_analyzer`.
   If you only want to define simple regular expression filters that are applied
   prior to tokenization, setting this property is the easiest method.
@@ -243,14 +243,14 @@ NOTE: The `field_name` cannot contain double quotes or backslashes.
 `function`::
   (string) The analysis function that is used. 
   For example, `count`, `rare`, `mean`, `min`, `max`, and `sum`. For more
-  information, see {xpack-ref}/ml-functions.html[Function Reference].
+  information, see {stack-ov}/ml-functions.html[Function Reference].
 
 `over_field_name`::
   (string) The field used to split the data.
   In particular, this property is used for analyzing the splits with respect to
   the history of all splits. It is used for finding unusual values in the
   population of all splits. For more information, see
-  {xpack-ref}/ml-configuring-pop.html[Performing Population Analysis].
+  {stack-ov}/ml-configuring-pop.html[Performing population analysis].
 
 `partition_field_name`::
   (string) The field used to segment the analysis.
@@ -406,7 +406,7 @@ the categorization analyzer produces then you find the original document that
 the categorization field value came from.
 
 For more information, see
-{xpack-ref}/ml-configuring-categories.html[Categorizing Log Messages].
+{stack-ov}/ml-configuring-categories.html[Categorizing log messages].
 
 [float]
 [[ml-detector-custom-rule]]
@@ -489,7 +489,7 @@ The `analysis_limits` object has the following properties:
 --
 NOTE: The `categorization_examples_limit` only applies to analysis that uses categorization.
 For more information, see
-{xpack-ref}/ml-configuring-categories.html[Categorizing Log Messages].
+{stack-ov}/ml-configuring-categories.html[Categorizing log messages].
 
 --
 

docs/reference/ml/anomaly-detection/apis/open-job.asciidoc

@@ -18,7 +18,7 @@ Opens one or more {anomaly-jobs}.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-open-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/post-calendar-event.asciidoc

@@ -18,7 +18,7 @@ Posts scheduled events in a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-post-calendar-event-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/post-data.asciidoc

@@ -18,7 +18,7 @@ Sends data to an anomaly detection job for analysis.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-post-data-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/preview-datafeed.asciidoc

@@ -20,7 +20,7 @@ Previews a {dfeed}.
 
 * If {es} {security-features} are enabled, you must have `monitor_ml`, `monitor`,
 `manage_ml`, or `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-preview-datafeed-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/put-calendar-job.asciidoc

@@ -18,7 +18,7 @@ Adds an {anomaly-job} to a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-put-calendar-job-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/put-calendar.asciidoc

@@ -18,7 +18,7 @@ Instantiates a calendar.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-put-calendar-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/put-datafeed.asciidoc

@@ -21,7 +21,7 @@ Instantiates a {dfeed}.
 * You must create an {anomaly-job} before you create a {dfeed}.  
 * If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
 cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-put-datafeed-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/put-filter.asciidoc

@@ -18,7 +18,7 @@ Instantiates a filter.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-put-filter-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/put-job.asciidoc

@@ -18,7 +18,7 @@ Instantiates an {anomaly-job}.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-put-job-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/resultsresource.asciidoc

@@ -38,7 +38,7 @@ Categorization results contain the definitions of _categories_ that have been
 identified. These are only applicable for jobs that are configured to analyze
 unstructured log data using categorization. These results do not contain a
 timestamp or any calculated scores. For more information, see
-{xpack-ref}/ml-configuring-categories.html[Categorizing Log Messages].
+{stack-ov}/ml-configuring-categories.html[Categorizing log messages].
 
 * <<ml-results-buckets,Buckets>>
 * <<ml-results-influencers,Influencers>>

docs/reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc

@@ -19,7 +19,7 @@ Reverts to a specific snapshot.
 * Before you revert to a saved snapshot, you must close the job.
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-revert-snapshot-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/set-upgrade-mode.asciidoc

@@ -29,7 +29,7 @@ POST /_ml/set_upgrade_mode?enabled=false&timeout=10m
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-set-upgrade-mode-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/start-datafeed.asciidoc

@@ -22,7 +22,7 @@ Starts one or more {dfeeds}.
 error occurs.
 * If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
 cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-start-datafeed-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/stop-datafeed.asciidoc

@@ -24,7 +24,7 @@ Stops one or more {dfeeds}.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-stop-datafeed-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/update-datafeed.asciidoc

@@ -22,7 +22,7 @@ Updates certain properties of a {dfeed}.
 
 * If {es} {security-features} are enabled, you must have `manage_ml`, or `manage`
 cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 
 [[ml-update-datafeed-desc]]

docs/reference/ml/anomaly-detection/apis/update-filter.asciidoc

@@ -18,7 +18,7 @@ Updates the description of a filter, adds items, or removes items.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-update-filter-path-parms]]
 ==== {api-path-parms-title}

docs/reference/ml/anomaly-detection/apis/update-job.asciidoc

@@ -18,7 +18,7 @@ Updates certain properties of an {anomaly-job}.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 
 [[ml-update-job-path-parms]]

docs/reference/ml/anomaly-detection/apis/update-snapshot.asciidoc

@@ -18,7 +18,7 @@ Updates certain properties of a snapshot.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 
 [[ml-update-snapshot-path-parms]]

docs/reference/ml/anomaly-detection/apis/validate-detector.asciidoc

@@ -18,7 +18,7 @@ Validates detector configuration information.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-valid-detector-desc]]
 ==== {api-description-title}

docs/reference/ml/anomaly-detection/apis/validate-job.asciidoc

@@ -18,7 +18,7 @@ Validates {anomaly-job} configuration information.
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[ml-valid-job-desc]]
 ==== {api-description-title}

docs/reference/ml/df-analytics/apis/delete-dfanalytics.asciidoc

@@ -20,8 +20,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `machine_learning_admin` built-in role to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-delete-dfanalytics-path-params]]
 ==== {api-path-parms-title}

docs/reference/ml/df-analytics/apis/estimate-memory-usage-dfanalytics.asciidoc

@@ -21,8 +21,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `monitor_ml` privilege to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-estimate-memory-usage-dfanalytics-desc]]
 ==== {api-description-title}

docs/reference/ml/df-analytics/apis/evaluate-dfanalytics.asciidoc

@@ -21,8 +21,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `monitor_ml` privilege to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-evaluate-dfanalytics-desc]]
 ==== {api-description-title}

docs/reference/ml/df-analytics/apis/get-dfanalytics-stats.asciidoc

@@ -29,8 +29,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `monitor_ml` privilege to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 
 [[ml-get-dfanalytics-stats-path-params]]

docs/reference/ml/df-analytics/apis/get-dfanalytics.asciidoc

@@ -26,8 +26,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `monitor_ml` privilege to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-get-dfanalytics-desc]]
 ==== {api-description-title}

docs/reference/ml/df-analytics/apis/put-dfanalytics.asciidoc

@@ -23,8 +23,7 @@ experimental[]
 * You must have `machine_learning_admin` built-in role to use this API. You must 
 also have `read` and `view_index_metadata` privileges on the source index and 
 `read`, `create_index`, and `index` privileges on the destination index. For 
-more information, see {stack-ov}/security-privileges.html[Security privileges] 
+more information, see <<security-privileges>> and <<built-in-roles>>.
-and {stack-ov}/built-in-roles.html[Built-in roles].
 
 
 [[ml-put-dfanalytics-desc]]

docs/reference/ml/df-analytics/apis/start-dfanalytics.asciidoc

@@ -23,8 +23,7 @@ experimental[]
 * You must have `machine_learning_admin` built-in role to use this API. You must 
 also have `read` and `view_index_metadata` privileges on the source index and 
 `read`, `create_index`, and `index` privileges on the destination index. For 
-more information, see {stack-ov}/security-privileges.html[Security privileges] 
+more information, see <<security-privileges>> and <<built-in-roles>>.
-and {stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-start-dfanalytics-path-params]]
 ==== {api-path-parms-title}

docs/reference/ml/df-analytics/apis/stop-dfanalytics.asciidoc

@@ -25,8 +25,7 @@ experimental[]
 ==== {api-prereq-title}
 
 * You must have `machine_learning_admin` built-in role to use this API. For more 
-information, see {stack-ov}/security-privileges.html[Security privileges] and 
+information, see <<security-privileges>> and <<built-in-roles>>.
-{stack-ov}/built-in-roles.html[Built-in roles].
 
 [[ml-stop-dfanalytics-desc]]
 ==== {api-description-title}

docs/reference/modules/remote-clusters.asciidoc

@@ -9,7 +9,7 @@ endif::[]
 ifdef::include-xpack[]
 The _remote clusters_ module enables you to establish uni-directional
 connections to a remote cluster. This functionality is used in
-{stack-ov}/xpack-ccr.html[{ccr}] and
+<<xpack-ccr,{ccr}>> and
 <<modules-cross-cluster-search,{ccs}>>.
 endif::[]
 

docs/reference/monitoring/collecting-monitoring-data.asciidoc

@@ -18,8 +18,7 @@ Advanced monitoring settings enable you to control how frequently data is
 collected, configure timeouts, and set the retention period for locally-stored 
 monitoring indices. You can also adjust how monitoring data is displayed. 
 
-To learn about monitoring in general, see 
+To learn about monitoring in general, see <<monitor-elasticsearch-cluster>>. 
-{stack-ov}/xpack-monitoring.html[Monitoring the {stack}]. 
 
 . Configure your cluster to collect monitoring data:
 
@@ -131,9 +130,9 @@ xpack.monitoring.exporters:
 must provide appropriate credentials when data is shipped to the monitoring cluster:
 
 ... Create a user on the monitoring cluster that has the 
-{stack-ov}/built-in-roles.html[`remote_monitoring_agent` built-in role]. 
+<<built-in-roles,`remote_monitoring_agent` built-in role>>. 
 Alternatively, use the 
-{stack-ov}/built-in-users.html[`remote_monitoring_user` built-in user].
+<<built-in-users,`remote_monitoring_user` built-in user>>.
 
 ... Add the user ID and password settings to the HTTP exporter settings in the 
 `elasticsearch.yml` file on each node. +
@@ -197,8 +196,7 @@ xpack.monitoring.exporters:
 
 . Configure your cluster to route monitoring data from sources such as {kib}, 
 Beats, and {ls} to the monitoring cluster. For information about configuring
-each product to collect and send monitoring data, see
+each product to collect and send monitoring data, see <<monitor-elasticsearch-cluster>>.
-{stack-ov}/xpack-monitoring.html[Monitoring the {stack}].
 
 . If you updated settings in the `elasticsearch.yml` files on your production 
 cluster, restart {es}. See <<stopping-elasticsearch>> and <<starting-elasticsearch>>. 

docs/reference/monitoring/configuring-filebeat.asciidoc

@@ -39,12 +39,12 @@ For more information, see <<monitoring-settings>> and <<cluster-update-settings>
 +
 --
 The {filebeat} {es} module can handle
-{stack-ov}/audit-log-output.html[audit logs],
+<<audit-log-output,audit logs>>,
-{ref}/logging.html#deprecation-logging[deprecation logs],
+<<deprecation-logging,deprecation logs>>,
-{ref}/gc-logging.html[gc logs], {ref}/logging.html[server logs], and 
+<<gc-logging,gc logs>>, <<logging,server logs>>, and 
-{ref}/index-modules-slowlog.html[slow logs].
+<<index-modules-slowlog,slow logs>>.
 For more information about the location of your {es} logs, see the
-{ref}/path-settings.html[path.logs] setting.
+<<path-settings,path.logs>> setting.
 
 IMPORTANT: If there are both structured (`*.json`) and unstructured (plain text)
 versions of the logs, you must use the structured logs. Otherwise, they might
@@ -117,7 +117,7 @@ If {security-features} are enabled, you must provide a valid user ID and
 password so that {filebeat} can connect to {kib}: 
 
 .. Create a user on the monitoring cluster that has the 
-{stack-ov}/built-in-roles.html[`kibana_user` built-in role] or equivalent
+<<built-in-roles,`kibana_user` built-in role>> or equivalent
 privileges.
 
 .. Add the `username` and `password` settings to the {es} output information in 
@@ -175,7 +175,7 @@ to file ownership or permissions when you try to run {filebeat} modules. See
 . Check whether the appropriate indices exist on the monitoring cluster.
 +
 --
-For example, use the {ref}/cat-indices.html[cat indices] command to verify
+For example, use the <<cat-indices,cat indices>> command to verify
 that there are new `filebeat-*` indices. 
 
 TIP: If you want to use the *Monitoring* UI in {kib}, there must also be 

docs/reference/monitoring/configuring-metricbeat.asciidoc

@@ -14,9 +14,6 @@ as described in <<collecting-monitoring-data>>.
 
 image::monitoring/images/metricbeat.png[Example monitoring architecture]
 
-To learn about monitoring in general, see 
-{stack-ov}/xpack-monitoring.html[Monitoring the {stack}]. 
-
 //NOTE: The tagged regions are re-used in the Stack Overview.
 
 . Enable the collection of monitoring data. +
@@ -106,9 +103,9 @@ If Elastic {security-features} are enabled, you must also provide a user ID
 and password so that {metricbeat} can collect metrics successfully: 
 
 .. Create a user on the production cluster that has the
-{stack-ov}/built-in-roles.html[`remote_monitoring_collector` built-in role]. 
+<<built-in-roles,`remote_monitoring_collector` built-in role>>. 
 Alternatively, use the
-{stack-ov}/built-in-users.html[`remote_monitoring_user` built-in user].
+<<built-in-users,`remote_monitoring_user` built-in user>>.
 
 .. Add the `username` and `password` settings to the {es} module configuration
 file. 
@@ -171,9 +168,9 @@ provide a valid user ID and password so that {metricbeat} can send metrics
 successfully: 
 
 .. Create a user on the monitoring cluster that has the 
-{stack-ov}/built-in-roles.html[`remote_monitoring_agent` built-in role]. 
+<<built-in-roles,`remote_monitoring_agent` built-in role>>. 
 Alternatively, use the 
-{stack-ov}/built-in-users.html[`remote_monitoring_user` built-in user].
+<<built-in-users,`remote_monitoring_user` built-in user>>.
 
 .. Add the `username` and `password` settings to the {es} output information in 
 the {metricbeat} configuration file.

docs/reference/monitoring/production.asciidoc

@@ -60,12 +60,12 @@ credentials must be valid on both the {kib} server and the monitoring cluster.
 *** If you plan to use {metricbeat} to collect data about {es} or {kib}, 
 create a user that has the `remote_monitoring_collector` built-in role and a 
 user that has the `remote_monitoring_agent` 
-{stack-ov}/built-in-roles.html#built-in-roles-remote-monitoring-agent[built-in role]. Alternatively, use the 
+<<built-in-roles-remote-monitoring-agent,built-in role>>. Alternatively, use the 
-`remote_monitoring_user` {stack-ov}/built-in-users.html[built-in user]. 
+`remote_monitoring_user` <<built-in-users,built-in user>>. 
 
 *** If you plan to use HTTP exporters to route data through your production 
 cluster, create a user that has the `remote_monitoring_agent` 
-{stack-ov}/built-in-roles.html#built-in-roles-remote-monitoring-agent[built-in role]. 
+<<built-in-roles-remote-monitoring-agent,built-in role>>. 
 +
 --
 For example, the 
@@ -83,7 +83,7 @@ POST /_security/user/remote_monitor
 ---------------------------------------------------------------
 // TEST[skip:needs-gold+-license]
 
-Alternatively, use the `remote_monitoring_user` {stack-ov}/built-in-users.html[built-in user]. 
+Alternatively, use the `remote_monitoring_user` <<built-in-users,built-in user>>. 
 --
 
 . Configure your production cluster to collect data and send it to the 

docs/reference/rollup/apis/delete-job.asciidoc

@@ -21,7 +21,7 @@ experimental[]
 
 * If the {es} {security-features} are enabled, you must have `manage` or
 `manage_rollup` cluster privileges to use this API. For more information, see
-{stack-ov}/security-privileges.html[Security privileges].
+<<security-privileges>>.
 
 [[rollup-delete-job-desc]]
 ==== {api-description-title}