Add LINQ to ESQL documentation

Author: flobernd

docs/reference/esql.md

@@ -6,14 +6,13 @@ mapped_pages:
 
 # ES|QL in the .NET client [esql]
 
-
 This page helps you understand and use [ES|QL](docs-content://explore-analyze/query-filter/languages/esql.md) in the .NET client.
 
-There are two ways to use ES|QL in the .NET client:
+The recommended way to work with ES|QL is the [LINQ to ES|QL](linq-to-esql.md) provider, which lets you write type-safe C# LINQ queries that are automatically translated to ES|QL at runtime.
 
-* Use the Elasticsearch [ES|QL API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-esql) directly: This is the most flexible approach, but it’s also the most complex because you must handle results in their raw form. You can choose the precise format of results, such as JSON, CSV, or text.
-* Use ES|QL high-level helpers: These helpers take care of parsing the raw response into something readily usable by the application. Several helpers are available for different use cases, such as object mapping, cursor traversal of results (in development), and dataframes (in development).
+For lower-level control, you can also use the Elasticsearch [ES|QL API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-esql) directly: This is the most flexible approach, but it's also the most complex because you must handle results in their raw form.
 
+You can choose the precise format of results, such as JSON, CSV, or text.
 
 ## How to use the ES|QL API [esql-how-to]
 
@@ -23,28 +22,15 @@ The following example gets ES|QL results as CSV and parses them:
 
 ```csharp
 var response = await client.Esql.QueryAsync(r => r
-	.Query("FROM index")
-	.Format("csv")
+    .Query("FROM index")
+    .Format("csv")
 );
+
 var csvContents = Encoding.UTF8.GetString(response.Data);
 ```
 
-
 ## Consume ES|QL results [esql-consume-results]
 
 The previous example showed that although the raw ES|QL API offers maximum flexibility, additional work is required in order to make use of the result data.
 
-To simplify things, try working with these three main representations of ES|QL results (each with its own mapping helper):
-
-* **Objects**, where each row in the results is mapped to an object from your application domain. This is similar to what ORMs (object relational mappers) commonly do.
-* **Cursors**, where you scan the results row by row and access the data using column names. This is similar to database access libraries.
-* **Dataframes**, where results are organized in a column-oriented structure that allows efficient processing of column data.
-
-```csharp
-// ObjectAPI example
-var response = await client.Esql.QueryAsObjectsAsync<Person>(x => x.Query("FROM index"));
-foreach (var person in response)
-{
-    // ...
-}
-```
+The recommended approach is [LINQ to ES|QL](linq-to-esql.md), which provides type-safe queries with automatic result mapping. See the [LINQ to ES|QL](linq-to-esql.md) documentation for details.