[camel] branch master updated: Cleanup documentation

[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 54ef429  Cleanup documentation
54ef429 is described below

commit 54ef429c7a1700ab8db32db7fec11f54a3f99c5d
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Fri Feb 19 09:44:25 2021 +0100

    Cleanup documentation
---
 .../main/docs/modules/eips/pages/recipientList-eip.adoc    | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/recipientList-eip.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/recipientList-eip.adoc
index a74a469..c5cd4ed 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/recipientList-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/recipientList-eip.adoc
@@ -327,22 +327,20 @@ from("direct:c").to("mock:C").setBody(constant("C"));
 ----
 
 [NOTE]
-===
-*Timeout in other EIPs*
-
+.Timeout in other EIPs
+====
 This timeout feature is also supported by Splitter and both multicast and recipientList.
-===
+====
 
 By default if a timeout occurs the `AggregationStrategy` is not invoked. However you can implement the `timeout` method:
 This allows you to deal with the timeout in the `AggregationStrategy` if you really need to.
 
 [NOTE]
-===
-*Timeout is total*
-
+.Timeout is total
+====
 The timeout is total, which means that after X time, Camel will aggregate the messages which have completed within the timeframe.
 The remainders will be cancelled. Camel will also only invoke the `timeout` method in the `TimeoutAwareAggregationStrategy` once, for the first index which caused the timeout.
-===
+====
 
 == Using onPrepare to execute custom logic when preparing messages
 See details at the Multicast EIP