[8.10] [DOCS] Change deep link to ES book for CCS privileges (#164165) (

#164395)

# Backport

This will backport the following commits from `main` to `8.10`:
- [[DOCS] Change deep link to ES book for CCS privileges
(#164165)](#164165)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Abdon
Pijpelink","email":"abdon.pijpelink@elastic.co"},"sourceCommit":{"committedDate":"2023-08-22T07:33:53Z","message":"[DOCS]
Change deep link to ES book for CCS privileges (#164165)\n\n##
Summary\r\n\r\nRelates to
elastic/elasticsearch#98330
introduces a new method to configure remote clusters (API key\r\nbased),
which will live next to the existing method (certificate based).\r\nAs a
result, the ES remote cluster docs will be restructured. The
deep\r\nlink from \"[Alerting
set\r\nup](https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-ccs-setup)\"\r\nto
the setting up CCS privileges section in the ES docs will break
(and\r\nwould potentially bring folks to the wrong page
anyway).\r\n\r\nThis PR changes the link into a link to the higher-level
remote cluster\r\ndocs, from where folks can click through to the
section that is relevant\r\nto
them.","sha":"4b1d833aee778e0e7278edc04260394b0c024de5","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.10.0","v8.11.0"],"number":164165,"url":"#164165
Change deep link to ES book for CCS privileges (#164165)\n\n##
Summary\r\n\r\nRelates to
elastic/elasticsearch#98330
introduces a new method to configure remote clusters (API key\r\nbased),
which will live next to the existing method (certificate based).\r\nAs a
result, the ES remote cluster docs will be restructured. The
deep\r\nlink from \"[Alerting
set\r\nup](https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-ccs-setup)\"\r\nto
the setting up CCS privileges section in the ES docs will break
(and\r\nwould potentially bring folks to the wrong page
anyway).\r\n\r\nThis PR changes the link into a link to the higher-level
remote cluster\r\ndocs, from where folks can click through to the
section that is relevant\r\nto
them.","sha":"4b1d833aee778e0e7278edc04260394b0c024de5"}},"sourceBranch":"main","suggestedTargetBranches":["8.10"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"#164165
Change deep link to ES book for CCS privileges (#164165)\n\n##
Summary\r\n\r\nRelates to
elastic/elasticsearch#98330
introduces a new method to configure remote clusters (API key\r\nbased),
which will live next to the existing method (certificate based).\r\nAs a
result, the ES remote cluster docs will be restructured. The
deep\r\nlink from \"[Alerting
set\r\nup](https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-ccs-setup)\"\r\nto
the setting up CCS privileges section in the ES docs will break
(and\r\nwould potentially bring folks to the wrong page
anyway).\r\n\r\nThis PR changes the link into a link to the higher-level
remote cluster\r\ndocs, from where folks can click through to the
section that is relevant\r\nto
them.","sha":"4b1d833aee778e0e7278edc04260394b0c024de5"}}]}] BACKPORT-->

Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>

docs/user/alerting/alerting-setup.asciidoc

@@ -109,5 +109,5 @@ The same behavior occurs when you change the API key in the header of your API c
 [[alerting-ccs-setup]]
 === {ccs-cap}
 
-If you want to use alerting rules with {ccs}, you must configure 
-{ref}/remote-clusters-privileges.html#clusters-privileges-ccs-kibana[privileges for {ccs-init} and {kib}].
+If you want to use alerting rules with {ccs}, you must configure privileges for
+{ccs-init} and {kib}. Refer to {ref}/remote-clusters.html[Remote clusters].