You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2019/08/12 09:13:41 UTC

[camel] branch master updated: CAMEL-13798: additional title fixes

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 8745711  CAMEL-13798: additional title fixes
8745711 is described below

commit 8745711c71c7473663044dabeeb563b452567a5f
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Mon Aug 12 11:13:31 2019 +0200

    CAMEL-13798: additional title fixes
---
 components/camel-ftp/src/main/docs/ftp-component.adoc      |  4 ++--
 components/camel-mina/src/main/docs/mina-component.adoc    |  4 ++--
 .../camel-quartz/src/main/docs/quartz-component.adoc       | 14 +++++++-------
 core/camel-core/src/main/docs/eips/process-eip.adoc        |  3 ++-
 docs/components/modules/ROOT/pages/ftp-component.adoc      |  4 ++--
 docs/components/modules/ROOT/pages/mina-component.adoc     |  4 ++--
 docs/components/modules/ROOT/pages/quartz-component.adoc   | 14 +++++++-------
 .../modules/ROOT/pages/commercial-camel-offerings.adoc     |  2 +-
 docs/user-manual/modules/ROOT/pages/content-enricher.adoc  |  2 +-
 docs/user-manual/modules/ROOT/pages/process-eip.adoc       |  3 ++-
 10 files changed, 28 insertions(+), 26 deletions(-)

diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index ca33797..c4a831c 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -485,7 +485,7 @@ FTP server we need to traverse and download files:
 And that we have a file in each of sub-a (a.txt) and sub-b (b.txt)
 folder.
 
-====Using stepwise=true (default mode)
+==== Using stepwise=true (default mode)
 
 [source,java]
 ----
@@ -575,7 +575,7 @@ disconnected.
 As you can see when stepwise is enabled, it will traverse the directory
 structure using CD xxx.
 
-====Using stepwise=false
+==== Using stepwise=false
 
 [source,java]
 ----
diff --git a/components/camel-mina/src/main/docs/mina-component.adoc b/components/camel-mina/src/main/docs/mina-component.adoc
index c2bebdc..bc4292d 100644
--- a/components/camel-mina/src/main/docs/mina-component.adoc
+++ b/components/camel-mina/src/main/docs/mina-component.adoc
@@ -211,7 +211,7 @@ Registry; for example, by creating a bean in the
 Spring XML file. Then use the `codec` option to specify the bean ID of
 your codec. See xref:hl7-dataformat.adoc[HL7] that has a custom codec.
 
-===Sample with sync=false
+=== Sample with sync=false
 
 In this sample, Camel exposes a service that listens for TCP connections
 on port 6200. We use the *textline* codec. In our route, we create a
@@ -235,7 +235,7 @@ template.sendBody("mina:tcp://localhost:" + port1 + "?textline=true&sync=false",
 assertMockEndpointsSatisfied();
 -------------------------------------------------------------------------------------------------
 
-===Sample with sync=true
+=== Sample with sync=true
 
 In the next sample, we have a more common use case where we expose a TCP
 service on port 6201 also use the textline codec. However, this time we
diff --git a/components/camel-quartz/src/main/docs/quartz-component.adoc b/components/camel-quartz/src/main/docs/quartz-component.adoc
index bcda1ba..eb224da 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -321,7 +321,7 @@ quartz://myGroup/myTimerName?cron=0/2+*+*+*+*+?trigger.misfireInstruction=2
 
 The simple and cron triggers has the following misfire instructions representative:
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_FIRE_NOW = 1 (default)
+=== SimpleTrigger.MISFIRE_INSTRUCTION_FIRE_NOW = 1 (default)
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be fired now by Scheduler.
@@ -330,7 +330,7 @@ This instruction should typically only be used for
 'one-shot' (non-repeating) Triggers. If it is used on a trigger with a
 repeat count > 0 then it is equivalent to the instruction MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT = 2
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT = 2
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -344,7 +344,7 @@ the start-time and repeat-count that it was originally setup with (this
 is only an issue if you for some reason wanted to be able to tell what
 the original values were at some later time).
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT = 3
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT = 3
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -365,7 +365,7 @@ This instruction could cause the Trigger
 to go to the 'COMPLETE' state after firing 'now', if all the
 repeat-fire-times where missed.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT = 4
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT = 4
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -376,7 +376,7 @@ repeat count set to what it would be, if it had not missed any firings.
 WARNING: This instruction could cause the Trigger
 to go directly to the 'COMPLETE' state if all fire-times where missed.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT = 5
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT = 5
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -387,12 +387,12 @@ WARNING: This instruction could cause the Trigger
 to go directly to the 'COMPLETE' state if the end-time of the trigger
 has arrived.
 
-====CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW = 1 (default)
+=== CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW = 1 (default)
 
 Instructs the Scheduler that upon a mis-fire
 situation, the CronTrigger wants to be fired now by Scheduler.
 
-====CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING = 2
+=== CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING = 2
 
 Instructs the Scheduler that upon a mis-fire
 situation, the CronTrigger wants to have it's
diff --git a/core/camel-core/src/main/docs/eips/process-eip.adoc b/core/camel-core/src/main/docs/eips/process-eip.adoc
index ff44400..7fdf400 100644
--- a/core/camel-core/src/main/docs/eips/process-eip.adoc
+++ b/core/camel-core/src/main/docs/eips/process-eip.adoc
@@ -16,7 +16,8 @@ The Process EIP supports 1 options which are listed below:
 // eip options: END
 
 == Samples
-==Using a processor in a route
+
+=== Using a processor in a route
 
 Once you have written a class which implements processor like this...
 
diff --git a/docs/components/modules/ROOT/pages/ftp-component.adoc b/docs/components/modules/ROOT/pages/ftp-component.adoc
index ca33797..c4a831c 100644
--- a/docs/components/modules/ROOT/pages/ftp-component.adoc
+++ b/docs/components/modules/ROOT/pages/ftp-component.adoc
@@ -485,7 +485,7 @@ FTP server we need to traverse and download files:
 And that we have a file in each of sub-a (a.txt) and sub-b (b.txt)
 folder.
 
-====Using stepwise=true (default mode)
+==== Using stepwise=true (default mode)
 
 [source,java]
 ----
@@ -575,7 +575,7 @@ disconnected.
 As you can see when stepwise is enabled, it will traverse the directory
 structure using CD xxx.
 
-====Using stepwise=false
+==== Using stepwise=false
 
 [source,java]
 ----
diff --git a/docs/components/modules/ROOT/pages/mina-component.adoc b/docs/components/modules/ROOT/pages/mina-component.adoc
index c2bebdc..bc4292d 100644
--- a/docs/components/modules/ROOT/pages/mina-component.adoc
+++ b/docs/components/modules/ROOT/pages/mina-component.adoc
@@ -211,7 +211,7 @@ Registry; for example, by creating a bean in the
 Spring XML file. Then use the `codec` option to specify the bean ID of
 your codec. See xref:hl7-dataformat.adoc[HL7] that has a custom codec.
 
-===Sample with sync=false
+=== Sample with sync=false
 
 In this sample, Camel exposes a service that listens for TCP connections
 on port 6200. We use the *textline* codec. In our route, we create a
@@ -235,7 +235,7 @@ template.sendBody("mina:tcp://localhost:" + port1 + "?textline=true&sync=false",
 assertMockEndpointsSatisfied();
 -------------------------------------------------------------------------------------------------
 
-===Sample with sync=true
+=== Sample with sync=true
 
 In the next sample, we have a more common use case where we expose a TCP
 service on port 6201 also use the textline codec. However, this time we
diff --git a/docs/components/modules/ROOT/pages/quartz-component.adoc b/docs/components/modules/ROOT/pages/quartz-component.adoc
index bcda1ba..eb224da 100644
--- a/docs/components/modules/ROOT/pages/quartz-component.adoc
+++ b/docs/components/modules/ROOT/pages/quartz-component.adoc
@@ -321,7 +321,7 @@ quartz://myGroup/myTimerName?cron=0/2+*+*+*+*+?trigger.misfireInstruction=2
 
 The simple and cron triggers has the following misfire instructions representative:
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_FIRE_NOW = 1 (default)
+=== SimpleTrigger.MISFIRE_INSTRUCTION_FIRE_NOW = 1 (default)
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be fired now by Scheduler.
@@ -330,7 +330,7 @@ This instruction should typically only be used for
 'one-shot' (non-repeating) Triggers. If it is used on a trigger with a
 repeat count > 0 then it is equivalent to the instruction MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT = 2
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT = 2
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -344,7 +344,7 @@ the start-time and repeat-count that it was originally setup with (this
 is only an issue if you for some reason wanted to be able to tell what
 the original values were at some later time).
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT = 3
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT = 3
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -365,7 +365,7 @@ This instruction could cause the Trigger
 to go to the 'COMPLETE' state after firing 'now', if all the
 repeat-fire-times where missed.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT = 4
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT = 4
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -376,7 +376,7 @@ repeat count set to what it would be, if it had not missed any firings.
 WARNING: This instruction could cause the Trigger
 to go directly to the 'COMPLETE' state if all fire-times where missed.
 
-====SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT = 5
+=== SimpleTrigger.MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT = 5
 
 Instructs the Scheduler that upon a mis-fire
 situation, the SimpleTrigger wants to be
@@ -387,12 +387,12 @@ WARNING: This instruction could cause the Trigger
 to go directly to the 'COMPLETE' state if the end-time of the trigger
 has arrived.
 
-====CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW = 1 (default)
+=== CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW = 1 (default)
 
 Instructs the Scheduler that upon a mis-fire
 situation, the CronTrigger wants to be fired now by Scheduler.
 
-====CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING = 2
+=== CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING = 2
 
 Instructs the Scheduler that upon a mis-fire
 situation, the CronTrigger wants to have it's
diff --git a/docs/user-manual/modules/ROOT/pages/commercial-camel-offerings.adoc b/docs/user-manual/modules/ROOT/pages/commercial-camel-offerings.adoc
index 6dd976e..2367a5e 100644
--- a/docs/user-manual/modules/ROOT/pages/commercial-camel-offerings.adoc
+++ b/docs/user-manual/modules/ROOT/pages/commercial-camel-offerings.adoc
@@ -31,7 +31,7 @@ Software. We specialize in helping our clients to realize new projects
 and support the delivery of the project from end to end.
 
 [[CommercialCamelOfferings-Evosent]]
-=====tp://evosent.com/?utm_source=apache&utm_medium=web&utm_campaign=commercial_support[Evosent]
+== http://evosent.com/?utm_source=apache&utm_medium=web&utm_campaign=commercial_support[Evosent]
 
 http://evosent.com/?utm_source=apache&utm_medium=web&utm_campaign=commercial_support[Evosent] is
 a boutique consultancy based in Europe. It specialises in open source
diff --git a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
index f611c14..f4a94d8 100644
--- a/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
+++ b/docs/user-manual/modules/ROOT/pages/content-enricher.adoc
@@ -340,7 +340,7 @@ polling
 * receive(timeout)
 
 [[ContentEnricher-PollEnrichOptions]]
-===PollEnrich Options
+=== PollEnrich Options
 
 [width="100%",cols="34%,33%,33%",options="header",]
 |=======================================================================
diff --git a/docs/user-manual/modules/ROOT/pages/process-eip.adoc b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
index ff44400..7fdf400 100644
--- a/docs/user-manual/modules/ROOT/pages/process-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/process-eip.adoc
@@ -16,7 +16,8 @@ The Process EIP supports 1 options which are listed below:
 // eip options: END
 
 == Samples
-==Using a processor in a route
+
+=== Using a processor in a route
 
 Once you have written a class which implements processor like this...