Update data-streams.asciidoc

docs/en/observability/apm/data-streams.asciidoc

@@ -90,7 +90,7 @@ Logs are stored in the following data streams:
 === APM data stream rerouting
 
 APM supports rerouting APM data to user-defined APM data stream names other than the defaults.
-This can be achieved by using a `reroute` processor in ingest pipelines to set the data stream dataset or namespace.
+This can be achieved by using a {ref}/reroute-processor.html[`reroute` processor] in ingest pipelines to set the data stream dataset or namespace.
 The benefit of separating APM data streams is that custom retention and security policies can be used.
 
 For example, consider traces that would originally be indexed to `traces-apm-default`. To set the data stream namespace from the trace's `service.environment` and fallback to a static string `"default"`, create an ingest pipeline named `traces-apm@custom` which will be used automatically:
@@ -109,9 +109,9 @@ For example, consider traces that would originally be indexed to `traces-apm-def
 ]
 ----
 
-For more about the reroute processor, see {ref}/reroute-processor.html[Reroute processor reference].
+For more about other ingest pipelines called by default, e.g. `traces-apm@custom`, see {fleet-guide}/data-streams.html#data-streams-pipelines[integration data streams ingest pipelines].
 
-For more information about custom ingest pipelines, see <<apm-ingest-pipelines,parse data using ingest pipelines>>.
+For more custom APM ingest pipeline guides, see <<apm-ingest-pipelines,parse data using ingest pipelines>>.
 
 [discrete]
 [[apm-data-streams-next]]