[camel] branch master updated: Document update (#4190)

[ac...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 942fc8c  Document update (#4190)
942fc8c is described below

commit 942fc8c6e0230d9cf483ba3ce1fe29e9d649e9ec
Author: Nitesh Koushik S <39...@users.noreply.github.com>
AuthorDate: Fri Sep 11 13:28:56 2020 +0530

    Document update (#4190)
    
    Change in key word from "messages is" to "messages are"
---
 docs/user-manual/modules/ROOT/pages/exception-clause.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
index f420018..222c6ba 100644
--- a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
@@ -718,7 +718,7 @@ would be:
 == Boundary of original message
 
 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 is passed via external
+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,
 multicast, will create a new unit of work boundary for the messages in their sub-route