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 dfe894ae18a118aed8fde483a53f8c78e88f0023
Author: Otavio R. Piske <angusyo...@gmail.com>
AuthorDate: Sun Feb 25 14:53:01 2024 +0100
CAMEL-20459: minor documentation tweaks for the messaging gateway EIP.
Signed-off-by: Otavio R. Piske <angusyo...@gmail.com>
---
.../src/main/docs/modules/eips/pages/messaging-gateway.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
index c19316acb8e..19e42219584 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-gateway.adoc
@@ -8,10 +8,10 @@ How do you encapsulate access to the messaging system from
the rest of the appli
image::eip/MessagingGatewaySolution.gif[image]
-Use a Messaging Gateway, a class than wraps messaging-specific method calls
and exposes domain-specific methods to the application.
+Use a Messaging Gateway, a class that wraps messaging-specific method calls
and exposes domain-specific methods to the application.
Camel has several endpoint components that support the Messaging Gateway from
the EIP patterns.
-Components like xref:ROOT:bean-component.adoc[Bean] provides a way to bind a
Java interface to the message exchange.
+Components like xref:ROOT:bean-component.adoc[Bean] provide a way to bind a
Java interface to the message exchange.
Another approach is to use `@Produce` annotations
(xref:manual::pojo-producing.adoc[POJO Producing])
which also can be used to hide Camel APIs and thereby encapsulate access,
acting as a Messaging Gateway EIP solution.
