update links (#2463)

Co-authored-by: Michael Wolf <[email protected]>

Author: colleenmcginnis

docs/docset.yml

@@ -5,7 +5,7 @@ cross_links:
   - beats
   - docs-content
   - elasticsearch
-  - logstash
+  - logstash-docs-md
 toc:
   - toc: reference
 subs:

docs/reference/ecs-conventions.md

@@ -28,7 +28,7 @@ Some specific kinds of codes are always integers, like HTTP status codes. If tho
 Elasticsearch can index text using datatypes:
 
 * **`text`** Text indexing allows for full text search, or searching arbitrary words that are part of the field. See [Text datatype](elasticsearch://reference/elasticsearch/mapping-reference/text.md) in the {{es}} Reference Guide.
-* **`keyword`** Keyword indexing offers faster exact match filtering, prefix search (like autocomplete), and makes aggregations (like {{kib}} visualizations) possible. See the {{es}} Reference Guide for more information on [exact match filtering](elasticsearch://reference/query-languages/query-dsl/query-dsl-term-query.md), [prefix search](elasticsearch://reference/query-languages/query-dsl/query-dsl-prefix-query.md), or [aggregations](elasticsearch://reference/data-analysis/aggregations/index.md).
+* **`keyword`** Keyword indexing offers faster exact match filtering, prefix search (like autocomplete), and makes aggregations (like {{kib}} visualizations) possible. See the {{es}} Reference Guide for more information on [exact match filtering](elasticsearch://reference/query-languages/query-dsl/query-dsl-term-query.md), [prefix search](elasticsearch://reference/query-languages/query-dsl/query-dsl-prefix-query.md), or [aggregations](elasticsearch://reference/aggregations/index.md).
 
 
 ## Default Elasticsearch convention for indexing text fields [_default_elasticsearch_convention_for_indexing_text_fields]

docs/reference/ecs-faq.md

@@ -27,7 +27,7 @@ The benefits to a user adopting these fields and names in their clusters are:
 
 ## What if I have fields that conflict with ECS? [conflict]
 
-The [rename processor](elasticsearch://reference/ingestion-tools/enrich-processor/rename-processor.md) can help you resolve field conflicts. For example, imagine that you already have a field called "user," but ECS employs `user` as an object. You can use the rename processor on ingest time to rename your field to the matching ECS field. If your field does not match ECS, you can rename your field to `user.value` instead.
+The [rename processor](elasticsearch://reference/enrich-processor/rename-processor.md) can help you resolve field conflicts. For example, imagine that you already have a field called "user," but ECS employs `user` as an object. You can use the rename processor on ingest time to rename your field to the matching ECS field. If your field does not match ECS, you can rename your field to `user.value` instead.
 
 
 ## What if my events have additional fields? [addl-fields]

docs/reference/ecs-products-solutions.md

@@ -20,5 +20,5 @@ The following Elastic products support ECS out of the box, as of version 7.0:
 * [Log Monitoring](docs-content://solutions/observability/logs/explore-logs.md)
 * Log formatters that support ECS out of the box for various languages can be found [here](https://github.com/elastic/ecs-logging/blob/master/README.md).
 * [Metrics Monitoring](docs-content://solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md)
-* {{ls}}' {{es}} output has an [ECS compatibility mode](logstash://reference/plugins-outputs-elasticsearch.md#_compatibility_with_the_elastic_common_schema_ecs)
+* {{ls}}' {{es}} output has an [ECS compatibility mode](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md#_compatibility_with_the_elastic_common_schema_ecs)