[camel] branch master updated: CAMEL-13928: Fix broken links

[zr...@apache.org]

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

zregvart 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 e1e7bd7  CAMEL-13928: Fix broken links
e1e7bd7 is described below

commit e1e7bd7494ad6b399f72c58d2f250687e1a53792
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Mon Sep 2 10:43:23 2019 +0200

    CAMEL-13928: Fix broken links
---
 docs/user-manual/modules/ROOT/pages/binding.adoc       | 2 +-
 docs/user-manual/modules/ROOT/pages/event-message.adoc | 4 ++--
 docs/user-manual/modules/ROOT/pages/faq.adoc           | 2 +-
 docs/user-manual/modules/ROOT/pages/servicepool.adoc   | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/binding.adoc b/docs/user-manual/modules/ROOT/pages/binding.adoc
index b914cbf..b9820f7 100644
--- a/docs/user-manual/modules/ROOT/pages/binding.adoc
+++ b/docs/user-manual/modules/ROOT/pages/binding.adoc
@@ -5,7 +5,7 @@ In Camel terms a _binding_ is a way of wrapping an
 xref:endpoint.adoc[Endpoint] in a contract; such as a
 xref:data-format.adoc[Data Format], a xref:content-enricher.adoc[Content
 Enricher] or validation step. Bindings are completely optional and you
-can choose to use them on any xref:xref:components::index.adoc[camel endpoint].
+can choose to use them on any xref:components::index.adoc[camel endpoint].
 
 Bindings are inspired by the work of
 http://www.jboss.org/switchyard[SwitchYard project] adding service
diff --git a/docs/user-manual/modules/ROOT/pages/event-message.adoc b/docs/user-manual/modules/ROOT/pages/event-message.adoc
index 0f70b4a..8242c05 100644
--- a/docs/user-manual/modules/ROOT/pages/event-message.adoc
+++ b/docs/user-manual/modules/ROOT/pages/event-message.adoc
@@ -6,12 +6,12 @@ http://www.enterpriseintegrationpatterns.com/EventMessage.html[Event
 Message] from the xref:enterprise-integration-patterns.adoc[EIP
 patterns] by supporting the xref:exchange-pattern.adoc[Exchange Pattern]
 on a xref:message.adoc[Message] which can be set to *InOnly* to indicate
-a oneway event message. Camel xref:xref:components::index.adoc[Components] then
+a oneway event message. Camel xref:components::index.adoc[Components] then
 implement this pattern using the underlying transport or protocols.
 
 image::eip/EventMessageSolution.gif[image]
 
-The default behaviour of many xref:xref:components::index.adoc[Components] is InOnly
+The default behaviour of many xref:components::index.adoc[Components] is InOnly
 such as for xref:components::jms-component.adoc[JMS], xref:components::jms-component.adoc[File] or
 xref:components::seda-component.adoc[SEDA]
 
diff --git a/docs/user-manual/modules/ROOT/pages/faq.adoc b/docs/user-manual/modules/ROOT/pages/faq.adoc
index 9ca7437..691e0c2 100644
--- a/docs/user-manual/modules/ROOT/pages/faq.adoc
+++ b/docs/user-manual/modules/ROOT/pages/faq.adoc
@@ -133,7 +133,7 @@ xref:components::log-component.adoc[Log] endpoint or JDK 1.4 logging or Log4j et
 [[FAQ-CamelEndpointQuestions]]
 == Camel Endpoint Questions
 
-Questions on using the various Camel xref:xref:components::index.adoc[Components]
+Questions on using the various Camel xref:components::index.adoc[Components]
 and xref:endpoint.adoc[Endpoint] implementations
 
 * xref:faq/how-do-i-invoke-camel-routes-from-jbi.adoc[How do I invoke Camel routes from JBI?]
diff --git a/docs/user-manual/modules/ROOT/pages/servicepool.adoc b/docs/user-manual/modules/ROOT/pages/servicepool.adoc
index bf231f0..eaf8627 100644
--- a/docs/user-manual/modules/ROOT/pages/servicepool.adoc
+++ b/docs/user-manual/modules/ROOT/pages/servicepool.adoc
@@ -13,7 +13,7 @@ The default producer service pool is
 default in Camel for pooling Producer.
 
 The need for pooling Producer is only apparent in some
-xref:xref:components::index.adoc[Components] in Camel to support thread safe
+xref:components::index.adoc[Components] in Camel to support thread safe
 producers and support concurrency. And using pooling we can improve
 performance as we do not have the overhead of creating, starting and
 stopping the Producer at each invocation. So where is it needed then?