[camel] 05/09: async.adoc fixed but asynchronous-processing.adoc missing

[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

commit 349bb6df622c0fa56e2fe319b66fbc219b3064e0
Author: nayananga@acerubuntu18.04 <na...@gmail.com>
AuthorDate: Sat Jun 22 08:15:39 2019 +0530

    async.adoc fixed but asynchronous-processing.adoc missing
---
 docs/user-manual/modules/ROOT/pages/async.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/async.adoc b/docs/user-manual/modules/ROOT/pages/async.adoc
index afd4d26..53b817b 100644
--- a/docs/user-manual/modules/ROOT/pages/async.adoc
+++ b/docs/user-manual/modules/ROOT/pages/async.adoc
@@ -121,8 +121,8 @@ application is still waiting. +
  3. The message is processed completely and the control is returned to
 the client.
 
-So why do you want to use synchronous link:event-message.html[Request
-Only]? Well if you want to know whether the message was processed
+So why do you want to use synchronous xref:event-message.adoc[Request Only]? 
+Well if you want to know whether the message was processed
 successfully or not before continuing. With synchronous it allows you to
 wait while the message is being processed. In case the processing was
 successful the control is returned to the client with no notion of error.
@@ -485,8 +485,8 @@ The `threads` DSL leverages the JDK concurrency framework for multi
 threading. It can be used to turn a synchronous route into
 Async. What happens is that from the point forwards
 from `threads` the messages is routed asynchronous in a new thread.
-Camel leverages the link:asynchronous-processing.html[asynchronous
-routing engine], which was re-introduced in Camel 2.4, to continue
+Camel leverages the xref:asynchronous-processing.adoc[asynchronous routing engine], 
+which was re-introduced in Camel 2.4, to continue
 routing the Exchange asynchronously.
 
 The `threads` DSL supports the following options: