[camel] branch master updated: Typo mistake about HTTP (#3938)

[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 c86c860  Typo mistake about HTTP (#3938)
c86c860 is described below

commit c86c860b7c5b5ef754970291b7ad7c4b32b443c6
Author: julienbonnard <43...@users.noreply.github.com>
AuthorDate: Mon Jun 22 13:30:29 2020 +0200

    Typo mistake about HTTP (#3938)
---
 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 aea6000..adb8456 100644
--- a/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
+++ b/docs/user-manual/modules/ROOT/pages/exception-clause.adoc
@@ -719,7 +719,7 @@ 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 is passed via external
-endpoints such as JMS or HTT then the consumer will create a new unit of work, with the
+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
 (eg the splitted message); however these EIPs have an option named shareUnitOfWork which