Apply suggestions from code review

docs/reference/data-streams/lifecycle/index.asciidoc

@@ -2,7 +2,7 @@
 [[data-stream-lifecycle]]
 == Data stream lifecycle
 
-A data stream lifecycle is the built-in mechanism <<data-streams,data streams>> use to manage their <<index-lifecycle-management,lifecycle>>. It enables you to easily
+A data stream lifecycle is the built-in mechanism data streams use to manage their lifecycle. It enables you to easily
 automate the management of your data streams according to your retention requirements. For example, you could configure
 the lifecycle to:
 

docs/reference/data-streams/lifecycle/tutorial-manage-existing-data-stream.asciidoc

@@ -2,7 +2,7 @@
 [[tutorial-manage-existing-data-stream]]
 === Tutorial: Update existing data stream
 
-To update the <<data-stream-lifecycle,lifecycle>> of an existing <<data-streams,data stream>> you do the following actions:
+To update the lifecycle of an existing data stream you do the following actions:
 
 . <<set-lifecycle>>
 . <<delete-lifecycle>>

docs/reference/data-streams/lifecycle/tutorial-manage-new-data-stream.asciidoc

@@ -2,7 +2,7 @@
 [[tutorial-manage-new-data-stream]]
 === Tutorial: Create a data stream with a lifecycle
 
-To create a <<data-streams,data stream>> with a built-in <<data-stream-lifecycle,lifecycle>>, follow these steps:
+To create a data stream with a built-in lifecycle, follow these steps:
 
 . <<create-index-template-with-lifecycle>>
 . <<create-data-stream-with-lifecycle>>

docs/reference/data-streams/lifecycle/tutorial-migrate-data-stream-from-ilm-to-dsl.asciidoc

@@ -2,8 +2,8 @@
 [[tutorial-migrate-data-stream-from-ilm-to-dsl]]
 === Tutorial: Migrate ILM managed data stream to data stream lifecycle 
 
-In this tutorial we'll look at migrating an existing <<data-streams,data stream>> from <<index-lifecycle-management,Index Lifecycle Management ({ilm-init})>> to
-<<data-stream-lifecycle,data stream lifecycle>>. The existing {ilm-init} managed backing indices will continue 
+In this tutorial we'll look at migrating an existing data strea from <<index-lifecycle-management,Index Lifecycle Management ({ilm-init})>> to
+data stream lifecycle. The existing {ilm-init} managed backing indices will continue 
 to be managed by {ilm-init} until they age out and get deleted by {ilm-init}; however,
 the new backing indices will be managed by data stream lifecycle. 
 This way, a data stream is gradually migrated away from being managed by {ilm-init} to 

docs/reference/data-streams/promote-data-stream-api.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Promote data stream</titleabbrev>
 ++++
 
-The purpose of the promote <<data-streams,data stream>> api is to turn
+The purpose of the promote <<data-streams,data stream>> API is to turn
 a data stream that is replicated by CCR into a regular
 data stream.
 

docs/reference/data-streams/set-up-a-data-stream.asciidoc

@@ -2,7 +2,7 @@
 [[set-up-a-data-stream]]
 == Set up a data stream
 
-To set up a <<data-streams,data stream>>, follow these steps:
+To set up a data stream, follow these steps:
 
 . <<create-index-lifecycle-policy>>
 . <<create-component-templates>>

docs/reference/data-streams/tsds-reindex.asciidoc

@@ -9,7 +9,7 @@
 [[tsds-reindex-intro]]
 ==== Introduction
 
-With reindexing, you can copy documents from an old <<tsds,time-series data stream (TSDS)>> to a new one. <<data-streams,Data streams>> support
+With reindexing, you can copy documents from an old <<tsds,time-series data stream (TSDS)>> to a new one. Data streams support
 reindexing in general, with a few <<reindex-with-a-data-stream, restrictions>>. Still, time-series data streams
 introduce additional challenges due to tight control on the accepted timestamp range for each backing index they
 contain. Direct use of the reindex API would likely error out due to attempting to insert documents with timestamps that are

docs/reference/eql/detect-threats-with-eql.asciidoc

@@ -2,7 +2,7 @@
 [[eql-ex-threat-detection]]
 == Example: Detect threats with EQL
 
-This example tutorial shows how you can use <<eql,(EQL)>> to detect security threats and
+This example tutorial shows how you can use EQL to detect security threats and
 other suspicious behavior. In the scenario, you're tasked with detecting
 https://attack.mitre.org/techniques/T1218/010/[regsvr32 misuse] in Windows event
 logs.

docs/reference/esql/esql-across-clusters.asciidoc

@@ -13,7 +13,7 @@ preview::["{ccs-cap} for {esql} is in technical preview and may be changed or re
 For {ccs-cap} with {esql} on version 8.16 or later, remote clusters must also be on version 8.16 or later.
 ====
 
-With <<esql,{esql}>>, you can execute a single query across multiple clusters.
+With {esql}, you can execute a single query across multiple clusters.
 
 [discrete]
 [[esql-ccs-prerequisites]]

docs/reference/esql/esql-commands.asciidoc

@@ -9,7 +9,7 @@
 // tag::source_commands[]
 ==== Source commands
 
-An <<esql,{esql}>> source command produces a table, typically with data from {es}. An {esql} query must start with a source command.
+An {esql} source command produces a table, typically with data from {es}. An {esql} query must start with a source command.
 
 image::images/esql/source-command.svg[A source command producing a table from {es},align="center"]
 

docs/reference/esql/esql-enrich-data.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Data enrichment</titleabbrev>
 ++++
 
-The <<esql,{esql}>> <<esql-enrich>> processing command combines, at query-time, data from
+The {esql} <<esql-enrich>> processing command combines, at query-time, data from
 one or more source indexes with field-value combinations found in {es} enrich
 indexes.
 

docs/reference/esql/esql-functions-operators.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Functions and operators</titleabbrev>
 ++++
 
-<<esql,{esql}>> provides a comprehensive set of functions and operators for working with data.
+{esql} provides a comprehensive set of functions and operators for working with data.
 The reference documentation is divided into the following categories:
 
 [[esql-functions]]

docs/reference/esql/esql-get-started.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>Getting started</titleabbrev>
 ++++
 
-This guide shows how you can use <<esql,{esql}>> to query and aggregate your data.
+This guide shows how you can use {esql} to query and aggregate your data.
 
 [TIP]
 ====

docs/reference/esql/esql-kibana.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Using {esql} in {kib}</titleabbrev>
 ++++
 
-You can use <<esql,{esql}>> in {kib} to query and aggregate your data, create
+You can use {esql} in {kib} to query and aggregate your data, create
 visualizations, and set up alerts.
 
 This guide shows you how to use {esql} in Kibana. To follow along with the

docs/reference/esql/esql-language.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>{esql} reference</titleabbrev>
 ++++
 
-Detailed reference documentation for the <<esql,{esql}>> language:
+Detailed reference documentation for the {esql} language:
 
 * <<esql-syntax>>
 * <<esql-commands>>

docs/reference/esql/esql-limitations.asciidoc

@@ -9,7 +9,7 @@
 [[esql-max-rows]]
 === Result set size limit
 
-By default, an <<esql,{esql}>> query returns up to 1000 rows. You can increase the number
+By default, an {esql} query returns up to 1000 rows. You can increase the number
 of rows up to 10,000 using the <<esql-limit>> command.
 include::processing-commands/limit.asciidoc[tag=limitation]