This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit d9843654a8a41a86706985ada55ee20d287c5db0
Author: Otavio R. Piske <angusyo...@gmail.com>
AuthorDate: Sun Feb 25 15:04:06 2024 +0100
CAMEL-20459: minor documentation tweaks for the pipeline EIP.
Signed-off-by: Otavio R. Piske <angusyo...@gmail.com>
---
.../src/main/docs/modules/eips/pages/pipeline-eip.adoc | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/pipeline-eip.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/pipeline-eip.adoc
index 2f3e078006d..30b0edcdb1f 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/pipeline-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/pipeline-eip.adoc
@@ -12,7 +12,7 @@ from the xref:enterprise-integration-patterns.adoc[EIP
patterns] in various ways
image::eip/PipesAndFilters.gif[image]
With Camel, you can separate your processing across multiple independent
-xref:manual::endpoint.adoc[Endpoint]'s which can then be chained
+xref:manual::endpoint.adoc[Endpoints] which can then be chained
together.
== Options
@@ -61,7 +61,7 @@ XML::
----
====
-Though pipeline is the default mode of operation when you specify
+Though a pipeline is the default mode of operation when you specify
multiple outputs in Camel. Therefore, it's much more common to see this with
Camel:
[tabs]
@@ -93,16 +93,18 @@ XML::
The opposite to `pipeline` is xref:multicast-eip.adoc[`multicast`].
A xref:multicast-eip.adoc[Multicast] EIP routes a copy of the same message
into each of its outputs,
-where these messages are processed independently. Pipeline EIP however, will
route the same message
-sequentially in the pipeline where the output from the previous step is input
to the next. The same principle
+where these messages are processed independently.
+Pipeline EIP, however, will route the same message
+sequentially in the pipeline where the output from the previous step is input
to the next.
+The same principle
from the Linux shell with chaining commands together with pipe (`|`).
-=== When using pipeline is necessary
+=== When using a pipeline is necessary
-Using pipeline becomes necessary when you need to group together a series of
steps into a single logical step.
-For example in the example below where xref:multicast-eip.adoc[Multicast] EIP
is in use, to process the same
+Using a pipeline becomes necessary when you need to group together a series of
steps into a single logical step.
+For example, in the example below where xref:multicast-eip.adoc[Multicast] EIP
is in use, to process the same
message in two different pipelines. The first pipeline calls the something
bean, and the second pipeline
-calls the foo and bar beans and then route the message to another queue.
+calls the foo and bar beans and then routes the message to another queue.
[tabs]
====
