From 2e5a4b5b7bc521fbf880380ccd3dbb500ec30c7c Mon Sep 17 00:00:00 2001 From: Carson Ip Date: Thu, 12 Sep 2024 14:36:38 +0100 Subject: [PATCH] Fix typo in reroute (#4240) --- docs/en/observability/apm/ingest-pipelines.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/observability/apm/ingest-pipelines.asciidoc b/docs/en/observability/apm/ingest-pipelines.asciidoc index 95aa785890..c1c80ccff9 100644 --- a/docs/en/observability/apm/ingest-pipelines.asciidoc +++ b/docs/en/observability/apm/ingest-pipelines.asciidoc @@ -64,7 +64,7 @@ The process for creating a custom ingest pipeline is as follows: If you prefer more guidance, see one of these tutorials: * <> — Learn how to obfuscate passwords stored in the `http.request.body.original` field. -* <> — Learn how rerouting APM data to user-defined APM data streams. +* <> — Learn how to reroute APM data to user-defined APM data streams. * {fleet-guide}/data-streams-pipeline-tutorial.html[Transform data with custom ingest pipelines] — A basic Elastic integration tutorial where you learn how to add a custom field to incoming data. // end::ingest-pipelines[] \ No newline at end of file