[DOCS] Update ingest pipeline xrefs (#70178)

docs/reference/ingest/enrich.asciidoc

@@ -107,8 +107,8 @@ and <<update-enrich-policies, update your enrich policies>>.
 
 [IMPORTANT]
 ====
-The enrich processor performs several operations
-and may impact the speed of your <<pipeline,ingest pipeline>>.
+The enrich processor performs several operations and may impact the speed of
+your ingest pipeline.
 
 We strongly recommend testing and benchmarking your enrich processors
 before deploying them in production.

docs/reference/migration/migrate_8_0/migrate_to_java_time.asciidoc

@@ -23,7 +23,7 @@ These formats are commonly used in:
 
 * <<mapping,Index mappings>>
 * <<index-templates,Index templates>>
-* <<pipeline,Ingest pipelines>>
+* <<ingest,Ingest pipelines>>
 
 If you don't use custom date formats, you can skip the rest of this guide.
 Most custom date formats are compatible. However, several require

docs/reference/modules/node.asciidoc

@@ -63,7 +63,7 @@ related operations such as CRUD, search, and aggregations. A node with the `data
 <<node-ingest-node,Ingest node>>::
 
 A node that has the `ingest` role. Ingest nodes are able to apply an
-<<pipeline,ingest pipeline>> to a document in order to transform and enrich the
+<<ingest,ingest pipeline>> to a document in order to transform and enrich the
 document before indexing. With a heavy ingest load, it makes sense to use
 dedicated ingest nodes and to not include the `ingest` role from nodes that have
 the `master` or `data` roles.

docs/reference/rest-api/common-parms.asciidoc

@@ -165,7 +165,7 @@ prior to starting the {transform}.
 end::dest-index[]
 
 tag::dest-pipeline[]
-The unique identifier for a <<pipeline,pipeline>>.
+The unique identifier for an <<ingest,ingest pipeline>>.
 end::dest-pipeline[]
 
 tag::detailed[]