Fix docs: links to cross_link://docs/reference/ should go to cross_li…

…nk://reference/ (#2558)

docs/reference/log-correlation-manual.md

@@ -49,7 +49,7 @@ This would print a log message along the lines of:
     ERROR [trace.id=cd04f33b9c0c35ae8abe77e799f126b7 transaction.id=cd04f33b9c0c35ae] an error occurred
 ```
 
-For log correlation to work, the trace ids must be extracted from the log message and stored in separate fields in the Elasticsearch document. This can be achieved by [parsing the data by using ingest node](beats://docs/reference/filebeat/configuring-ingest-node.md), in particular by using [the grok processor](elasticsearch://docs/reference/ingestion-tools/enrich-processor/grok-processor.md).
+For log correlation to work, the trace ids must be extracted from the log message and stored in separate fields in the Elasticsearch document. This can be achieved by [parsing the data by using ingest node](beats://reference/filebeat/configuring-ingest-node.md), in particular by using [the grok processor](elasticsearch://reference/ingestion-tools/enrich-processor/grok-processor.md).
 
 ```json
 {

docs/reference/logs.md

@@ -9,7 +9,7 @@ Elastic .NET Agent provides [Log correlation](#log-correlation-ids). The agent w
 
 This features is part of [Application log ingestion strategies](docs-content://solutions/observability/logs/stream-application-logs.md).
 
-The [`ecs-logging-dotnet`](ecs-dotnet://docs/reference/index.md) library can also be used to use the [ECS logging](ecs-logging://docs/reference/intro.md) format without an APM agent. ECS .NET logging will always provide [log correlation](#log-correlation-ids) IDs through [`System.Diagnostics.Activity`](https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.activity?view=net-7.0). When paired with the APM Agent it will pick up the appropriate service correlation features too.
+The [`ecs-logging-dotnet`](ecs-dotnet://reference/index.md) library can also be used to use the [ECS logging](ecs-logging://reference/intro.md) format without an APM agent. ECS .NET logging will always provide [log correlation](#log-correlation-ids) IDs through [`System.Diagnostics.Activity`](https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.activity?view=net-7.0). When paired with the APM Agent it will pick up the appropriate service correlation features too.
 
 
 ## Log correlation [log-correlation-ids]
@@ -24,7 +24,7 @@ If your favorite logging framework is not already supported, there are two other
 * Open a feature request, or contribute code, for additional support, as described in [CONTRIBUTING.md](https://github.com/elastic/apm-agent-dotnet/blob/main/CONTRIBUTING.md).
 * Manually inject trace IDs into log records, as described in [Manual log correlation](/reference/log-correlation-manual.md).
 
-Regardless of how you integrate APM with logging, you can use [Filebeat](beats://docs/reference/filebeat/filebeat-overview.md) to send your logs to Elasticsearch, in order to correlate your traces and logs and link from APM to the [Logs app](docs-content://solutions/observability/logs/explore-logs.md).
+Regardless of how you integrate APM with logging, you can use [Filebeat](beats://reference/filebeat/filebeat-overview.md) to send your logs to Elasticsearch, in order to correlate your traces and logs and link from APM to the [Logs app](docs-content://solutions/observability/logs/explore-logs.md).
 
 
 

docs/reference/metrics.md

@@ -35,7 +35,7 @@ For applications running in IIS, [IIS application pool identities use *virtual*
 ::::
 
 
-For more system metrics, consider installing [metricbeat](beats://docs/reference/metricbeat/metricbeat.md) on your hosts.
+For more system metrics, consider installing [metricbeat](beats://reference/metricbeat/metricbeat.md) on your hosts.
 
 **`system.cpu.total.norm.pct`**
 :   type: scaled_float

docs/reference/public-api.md

@@ -316,7 +316,7 @@ finally
 Labels are used to add **indexed** information to transactions, spans, and errors. Indexed means the data is searchable and aggregatable in Elasticsearch. Multiple labels can be defined with different key-value pairs.
 
 * Indexed: Yes
-* Elasticsearch type: [object](elasticsearch://docs/reference/elasticsearch/mapping-reference/object.md)
+* Elasticsearch type: [object](elasticsearch://reference/elasticsearch/mapping-reference/object.md)
 * Elasticsearch field: `labels` (previously `context.tags` in <v.7.0)
 
 Label values can be a string, boolean, or number. Because labels for a given key are stored in the same place in Elasticsearch, all label values of a given key must have the same data type. Multiple data types per key will throw an exception, e.g., `{"foo": "bar"}` and `{"foo": 42}`.
@@ -511,7 +511,7 @@ To enable the JavaScript RUM agent in ASP.NET Core, initialize the RUM agent wit
 </script>
 ```
 
-See the  [JavaScript RUM agent documentation](apm-agent-rum-js://docs/reference/index.md) for more information.
+See the  [JavaScript RUM agent documentation](apm-agent-rum-js://reference/index.md) for more information.
 
 
 #### `Dictionary<string,string> Custom` [api-transaction-custom]