[camel] 03/03: CAMEL-17422: Grammar

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 998e7ed358b395f0186cd2b75e86d40eb664cb76
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Thu Jan 6 10:12:30 2022 +0100

    CAMEL-17422: Grammar
---
 docs/user-manual/modules/ROOT/pages/exception-clause.adoc           | 6 +++---
 .../why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc  | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
index 808549f..4c6310a 100644
--- a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
@@ -691,10 +691,10 @@ would be:
 The original input means the input message that are bounded by the current unit of work. An unit of work typically spans one route, or multiple routes if they are connected 
 using internal endpoints such as direct or seda. When messages are passed via external
 endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the
-message it received as input as the original input. Also some EIP patterns such as splitter,
+message it received as input as the original input. Also, some EIP patterns such as splitter,
 multicast, will create a new unit of work boundary for the messages in their sub-route
-(eg the splitted message); however these EIPs have an option named shareUnitOfWork which
-allows to combine with the parent unit of work in regard to error handling and therefore use
+(i.e. the split message); however these EIPs have an option named shareUnitOfWork which
+allows combining with the parent unit of work in regard to error handling and therefore use
 the parent original message.
 
 == Using `useOriginalBody`
diff --git a/docs/user-manual/modules/faq/pages/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc b/docs/user-manual/modules/faq/pages/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
index a995b9d..73d74e7 100644
--- a/docs/user-manual/modules/faq/pages/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
+++ b/docs/user-manual/modules/faq/pages/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.adoc
@@ -81,7 +81,7 @@ xref:components:eips:enterprise-integration-patterns.adoc[EIP]s which often have
 methods to configure or as part of the
 xref:components:eips:enterprise-integration-patterns.adoc[EIP] itself. For example the
 xref:components:eips:split-eip.adoc[Splitter] EIP has a sub-route which denotes the
-routing of each splitted message. You would also have to use
+routing of each split message. You would also have to use
 `.endChoice()` to indicate the end of the sub-route and to return back
 to the xref:components:eips:choice-eip.adoc[Content Based Router].