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 3b3fff0804f04079f8a6bf87ee9445e41bee2d27 Author: Otavio Rodolfo Piske <[email protected]> AuthorDate: Mon Feb 26 10:50:50 2024 +0100 CAMEL-20459: minor documentation tweaks for the point-to-point channel EIP. --- .../src/main/docs/modules/eips/pages/point-to-point-channel.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/point-to-point-channel.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/point-to-point-channel.adoc index c2c1aa0a53e..75f1b378f7b 100644 --- a/core/camel-core-engine/src/main/docs/modules/eips/pages/point-to-point-channel.adoc +++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/point-to-point-channel.adoc @@ -5,7 +5,7 @@ Camel supports the http://www.enterpriseintegrationpatterns.com/PointToPointChannel.html[Point to Point Channel] from the xref:enterprise-integration-patterns.adoc[EIP patterns]. -An application is using Messaging to make remote procedure calls (RPC’s) or transfer documents. +An application is using Messaging to make remote procedure calls (RPC) or transfer documents. How can the caller be sure that exactly one receiver will receive the document or perform the call? @@ -20,7 +20,7 @@ The Point to Point Channel is supported in Camel by messaging based xref:ROOT:in * xref:ROOT:seda-component.adoc[SEDA] for internal Camel seda queue based messaging * xref:ROOT:spring-rabbitmq-component.adoc[Spring RabbitMQ] for working with AMQP Queues (RabbitMQ) -There are also messaging based in the cloud from cloud providers such as Amazon, Google and Azure. +There is also messaging based in the cloud from cloud providers such as Amazon, Google and Azure. TIP: See also the related xref:publish-subscribe-channel.adoc[Publish Scribe Channel] EIP
