Quantcast

[01/14] camel git commit: Make heading in adoc files sane again.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[01/14] camel git commit: Make heading in adoc files sane again.

davsclaus-2
Repository: camel
Updated Branches:
  refs/heads/master e378f76f3 -> 284296813


Make heading in adoc files sane again.


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/11dfcc00
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/11dfcc00
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/11dfcc00

Branch: refs/heads/master
Commit: 11dfcc00b44070f07c3dc0d2c06daf56d6afe191
Parents: e378f76
Author: Claus Ibsen <[hidden email]>
Authored: Wed Jan 11 18:30:25 2017 +0100
Committer: Claus Ibsen <[hidden email]>
Committed: Wed Jan 11 19:26:15 2017 +0100

----------------------------------------------------------------------
 .../maven/packaging/ReadmeComponentMojo.java    | 97 ++++++++++----------
 1 file changed, 48 insertions(+), 49 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/11dfcc00/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
----------------------------------------------------------------------
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
index 8393470..3725acf 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
+++ b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/ReadmeComponentMojo.java
@@ -24,6 +24,7 @@ import java.util.List;
 import java.util.Map;
 import java.util.Set;
 import java.util.TreeSet;
+import java.util.stream.Collectors;
 
 import org.apache.camel.maven.packaging.model.ComponentModel;
 import org.apache.camel.maven.packaging.model.ComponentOptionModel;
@@ -131,7 +132,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
                     boolean exists = file.exists();
                     boolean updated = false;
 
-                    updated |= updateTitle(file, model.getTitle() + " Component");
+                    updated |= updateTitles(file, model.getTitle() + " Component");
 
                     if (model.getComponentOptions() != null) {
                         String options = templateComponentOptions(model);
@@ -182,7 +183,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
                     boolean exists = file.exists();
                     boolean updated = false;
 
-                    updated |= updateTitle(file, model.getTitle() + " DataFormat");
+                    updated |= updateTitles(file, model.getTitle() + " DataFormat");
 
                     if (model.getDataFormatOptions() != null) {
                         String options = templateDataFormatOptions(model);
@@ -260,7 +261,7 @@ public class ReadmeComponentMojo extends AbstractMojo {
                     boolean exists = file.exists();
                     boolean updated = false;
 
-                    updated |= updateTitle(file, model.getTitle() + " Language");
+                    updated |= updateTitles(file, model.getTitle() + " Language");
 
                     if (model.getLanguageOptions() != null) {
                         String options = templateLanguageOptions(model);
@@ -282,71 +283,69 @@ public class ReadmeComponentMojo extends AbstractMojo {
         }
     }
 
-    private boolean updateTitle(File file, String title) throws MojoExecutionException {
+    private boolean updateTitles(File file, String title) throws MojoExecutionException {
         if (!file.exists()) {
             return false;
         }
 
-        // they may be in old title format which we want to avoid
-        // [[Bean-BeanComponent]]
-        // Bean Component
-        // ~~~~~~~~~~~~~~
+        boolean updated = false;
 
         try {
             String text = loadText(new FileInputStream(file));
 
-            // grab the first 3 lines which can have old legacy format
-            String before = StringHelper.before(text, "\n");
-            text = StringHelper.after(text, "\n");
-            String before2 = StringHelper.before(text, "\n");
-            text = StringHelper.after(text, "\n");
-            String before3 = StringHelper.before(text, "\n");
-            text = StringHelper.after(text, "\n");
-
-            // skip old title format
-            if (before3 != null && before3.startsWith("~~~")) {
-                before = null;
-                before2 = null;
-                before3 = null;
-            }
-            if (before2 != null && before2.startsWith("~~~")) {
-                before = null;
-                before2 = null;
-            }
+            List<String> newLines = new ArrayList<>();
 
-            String oldTitle = before;
-            if (oldTitle == null) {
-                oldTitle = before2;
-            }
-            if (oldTitle == null) {
-                oldTitle = before3;
-            }
+            String[] lines = text.split("\n");
+            for (int i = 0; i < lines.length; i++) {
+                String line = lines[i];
 
-            String changed = "# " + title;
-            if (!changed.equals(oldTitle)) {
-                // insert title in top of file
-                String newText = changed + "\n";
-                // keep the before lines that was okay to keep
-                if (before != null) {
-                    newText += before + "\n";
+                if (i == 0) {
+                    // first line is the title to make the text less noisy we use level 2
+                    String newLine = "## " + title;
+                    newLines.add(newLine);
+                    updated = !line.equals(newLine);
+                    continue;
                 }
-                if (before2 != null) {
-                    newText += before2 + "\n";
-                }
-                if (before3 != null) {
-                    newText += before3 + "\n";
+
+                // use single line headers with # as level instead of the cumbersome adoc weird style
+                if (line.startsWith("^^^") || line.startsWith("~~~") || line.startsWith("+++") ) {
+                    String level = line.startsWith("+++") ? "####" : "###";
+
+                    // transform legacy heading into new style
+                    int idx = newLines.size() - 1;
+                    String prev = newLines.get(idx);
+
+                    newLines.set(idx, level + " " + prev);
+
+                    // okay if 2nd-prev line is a [[title]] we need to remove that too
+                    // so we have nice clean sub titles
+                    idx = newLines.size() - 2;
+                    if (idx >= 0) {
+                        prev = newLines.get(idx);
+                        if (prev.startsWith("[[")) {
+                            // remove
+                            newLines.remove(idx);
+                        }
+                    }
+
+                    updated = true;
+                } else {
+                    // okay normal text so just add it
+                    newLines.add(line);
                 }
-                // and remember the doc body
-                newText += text;
+            }
+
 
+            if (updated) {
+                // build the new updated text
+                String newText = newLines.stream().collect(Collectors.joining("\n"));
                 writeText(file, newText);
-                return true;
             }
         } catch (Exception e) {
             throw new MojoExecutionException("Error reading file " + file + " Reason: " + e, e);
         }
 
-        return false;
+        return updated;
     }
 
     private boolean updateComponentOptions(File file, String changed) throws MojoExecutionException {

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[02/14] camel git commit: Use single line header for adoc files

davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-twitter/src/main/docs/twitter-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-twitter/src/main/docs/twitter-component.adoc b/components/camel-twitter/src/main/docs/twitter-component.adoc
index 246f13d..72196d3 100644
--- a/components/camel-twitter/src/main/docs/twitter-component.adoc
+++ b/components/camel-twitter/src/main/docs/twitter-component.adoc
@@ -1,4 +1,4 @@
-# Twitter Component
+## Twitter Component
 ifdef::env-github[]
 :caution-caption: :boom:
 :important-caption: :exclamation:
@@ -8,9 +8,7 @@ ifdef::env-github[]
 endif::[]
 
 [[ConfluenceContent]]
-[[Twitter-Twitter]]
-Twitter
-~~~~~~~
+### Twitter
 
 *Available as of Camel 2.10*
 
@@ -38,18 +36,14 @@ for this component:
 </dependency>
 ----
 
-[[Twitter-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
 twitter://endpoint[?options]
 ----
 
-[[Twitter-TwitterComponent]]
-Twitter component
-^^^^^^^^^^^^^^^^^
+### Twitter component
 
 The twitter component can be configured with the Twitter account
 settings which is mandatory to configure before using.
@@ -85,9 +79,7 @@ The Twitter component supports 8 options which are listed below.
 
 You can also configure these options directly in the endpoint.
 
-[[Twitter-ConsumerEndpoints]]
-Consumer endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer endpoints
 
 Rather than the endpoints returning a List through one single route
 exchange, camel-twitter creates one route exchange per returned object.
@@ -130,9 +122,7 @@ polling* |[line-through]*twitter4j.Status* |[line-through]*@deprecated.
 Removed from Camel 2.11 onwards.*
 |=======================================================================
 
-[[Twitter-ProducerEndpoints]]
-Producer endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer endpoints
 
 [width="100%",cols="20%,80%",options="header",]
 |==============================
@@ -142,9 +132,7 @@ Producer endpoints
 |timeline/user |String
 |==============================
 
-[[Twitter-URIOptions]]
-URI options
-^^^^^^^^^^^
+### URI options
 
 
 
@@ -212,9 +200,7 @@ The Twitter component supports 43 endpoint options which are listed below:
 
 
 
-[[Twitter-Messageheaders]]
-Message headers
-^^^^^^^^^^^^^^^
+### Message headers
 
 [width="100%",cols="20%,80%",options="header",]
 |=======================================================================
@@ -234,15 +220,11 @@ the option of `numberOfPages` which sets how many pages we want to
 twitter returns.
 |=======================================================================
 
-[[Twitter-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
 
 All message bodies utilize objects provided by the Twitter4J API.
 
-[[Twitter-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
 
 NOTE: *API Rate Limits:* Twitter REST APIs encapsulated by http://twitter4j.org/[Twitter4J] are
 subjected to https://dev.twitter.com/rest/public/rate-limiting[API Rate
@@ -251,9 +233,7 @@ https://dev.twitter.com/rest/public/rate-limits[API Rate Limits]
 documentation. Note that endpoints/resources not listed in that page are
 default to 15 requests per allotted user per window.
 
-[[Twitter-TocreateastatusupdatewithinyourTwitterprofile,sendthisproduceraStringbody]]
-To create a status update within your Twitter profile, send this producer a String body:
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To create a status update within your Twitter profile, send this producer a String body:
 
 [source,java]
 ----
@@ -261,9 +241,7 @@ from("direct:foo")
   .to("twitter://timeline/user?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]);
 ----
 
-[[Twitter-Topoll,every60sec.,allstatusesonyourhometimeline]]
-To poll, every 60 sec., all statuses on your home timeline:
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To poll, every 60 sec., all statuses on your home timeline:
 
 [source,java]
 ----
@@ -271,9 +249,7 @@ from("twitter://timeline/home?type=polling&delay=60&consumerKey=[s]&consumerSecr
   .to("bean:blah");
 ----
 
-[[Twitter-TosearchforallstatuseswiththekeywordCamel]]
-To search for all statuses with the keyword 'camel':
-++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### To search for all statuses with the keyword 'camel':
 
 [source,java]
 ----
@@ -281,9 +257,7 @@ from("twitter://search?type=direct&keywords=camel&consumerKey=[s]&consumerSecret
   .to("bean:blah");
 ----
 
-[[Twitter-Searchingusingaproducerwithstatickeywords]]
-Searching using a producer with static keywords:
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Searching using a producer with static keywords:
 
 [source,java]
 ----
@@ -291,9 +265,7 @@ from("direct:foo")
   .to("twitter://search?keywords=camel&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
 ----
 
-[[Twitter-Searchingusingaproducerwithdynamickeywordsfromheader]]
-Searching using a producer with dynamic keywords from header:
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Searching using a producer with dynamic keywords from header:
 
 In the `bar` header we have the keywords we want to search, so we can
 assign this value to the `CamelTwitterKeywords` header:
@@ -305,20 +277,16 @@ from("direct:foo")
   .to("twitter://search?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
 ----
 
-[[Twitter-Example]]
-Example
-^^^^^^^
+### Example
 
 See also the link:twitter-websocket-example.html[Twitter Websocket
 Example].
 
-[[Twitter-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:twitter-websocket-example.html[Twitter Websocket Example]
+* link:twitter-websocket-example.html[Twitter Websocket Example]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-undertow/src/main/docs/undertow-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-undertow/src/main/docs/undertow-component.adoc b/components/camel-undertow/src/main/docs/undertow-component.adoc
index cc4143d..66373a9 100644
--- a/components/camel-undertow/src/main/docs/undertow-component.adoc
+++ b/components/camel-undertow/src/main/docs/undertow-component.adoc
@@ -1,4 +1,4 @@
-# Undertow Component
+## Undertow Component
 
 *Available as of Camel 2.16*
 
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Undertow-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------------------
@@ -33,9 +31,7 @@ undertow:http://hostname[:port][/resourceUri][?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Undertow-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -93,9 +89,7 @@ The Undertow component supports 18 endpoint options which are listed below:
 
 
 
-[[Undertow-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel uses the same message headers as the link:http.html[HTTP]
 component.
@@ -108,9 +102,7 @@ example, given a client request with the URL,
 `http://myserver/myserver?orderid=123`, the exchange will contain a
 header named `orderid` with the value 123.
 
-[[Undertow-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
 
 The following is a basic example of how to send an HTTP request to an
 existing HTTP endpoint.
@@ -132,9 +124,7 @@ or in Spring XML
 <route>
 ----------------------------------------------
 
-[[Undertow-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
 
 In this sample we define a route that exposes a HTTP service at
 `http://localhost:8080/myapp/myservice`:
@@ -167,9 +157,7 @@ Servlet, you should instead refer to the
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=46339[Servlet
 Transport].
 
-[[Undertow-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -177,5 +165,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:jetty.html[Jetty]
-* link:http.html[HTTP]
-
+* link:http.html[HTTP]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
index 923d509..1bf0e75 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-csv-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity CSV DataFormat
+## uniVocity CSV DataFormat
 
 *Available as of Camel 2.15.0*
 
@@ -28,9 +28,7 @@ download page for the latest versions]).
 </dependency>
 ----------------------------------------------------
 
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
 
 Most configuration options of the uniVocity-parsers are available in the
 data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
 The 3 data formats share common options and have dedicated ones, this
 section presents them all.
 
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // dataformat options: START
@@ -79,9 +75,7 @@ The uniVocity CSV dataformat supports 18 options which are listed below.
 
 
 
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
 
 The marshalling accepts either:
 
@@ -90,9 +84,7 @@ The marshalling accepts either:
 
 Any other body will throws an exception.
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -105,9 +97,7 @@ Usage example: marshalling a Map into CSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -124,9 +114,7 @@ Usage example: marshalling a Map into fixed-width format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -139,9 +127,7 @@ Usage example: marshalling a Map into TSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
 
 The unmarshalling uses an `InputStream` in order to read the data.
 
@@ -156,9 +142,7 @@ All the rows can either:
 * be collected at once into a list (`lazyLoad` option with `false`);
 * be read on the fly using an iterator (`lazyLoad` option with `true`).
 
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -171,9 +155,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -188,5 +170,4 @@ Usage example: unmarshalling a fixed-width format into lists
     </unmarshal>
     <to uri="mock:result"/>
 </route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
index f834d92..86abe57 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-fixed-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity Fixed Length DataFormat
+## uniVocity Fixed Length DataFormat
 
 *Available as of Camel 2.15.0*
 
@@ -28,9 +28,7 @@ download page for the latest versions]).
 </dependency>
 ----------------------------------------------------
 
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
 
 Most configuration options of the uniVocity-parsers are available in the
 data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
 The 3 data formats share common options and have dedicated ones, this
 section presents them all.
 
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // dataformat options: START
@@ -78,9 +74,7 @@ The uniVocity Fixed Length dataformat supports 17 options which are listed below
 
 
 
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
 
 The marshalling accepts either:
 
@@ -89,9 +83,7 @@ The marshalling accepts either:
 
 Any other body will throws an exception.
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -104,9 +96,7 @@ Usage example: marshalling a Map into CSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -123,9 +113,7 @@ Usage example: marshalling a Map into fixed-width format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -138,9 +126,7 @@ Usage example: marshalling a Map into TSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
 
 The unmarshalling uses an `InputStream` in order to read the data.
 
@@ -155,9 +141,7 @@ All the rows can either:
 * be collected at once into a list (`lazyLoad` option with `false`);
 * be read on the fly using an iterator (`lazyLoad` option with `true`).
 
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -170,9 +154,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -187,5 +169,4 @@ Usage example: unmarshalling a fixed-width format into lists
     </unmarshal>
     <to uri="mock:result"/>
 </route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
index 9a21af3..c7e812f 100644
--- a/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
+++ b/components/camel-univocity-parsers/src/main/docs/univocity-tsv-dataformat.adoc
@@ -1,4 +1,4 @@
-# uniVocity TSV DataFormat
+## uniVocity TSV DataFormat
 
 *Available as of Camel 2.15.0*
 
@@ -28,9 +28,7 @@ download page for the latest versions]).
 </dependency>
 ----------------------------------------------------
 
-[[uniVocity-parsersformats-Options]]
-Options
-^^^^^^^
+### Options
 
 Most configuration options of the uniVocity-parsers are available in the
 data formats. If you want more information about a particular option,
@@ -41,9 +39,7 @@ page].
 The 3 data formats share common options and have dedicated ones, this
 section presents them all.
 
-[[uniVocity-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // dataformat options: START
@@ -76,9 +72,7 @@ The uniVocity TSV dataformat supports 15 options which are listed below.
 
 
 
-[[uniVocity-parsersformats-Marshallingusages]]
-Marshalling usages
-^^^^^^^^^^^^^^^^^^
+### Marshalling usages
 
 The marshalling accepts either:
 
@@ -87,9 +81,7 @@ The marshalling accepts either:
 
 Any other body will throws an exception.
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoCSVformat]]
-Usage example: marshalling a Map into CSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into CSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -102,9 +94,7 @@ Usage example: marshalling a Map into CSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintofixed-widthformat]]
-Usage example: marshalling a Map into fixed-width format
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into fixed-width format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -121,9 +111,7 @@ Usage example: marshalling a Map into fixed-width format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexample:marshallingaMapintoTSVformat]]
-Usage example: marshalling a Map into TSV format
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: marshalling a Map into TSV format
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -136,9 +124,7 @@ Usage example: marshalling a Map into TSV format
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Unmarshallingusages]]
-Unmarshalling usages
-^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling usages
 
 The unmarshalling uses an `InputStream` in order to read the data.
 
@@ -153,9 +139,7 @@ All the rows can either:
 * be collected at once into a list (`lazyLoad` option with `false`);
 * be read on the fly using an iterator (`lazyLoad` option with `true`).
 
-[[uniVocity-parsersformats-UsageexampleunmarshallingaCSVformatintomapswithautomaticheaders]]
-Usage example: unmarshalling a CSV format into maps with automatic headers
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a CSV format into maps with automatic headers
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -168,9 +152,7 @@ Usage example: unmarshalling a CSV format into maps with automatic headers
 </route>
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[uniVocity-parsersformats-Usageexampleunmarshallingafixed-widthformatintolists]]
-Usage example: unmarshalling a fixed-width format into lists
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Usage example: unmarshalling a fixed-width format into lists
 
 [source,xml]
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ -185,5 +167,4 @@ Usage example: unmarshalling a fixed-width format into lists
     </unmarshal>
     <to uri="mock:result"/>
 </route>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-velocity/src/main/docs/velocity-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-velocity/src/main/docs/velocity-component.adoc b/components/camel-velocity/src/main/docs/velocity-component.adoc
index 83b5b0b..ea9026e 100644
--- a/components/camel-velocity/src/main/docs/velocity-component.adoc
+++ b/components/camel-velocity/src/main/docs/velocity-component.adoc
@@ -1,4 +1,4 @@
-# Velocity Component
+## Velocity Component
 
 The *velocity:* component allows you to process a message using an
 http://velocity.apache.org/[Apache Velocity] template. This can be ideal
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Velocity-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
@@ -34,9 +32,7 @@ file://folder/myfile.vm[file://folder/myfile.vm]).
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Velocity-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -75,9 +71,7 @@ The Velocity component supports 6 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Velocity-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The velocity component sets a couple headers on the message (you can't
 set these yourself and from Camel 2.1 velocity component will not set
@@ -111,9 +105,7 @@ $in.setHeader("fruit", "Apple")
 
 The `fruit` header is now accessible from the `message.out.headers`.
 
-[[Velocity-VelocityContext]]
-Velocity Context
-^^^^^^^^^^^^^^^^
+### Velocity Context
 
 Camel will provide exchange information in the Velocity context (just a
 `Map`). The `Exchange` is transfered as:
@@ -152,9 +144,7 @@ setting the message header *CamelVelocityContext *just like this
 
 Â 
 
-[[Velocity-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
 
 The Velocity template resource is, by default, hot reloadable for both
 file and classpath resources (expanded jar). If you set
@@ -162,9 +152,7 @@ file and classpath resources (expanded jar). If you set
 hot reloading is not possible. This scenario can be used in production,
 when the resource never changes.
 
-[[Velocity-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
 
 *Available as of Camel 2.1* +
  Camel provides two headers by which you can define a different resource
@@ -182,9 +170,7 @@ endpoint configured.
 |CamelVelocityTemplate |String |*Camel 2.1:* The template to use instead of the endpoint configured.
 |=======================================================================
 
-[[Velocity-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use something like
 
@@ -246,9 +232,7 @@ from("direct:in").
   to("velocity:dummy");
 ---------------------------------------------------------------------------------------------------------------
 
-[[Velocity-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
 
 In this sample we want to use Velocity templating for an order
 confirmation email. The email template is laid out in Velocity as:
@@ -265,12 +249,9 @@ ${body}
 
 And the java code:
 
-[[Velocity-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-vertx/src/main/docs/vertx-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-vertx/src/main/docs/vertx-component.adoc b/components/camel-vertx/src/main/docs/vertx-component.adoc
index faba01d..2dd007d 100644
--- a/components/camel-vertx/src/main/docs/vertx-component.adoc
+++ b/components/camel-vertx/src/main/docs/vertx-component.adoc
@@ -1,4 +1,4 @@
-# Vert.x Component
+## Vert.x Component
 
 *Available as of Camel 2.12*
 
@@ -24,18 +24,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Vertx-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------
 vertx:channelName[?options]
 ---------------------------
 
-[[Vertx-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -86,9 +82,7 @@ point when sending to a vertx endpoint.
 You can append query options to the URI in the following format, ?option=value&option=value&...
 -----------------------------------------------------------------------------------------------
 
-[[Vertx-ConnectingtotheexistingVert.xinstance]]
-Connecting to the existing Vert.x instance
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Connecting to the existing Vert.x instance
 
 If you would like to connect to the Vert.x instance already existing in
 your JVM, you can set the instance on the component level:
@@ -101,12 +95,9 @@ vertxComponent.setVertx(vertx);
 camelContext.addComponent("vertx", vertxComponent);
 -----------------------------------------------------
 
-[[Vertx-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-weather/src/main/docs/weather-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-weather/src/main/docs/weather-component.adoc b/components/camel-weather/src/main/docs/weather-component.adoc
index f4f1915..f0de088 100644
--- a/components/camel-weather/src/main/docs/weather-component.adoc
+++ b/components/camel-weather/src/main/docs/weather-component.adoc
@@ -1,4 +1,4 @@
-# Weather Component
+## Weather Component
 
 *Available as of Camel 2.12*
 
@@ -24,26 +24,20 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Weather-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------
 weather://<unused name>[?options]
 ---------------------------------
 
-[[Weather-REMARK]]
-REMARK
-^^^^^^
+### REMARK
 
 Since the 9th of October, an Api Key is required to access the
 openweather service. This key is passed as parameter to the URI
 definition of the weather endpoint using the appid param !
 
-[[Weather-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -111,16 +105,12 @@ The Weather component supports 44 endpoint options which are listed below:
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Weather-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
 
 Camel will deliver the body as a json formatted java.lang.String (see
 the `mode` option above).
 
-[[Weather-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -132,9 +122,7 @@ Message Headers
 location from this header instead.
 |=======================================================================
 
-[[Weather-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 In this sample we find the 7 day weather forecast for Madrid, Spain:
 
@@ -172,4 +160,4 @@ And to get the weather at the current location, then:
 [source,java]
 --------------------------------------------------------------------------------------------------------------------------------
   String json = template.requestBodyAndHeader("direct:start", "", "CamelWeatherLocation", "current&appid=APIKEY", String.class);
---------------------------------------------------------------------------------------------------------------------------------
+--------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-websocket/src/main/docs/websocket-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-websocket/src/main/docs/websocket-component.adoc b/components/camel-websocket/src/main/docs/websocket-component.adoc
index aaf0c24..e6943df 100644
--- a/components/camel-websocket/src/main/docs/websocket-component.adoc
+++ b/components/camel-websocket/src/main/docs/websocket-component.adoc
@@ -1,4 +1,4 @@
-# Jetty Websocket Component
+## Jetty Websocket Component
 
 *Available as of Camel 2.10*
 
@@ -14,9 +14,7 @@ protocol, the SSLContextParameters must be defined.
 
 Camel 2.18 uses Jetty 9
 
-[[Websocket-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------------------
@@ -26,9 +24,7 @@ websocket://hostname[:port][/resourceUri][?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Websocket-Options]]
-Websocket Options
-^^^^^^^^^^^^^^^^^
+### Websocket Options
 
 
 
@@ -105,9 +101,7 @@ The Jetty Websocket component supports 21 endpoint options which are listed belo
 
 Â 
 
-[[Websocket-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The websocket component uses 2 headers to indicate to either send
 messages back to a single/current client, or to all clients.
@@ -121,9 +115,7 @@ use the `sendToAll` option on the endpoint instead of using this header.
 |`WebsocketConstants.CONNECTION_KEY` |Sends the message to the client with the given connection key.
 |=======================================================================
 
-[[Websocket-Usage]]
-Usage
-^^^^^
+### Usage
 
 In this example we let Camel exposes a websocket server which clients
 can communicate with. The websocket server uses the default host and
@@ -150,13 +142,9 @@ from("activemq:topic:newsTopic")
    .to("websocket://localhost:8443/newsTopic?sendToAll=true&staticResources=classpath:webapp");
 -----------------------------------------------------------------------------------------------
 
-[[Websocket-SettingupSSLforWebSocketComponent]]
-Setting up SSL for WebSocket Component
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting up SSL for WebSocket Component
 
-[[Websocket-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
 
 As of Camel 2.10, the WebSocket component supports SSL/TLS configuration
 through the link:camel-configuration-utilities.html[Camel JSSE
@@ -234,9 +222,7 @@ Java DSL based configuration of endpoint
 ...
 ----------------------------------------------------------------------------------------------------------
 
-[[Websocket-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -247,5 +233,4 @@ See Also
 * link:jetty.html[Jetty]
 * link:twitter-websocket-example.html[Twitter Websocket Example]
 demonstrates how to poll a constant feed of twitter searches and publish
-results in real time using web socket to a web page.
-
+results in real time using web socket to a web page.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc b/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
index ba593b6..b0a4a2e 100644
--- a/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
+++ b/components/camel-xmlbeans/src/main/docs/xmlBeans-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML Beans DataFormat
+## XML Beans DataFormat
 
 XmlBeans is a link:data-format.html[Data Format] which uses the
 http://xmlbeans.apache.org/[XmlBeans library] to unmarshal an XML
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[XmlBeans-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The XML Beans dataformat supports 2 options which are listed below.
@@ -31,9 +29,7 @@ The XML Beans dataformat supports 2 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[XmlBeans-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use XmlBeans in your camel routes you need to add the dependency on
 *camel-xmlbeans* which implements this data format.
@@ -50,4 +46,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc b/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
index 472cc2e..4f9e86a 100644
--- a/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
+++ b/components/camel-xmljson/src/main/docs/xmljson-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML JSon DataFormat
+## XML JSon DataFormat
 
 *Available as of Camel 2.10*
 
@@ -17,9 +17,7 @@ semantics are assigned as follows:
 * marshalling => converting from XML to JSON
 * unmarshalling => converting from JSON to XML.
 
-[[XmlJson-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The XML JSon dataformat supports 13 options which are listed below.
@@ -47,13 +45,9 @@ The XML JSon dataformat supports 13 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[XmlJson-BasicUsagewithJavaDSL]]
-Basic Usage with Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Basic Usage with Java DSL
 
-[[XmlJson-Explicitlyinstantiatingthedataformat]]
-Explicitly instantiating the data format
-++++++++++++++++++++++++++++++++++++++++
+#### Explicitly instantiating the data format
 
 Just instantiate the `XmlJsonDataFormat` from package
 `org.apache.camel.dataformat.xmljson`. Make sure you have installed the
@@ -92,9 +86,7 @@ from("direct:marshal").marshal(xmlJsonFormat).to("mock:json");
 from("direct:unmarshal").unmarshal(xmlJsonFormat).to("mock:xml");
 ----
 
-[[XmlJson-Definingthedataformatin-line]]
-Defining the data format in-line
-++++++++++++++++++++++++++++++++
+#### Defining the data format in-line
 
 Alternatively, you can define the data format inline by using the
 `xmljson()` DSL element:
@@ -125,9 +117,7 @@ from("direct:marshalInlineOptions").marshal().xmljson(xmlJsonOptions).to("mock:j
 from("direct:unmarshalInlineOptions").unmarshal().xmljson(xmlJsonOptions).to("mock:xmlInlineOptions");
 ----
 
-[[XmlJson-BasicusagewithSpringorBlueprintDSL]]
-Basic usage with Spring or Blueprint DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Basic usage with Spring or Blueprint DSL
 
 Within the `<dataFormats>` block, simply configure an `xmljson` element
 with unique IDs:
@@ -172,9 +162,7 @@ The syntax with link:using-osgi-blueprint-with-camel.html[Blueprint] is
 identical to that of the Spring DSL. Just ensure the correct namespaces
 and schemaLocations are in use.
 
-[[XmlJson-Namespacemappings]]
-Namespace mappings
-^^^^^^^^^^^^^^^^^^
+### Namespace mappings
 
 XML has namespaces to fully qualify elements and attributes; JSON
 doesn't. You need to take this into account when performing XML-JSON
@@ -231,9 +219,7 @@ namespacesFormat.setRootElement("person");
 
 And you can achieve the same in Spring DSL.
 
-[[XmlJson-Example]]
-Example
-+++++++
+#### Example
 
 Using the namespace bindings in the Java snippet above on the following
 JSON string:
@@ -265,9 +251,7 @@ _________________________________________________________
 
 That's why the elements are in a different order in the output XML.
 
-[[XmlJson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use the link:xmljson.html[XmlJson] dataformat in your camel routes
 you need to add the following dependency to your pom:
@@ -290,9 +274,7 @@ license with ASF; so add this manually -->
 </dependency>
 ----
 
-[[XmlJson-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:data-format.html[Data Format]
-* http://json-lib.sourceforge.net/[json-lib]
+* http://json-lib.sourceforge.net/[json-lib]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc b/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
index f4942c4..293d0eb 100644
--- a/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
+++ b/components/camel-xmlrpc/src/main/docs/xmlrpc-component.adoc
@@ -1,4 +1,4 @@
-# XML RPC Component
+## XML RPC Component
 
 *Available as of Camel 2.11*
 
@@ -20,9 +20,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[XmlRpc-XmlRpcOverview]]
-XmlRpc Overview
-^^^^^^^^^^^^^^^
+### XmlRpc Overview
 
 It's a http://xmlrpc.scripting.com/spec[spec] and a set of
 implementations that allow software running on disparate operating
@@ -86,18 +84,14 @@ A typical XML-RPC fault would be:
 </methodResponse>
 --------------------------------------------------------------
 
-[[XmlRpc-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------
 xmlrpc://serverUri[?options]
 ----------------------------
 
-[[XmlRpc-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -137,9 +131,7 @@ The XML RPC component supports 19 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[XmlRpc-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel XmlRpc uses these headers.
 
@@ -150,17 +142,13 @@ Camel XmlRpc uses these headers.
 |`CamelXmlRpcMethodName` |The XmlRpc method name which will be use for invoking the XmlRpc server.
 |=======================================================================
 
-[[XmlRpc-UsingtheXmlRpcdataformat]]
-Using the XmlRpc data format
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the XmlRpc data format
 
 As the XmlRpc message could be request or response, when you use the
 XmlRpcDataFormat, you need to specify the dataformat is for request or
 not.
 
-[[XmlRpc-InvokeXmlRpcServicefromClient]]
-Invoke XmlRpc Service from Client
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Invoke XmlRpc Service from Client
 
 To invoke the XmlRpc service, you need to specify the methodName on the
 message header and put the parameters into the message body like below
@@ -173,12 +161,10 @@ XmlRpcException.
    String response = template.requestBodyAndHeader(xmlRpcServiceAddress, new Object[]{"me"}, XmlRpcConstants.METHOD_NAME, "hello", String.class);
 -------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[XmlRpc-HowtoconfiguretheXmlRpcClientwithJavacode]]
-How to configure the XmlRpcClient with Java code
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to configure the XmlRpcClient with Java code
 
 camel-xmlrpc provides a pluggable strategy for configuring the
 XmlRpcClient used by the component, user just to implement the
 *XmlRpcClientConfigurer* interface and can configure the XmlRpcClient as
 he wants. The clientConfigure instance reference can be set through the
-uri option clientConfigure.
+uri option clientConfigure.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc b/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
index 4afb7ea..112fffa 100644
--- a/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
+++ b/components/camel-xmlrpc/src/main/docs/xmlrpc-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML RPC DataFormat
+## XML RPC DataFormat
 
 As the XmlRpc message could be request or response, when you use the
 XmlRpcDataFormat, you need to specify the dataformat is for request or
@@ -34,9 +34,7 @@ not.
 </camelContext>
 -------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[XmlRpc-Dataformat-Options]]
-XmlRpc Dataformat Options
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### XmlRpc Dataformat Options
 
 // dataformat options: START
 The XML RPC dataformat supports 2 options which are listed below.
@@ -51,6 +49,4 @@ The XML RPC dataformat supports 2 options which are listed below.
 | contentTypeHeader | false | Boolean | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML or application/json for data formats marshalling to JSon etc.
 |=======================================================================
 {% endraw %}
-// dataformat options: END
-
-
+// dataformat options: END
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
index 656e607..7402627 100644
--- a/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/secureXML-dataformat.adoc
@@ -1,4 +1,4 @@
-# XML Security DataFormat
+## XML Security DataFormat
 
 The XMLSecurity Data Format facilitates encryption and decryption of XML
 payloads at the Document, Element, and Element Content levels (including
@@ -33,9 +33,7 @@ configuration. This enables true namespace matching, even if the prefix
 values in the XPath query and the target xml document are not equivalent
 strings.
 
-[[XMLSecurityDataFormat-Options]]
-XMLSecurity Options
-^^^^^^^^^^^^^^^^^^^
+### XMLSecurity Options
 
 // dataformat options: START
 The XML Security dataformat supports 12 options which are listed below.
@@ -63,9 +61,7 @@ The XML Security dataformat supports 12 options which are listed below.
 // dataformat options: END
 
 
-[[XMLSecurityDataFormat-KeyCipherAlgorithm]]
-Key Cipher Algorithm
-++++++++++++++++++++
+#### Key Cipher Algorithm
 
 As of Camel 2.12.0, the default Key Cipher Algorithm is now
 XMLCipher.RSA_OAEP instead of XMLCipher.RSA_v1dot5. Usage of
@@ -73,30 +69,22 @@ XMLCipher.RSA_v1dot5 is discouraged due to various attacks. Requests
 that use RSA v1.5 as the key cipher algorithm will be rejected unless it
 has been explicitly configured as the key cipher algorithm.
 
-[[XMLSecurityDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
 
 In order to encrypt the payload, the `marshal` processor needs to be
 applied on the route followed by the *`secureXML()`* tag.
 
-[[XMLSecurityDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
 
 In order to decrypt the payload, the `unmarshal` processor needs to be
 applied on the route followed by the *`secureXML()`* tag.
 
-[[XMLSecurityDataFormat-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 Given below are several examples of how marshalling could be performed
 at the Document, Element, and Content levels.
 
-[[XMLSecurityDataFormat-FullPayloadencryptiondecryption]]
-Full Payload encryption/decryption
-++++++++++++++++++++++++++++++++++
+#### Full Payload encryption/decryption
 
 [source,java]
 ----------------------------
@@ -106,9 +94,7 @@ from("direct:start")
     .to("direct:end");
 ----------------------------
 
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryption]]
-Partial Payload Content Only encryption/decryption
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption
 
 [source,java]
 ------------------------------------------------------
@@ -121,9 +107,7 @@ from("direct:start")
     .to("direct:end");
 ------------------------------------------------------
 
-[[XMLSecurityDataFormat-PartialMultiNodePayloadContentOnlyencryptiondecryption]]
-Partial Multi Node Payload Content Only encryption/decryption
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Multi Node Payload Content Only encryption/decryption
 
 [source,java]
 ------------------------------------------------------
@@ -136,9 +120,7 @@ from("direct:start")
     .to("direct:end");
 ------------------------------------------------------
 
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryptionwithchoiceofpassPhrasepassword]]
-Partial Payload Content Only encryption/decryption with choice of passPhrase(password)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption with choice of passPhrase(password)
 
 [source,java]
 ------------------------------------------------------------------
@@ -152,9 +134,7 @@ from("direct:start")
     .to("direct:end");
 ------------------------------------------------------------------
 
-[[XMLSecurityDataFormat-PartialPayloadContentOnlyencryptiondecryptionwithpassPhrasepasswordandAlgorithm]]
-Partial Payload Content Only encryption/decryption with passPhrase(password) and Algorithm
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content Only encryption/decryption with passPhrase(password) and Algorithm
 
 [source,java]
 -----------------------------------------------------------------------------
@@ -170,9 +150,7 @@ from("direct:start")
     .to("direct:end");
 -----------------------------------------------------------------------------
 
-[[XMLSecurityDataFormat-PartialPayloadContentwithNamespacesupport]]
-Partial Payload Content with Namespace support
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Partial Payload Content with Namespace support
 
 [[XMLSecurityDataFormat-JavaDSL]]
 Java DSL
@@ -217,9 +195,7 @@ attribute of the `secureXML` element.
             ...
 ---------------------------------------------------------------------------------
 
-[[XMLSecurityDataFormat-AsymmetricKeyEncryption]]
-Asymmetric Key Encryption
-+++++++++++++++++++++++++
+#### Asymmetric Key Encryption
 
 [[XMLSecurityDataFormat-SpringXMLSender]]
 Spring XML Sender
@@ -271,8 +247,6 @@ Spring XML Recipient
             ...
 ----------------------------------------------------------------------------------------------
 
-[[XMLSecurityDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
-This data format is provided within the *camel-xmlsecurity* component.
+This data format is provided within the *camel-xmlsecurity* component.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
index c4f7758..ec5a794 100644
--- a/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
+++ b/components/camel-xmlsecurity/src/main/docs/xmlsecurity-component.adoc
@@ -1,4 +1,4 @@
-# XML Security Component
+## XML Security Component
 
 *Available as of Camel 2.12.0*
 
@@ -37,9 +37,7 @@ for this component:
 </dependency>
 ----
 
-[[XMLSecuritycomponent-XMLSignatureWrappingModes]]
-XML Signature Wrapping Modes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XML Signature Wrapping Modes
 
 XML Signature differs between enveloped, enveloping, and detached XML
 signature. In the
@@ -146,9 +144,7 @@ Elements):
 
 Â 
 
-[[XMLSecuritycomponent-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 The camel component consists of two endpoints which have the following
 URI format:
@@ -171,9 +167,7 @@ signature and set to the body of the out-message.
 * The `name` part in the URI can be chosen by the user to distinguish
 between different signer/verifier endpoints within the camel context.
 
-[[XMLSecuritycomponent-BasicExample]]
-Basic Example
-^^^^^^^^^^^^^
+### Basic Example
 
 The following example shows the basic usage of the component.
 
@@ -224,9 +218,7 @@ the parent element of the Signature element; see option
 For creating _detached_ XML signatures, see sub-chapter "Detached XML
 Signatures as Siblings of the Signed Elements".
 
-[[XMLSecuritycomponent-ComponentOptions]]
-Component Options
-^^^^^^^^^^^^^^^^
+### Component Options
 
 
 
@@ -252,9 +244,7 @@ The XML Security component supports 2 options which are listed below.
 
 
 
-[[XMLSecuritycomponent-EndpointOptions]]
-Endpoint Options
-^^^^^^^^^^^^^^^^
+### Endpoint Options
 
 
 // endpoint options: START
@@ -307,9 +297,7 @@ The XML Security component supports 37 endpoint options which are listed below:
 
 
 
-[[XMLSecuritycomponent-OutputNodeDeterminationinEnvelopingXMLSignatureCase]]
-Output Node Determination in Enveloping XML Signature Case
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Output Node Determination in Enveloping XML Signature Case
 
 After the validation the node is extracted from the XML signature
 document which is finally returned to the output-message body. In the
@@ -377,9 +365,7 @@ or the structure:
 </Signature>
 ----
 
-[[XMLSecuritycomponent-DetachedXMLSignaturesasSiblingsoftheSignedElements]]
-Detached XML Signatures as Siblings of the Signed Elements
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Detached XML Signatures as Siblings of the Signed Elements
 
 **Since 2.14.0**
 
@@ -483,9 +469,7 @@ from("direct:detached")
 ----
 
 
-[[XMLSecuritycomponent-XAdES-BESEPESfortheSignerEndpoint]]
-XAdES-BES/EPES for the Signer Endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XAdES-BES/EPES for the Signer Endpoint
 
 *Available as of Camel 2.15.0* 
 
@@ -660,9 +644,7 @@ from("direct:xades").to("xmlsecurity:sign://xades?keyAccessor=#keyAccessorDefaul
 </bean>
 ----
 
-[[XMLSecuritycomponent-Headers]]
-Headers
-+++++++
+#### Headers
 
 [width="100%",cols="1m,1m,4",options="header",]
 |=======================================================================
@@ -686,9 +668,7 @@ namespace parameter value
 parameter value
 |=======================================================================
 
-[[XMLSecuritycomponent-LimitationswithregardtoXAdESversion1.4.2]]
-Limitations with regard to XAdES version 1.4.2
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Limitations with regard to XAdES version 1.4.2
 
 * No support for signature form XAdES-T and XAdES-C
 * Only signer part implemented. Verifier part currently not available.
@@ -713,8 +693,6 @@ the XML signer endpoint).
 * The `AllDataObjectsTimeStamp` element is not supported
 * The `IndividualDataObjectsTimeStamp` element is not supported
 
-[[XMLSecuritycomponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
-* http://www.w3.org/TR/xmldsig-bestpractices/[Best Practices]
+* http://www.w3.org/TR/xmldsig-bestpractices/[Best Practices]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xmpp/src/main/docs/xmpp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xmpp/src/main/docs/xmpp-component.adoc b/components/camel-xmpp/src/main/docs/xmpp-component.adoc
index f9f263b..f9e3139 100644
--- a/components/camel-xmpp/src/main/docs/xmpp-component.adoc
+++ b/components/camel-xmpp/src/main/docs/xmpp-component.adoc
@@ -1,4 +1,4 @@
-# XMPP Component
+## XMPP Component
 
 The *xmpp:* component implements an XMPP (Jabber) transport.
 
@@ -15,9 +15,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[XMPP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,text]
 ------------------------------------------------------
@@ -33,9 +31,7 @@ starting.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[XMPP-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -77,9 +73,7 @@ The XMPP component supports 21 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[XMPP-HeadersandsettingSubjectorLanguage]]
-Headers and setting Subject or Language
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Headers and setting Subject or Language
 
 Camel sets the message IN headers as properties on the XMPP message. You
 can configure a `HeaderFilterStategy` if you need custom filtering of
@@ -87,9 +81,7 @@ headers.
 The *Subject* and *Language* of the XMPP message are also set if they
 are provided as IN headers.
 
-[[XMPP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 User `superman` to join room `krypton` at `jabber` server with password,
 `secret`:
@@ -152,12 +144,9 @@ from("direct:start").
 
 Â 
 
-[[XMPP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc b/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
index 5045fbd..2215f6f 100644
--- a/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
+++ b/components/camel-xstream/src/main/docs/json-xstream-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon XStream DataFormat
+## JSon XStream DataFormat
 
 XStream is a link:data-format.html[Data Format] which uses the
 http://xstream.codehaus.org/[XStream library] to marshal and unmarshal
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their
 </dependency>
 ----------------------------------------------------------
 
-[[XStream-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The JSon XStream dataformat supports 17 options which are listed below.
@@ -55,9 +53,7 @@ The JSon XStream dataformat supports 17 options which are listed below.
 // dataformat options: END
 
 
-[[XStream-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
 
 [source,java]
 -----------------------------------------------------------
@@ -84,9 +80,7 @@ from("direct:marshal").
   to("mock:marshaled");
 ---------------------------------------------------------
 
-[[XStream-XMLInputFactoryandXMLOutputFactory]]
-XMLInputFactory and XMLOutputFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XMLInputFactory and XMLOutputFactory
 
 http://xstream.codehaus.org/[The XStream library] uses the
 `javax.xml.stream.XMLInputFactory` and
@@ -104,9 +98,7 @@ looking in the `META-INF/services/javax.xml.stream.XMLInputFactory`,
 available to the JRE.
  4. Use the platform default XMLInputFactory,XMLOutputFactory instance.
 
-[[XStream-HowtosettheXMLencodinginXstreamDataFormat]]
-How to set the XML encoding in Xstream DataFormat?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the XML encoding in Xstream DataFormat?
 
 From Camel 2.2.0, you can set the encoding of XML in Xstream DataFormat
 by setting the Exchange's property with the key `Exchange.CHARSET_NAME`,
@@ -119,9 +111,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[XStream-SettingthetypepermissionsofXstreamDataFormat]]
-Setting the type permissions of Xstream DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting the type permissions of Xstream DataFormat
 
 In Camel, one can always use its own processing step in the route to
 filter and block certain XML documents to be routed to the XStream's
@@ -154,4 +144,4 @@ DataFormat instance by setting its type permissions property.
                  permissions="org.apache.camel.samples.xstream.*"/>
         ...
 
--------------------------------------------------------------------
+-------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-xstream/src/main/docs/xstream-dataformat.adoc b/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
index 13e84ce..ccb948f 100644
--- a/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
+++ b/components/camel-xstream/src/main/docs/xstream-dataformat.adoc
@@ -1,4 +1,4 @@
-# XStream DataFormat
+## XStream DataFormat
 
 XStream is a link:data-format.html[Data Format] which uses the
 http://xstream.codehaus.org/[XStream library] to marshal and unmarshal
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their
 </dependency>
 ----------------------------------------------------------
 
-[[XStream-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The XStream dataformat supports 10 options which are listed below.
@@ -48,9 +46,7 @@ The XStream dataformat supports 10 options which are listed below.
 // dataformat options: END
 
 
-[[XStream-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
 
 [source,java]
 -----------------------------------------------------------
@@ -77,9 +73,7 @@ from("direct:marshal").
   to("mock:marshaled");
 ---------------------------------------------------------
 
-[[XStream-XMLInputFactoryandXMLOutputFactory]]
-XMLInputFactory and XMLOutputFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### XMLInputFactory and XMLOutputFactory
 
 http://xstream.codehaus.org/[The XStream library] uses the
 `javax.xml.stream.XMLInputFactory` and
@@ -97,9 +91,7 @@ looking in the `META-INF/services/javax.xml.stream.XMLInputFactory`,
 available to the JRE.
  4. Use the platform default XMLInputFactory,XMLOutputFactory instance.
 
-[[XStream-HowtosettheXMLencodinginXstreamDataFormat]]
-How to set the XML encoding in Xstream DataFormat?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the XML encoding in Xstream DataFormat?
 
 From Camel 2.2.0, you can set the encoding of XML in Xstream DataFormat
 by setting the Exchange's property with the key `Exchange.CHARSET_NAME`,
@@ -112,9 +104,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[XStream-SettingthetypepermissionsofXstreamDataFormat]]
-Setting the type permissions of Xstream DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting the type permissions of Xstream DataFormat
 
 In Camel, one can always use its own processing step in the route to
 filter and block certain XML documents to be routed to the XStream's
@@ -147,4 +137,4 @@ DataFormat instance by setting its type permissions property.
                  permissions="org.apache.camel.samples.xstream.*"/>
         ...
 
--------------------------------------------------------------------
+-------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-yammer/src/main/docs/yammer-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-yammer/src/main/docs/yammer-component.adoc b/components/camel-yammer/src/main/docs/yammer-component.adoc
index 946ebbe..122c3cb 100644
--- a/components/camel-yammer/src/main/docs/yammer-component.adoc
+++ b/components/camel-yammer/src/main/docs/yammer-component.adoc
@@ -1,4 +1,4 @@
-# Yammer Component
+## Yammer Component
 
 *Available as of Camel 2.12*
 
@@ -25,18 +25,14 @@ for this component:
 </dependency>
 ----
 
-[[Yammer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
 yammer:[function]?[options]
 ----
 
-[[Yammer-ComponentOptions]]
-Component options
-^^^^^^^^^^^^^^^^^
+### Component options
 
 The Yammer component can be configured with the Yammer account settings
 which are mandatory to configure before using.
@@ -66,9 +62,7 @@ The Yammer component supports 4 options which are listed below.
 
 You can also configure these options directly in the endpoint.
 
-[[Yammer-EndpointOptions]]
-Endpoint options
-^^^^^^^^^^^^^^^^^
+### Endpoint options
 
 
 
@@ -115,9 +109,7 @@ The Yammer component supports 29 endpoint options which are listed below:
 
 
 
-[[Yammer-Consumingmessages]]
-Consuming messages
-^^^^^^^^^^^^^^^^^^
+### Consuming messages
 
 The Yammer component provides several endpoints for consuming
 messages:
@@ -148,9 +140,7 @@ and topics that the user is following.
 |=======================================================================
 
 
-[[Yammer-Messageformat]]
-Message format
-++++++++++++++
+#### Message format
 
 All messages by default are converted to a POJO model provided in the
 `org.apache.camel.component.yammer.model` package. The original message
@@ -259,9 +249,7 @@ That said, marshaling this data into POJOs is not free so if you need
 you can switch back to using pure JSON by adding the `useJson=false`
 option to your URI.
 
-[[Yammer-Creatingmessages]]
-Creating messages
-^^^^^^^^^^^^^^^^^
+### Creating messages
 
 To create a new message in the account of the current user, you can use
 the following URI:
@@ -306,9 +294,7 @@ assertEquals(1, messages.getMessages().size());
 assertEquals("Hi from Camel!", messages.getMessages().get(0).getBody().getPlain());
 ----
 
-[[Yammer-Retrievinguserrelationships]]
-Retrieving user relationships
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Retrieving user relationships
 
 The Yammer component can retrieve user relationships:
 
@@ -318,9 +304,7 @@ yammer:relationships?[options]
 ----
 
 
-[[Yammer-Retrievingusers]]
-Retrieving users
-^^^^^^^^^^^^^^^^
+### Retrieving users
 
 The Yammer component provides several endpoints for retrieving
 users:
@@ -335,9 +319,7 @@ users:
 |=====================================================
 
 
-[[Yammer-Usinganenricher]]
-Using an enricher
-^^^^^^^^^^^^^^^^^
+### Using an enricher
 
 It is helpful sometimes (or maybe always in the case of users or
 relationship consumers) to use an enricher pattern rather than a route
@@ -361,11 +343,9 @@ from("direct:start")
 This will go out and fetch the current user's `User` object and set it as
 the Camel message body.
 
-[[Yammer-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc b/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
index 91e2a76..dc3660d 100644
--- a/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
+++ b/components/camel-zipfile/src/main/docs/zipfile-dataformat.adoc
@@ -1,4 +1,4 @@
-# Zip File DataFormat
+## Zip File DataFormat
 
 TIP:*Available since Camel 2.11.0*
 
@@ -13,9 +13,7 @@ https://blogs.oracle.com/xuemingshen/entry/zip64_support_for_4g_zipfile[Java
 Since Camel 2.12.3 there is also a aggregation strategy that can
 aggregate multiple messages into a single Zip file.
 
-[[ZipFile-Options]]
-ZipFile Options
-^^^^^^^^^^^^^^^
+### ZipFile Options
 
 
 // dataformat options: START
@@ -35,9 +33,7 @@ The Zip File dataformat supports 2 options which are listed below.
 
 
 
-[[ZipFileDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
 
 In this example we marshal a regular text/XML payload to a compressed
 payload using Zip file compression, and send it to an ActiveMQ queue
@@ -78,9 +74,7 @@ from("direct:start").setHeader(Exchange.FILE_NAME, constant("report.txt")).marsh
 This route would result in a Zip file named "report.txt.zip" in the
 output directory, containing a single Zip entry named "report.txt".
 
-[[ZipFileDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
 
 In this example we unmarshal a Zip file payload from an ActiveMQ queue
 called MY_QUEUE to its original format, and forward it for processing to
@@ -119,9 +113,7 @@ like this
      .end();
 ----------------------------------------------------------------------------------------------------
 
-[[ZipFileDataFormat-Aggregate]]
-Aggregate
-^^^^^^^^^
+### Aggregate
 
 TIP:*Available since Camel 2.12.3*
 
@@ -157,9 +149,7 @@ the `CamelFileName` header explicitly in your route:
    .to("file:output/directory");
 ------------------------------------------------------------
 
-[[ZipFileDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Zip files in your camel routes you need to add a dependency on
 *camel-zipfile* which implements this data format.
@@ -176,4 +166,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc b/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
index b139627..fd0ce0f 100644
--- a/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
+++ b/components/camel-zookeeper/src/main/docs/zookeeper-component.adoc
@@ -1,4 +1,4 @@
-# ZooKeeper Component
+## ZooKeeper Component
 
 *Available as of Camel 2.9*
 
@@ -28,9 +28,7 @@ for this component:
 </dependency>
 ----
 
-[[Zookeeper-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
@@ -40,9 +38,7 @@ zookeeper://zookeeper-server[:port][/path][?options]
 The path from the URI specifies the node in the ZooKeeper server (a.k.a.
 _znode_) that will be the target of the endpoint:
 
-[[Zookeeper-Options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The ZooKeeper component supports 1 options which are listed below.
@@ -84,13 +80,9 @@ The ZooKeeper component supports 14 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Zookeeper-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
 
-[[Zookeeper-Readingfromaznode]]
-Reading from a _znode_
-+++++++++++++++++++++
+#### Reading from a _znode_
 
 The following snippet will read the data from the _znode_
 `/somepath/somenode/` provided that it already exists. The data
@@ -110,9 +102,7 @@ endpoint await its creation:
 from("zookeeper://localhost:39913/somepath/somenode?awaitCreation=true").to("mock:result");
 ----
 
-[[Zookeeper-ReadingfromaznodeAdditionalCamel210onwards]]
-Reading from a _znode_ (additional Camel 2.10 onwards)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reading from a _znode_ (additional Camel 2.10 onwards)
 
 When data is read due to a `WatchedEvent` received from the ZooKeeper
 ensemble, the `CamelZookeeperEventType` header holds ZooKeeper's
@@ -121,9 +111,7 @@ value from that `WatchedEvent`. If the data is read initially (not
 triggered by a `WatchedEvent`) the `CamelZookeeperEventType` header will not
 be set.
 
-[[Zookeeper-Writingtoaznode]]
-Writing to a _znode_
-++++++++++++++++++++
+#### Writing to a _znode_
 
 The following snippet will write the payload of the exchange into the
 znode at `/somepath/somenode/` provided that it already exists:
@@ -216,9 +204,7 @@ Object testPayload = ...
 template.sendBodyAndHeader("direct:create-and-write-to-persistent-znode", testPayload, "CamelZooKeeperCreateMode", "PERSISTENT");
 ----
 
-[[Zookeeper-ZooKeeperenabledRoutepolicy]]
-ZooKeeper enabled Route policies
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### ZooKeeper enabled Route policies
 
 ZooKeeper allows for very simple and effective leader election out of
 the box. This component exploits this election capability in a
@@ -276,11 +262,9 @@ There are currently 3 policies defined in the component, with different SLAs:
  thus you can be sure that no even is processed before the Policy takes its decision.
 
 
-[[Zookeeper-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
+* link:getting-started.html[Getting Started]
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[03/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-slack/src/main/docs/slack-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-slack/src/main/docs/slack-component.adoc b/components/camel-slack/src/main/docs/slack-component.adoc
index 9e0a5bc..6b41a65 100644
--- a/components/camel-slack/src/main/docs/slack-component.adoc
+++ b/components/camel-slack/src/main/docs/slack-component.adoc
@@ -1,4 +1,4 @@
-# Slack Component
+## Slack Component
 
 *Available as of Camel 2.16*
 
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Slack-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 To send a message to a channel.
 
@@ -39,9 +37,7 @@ To send a direct message to a slackuser.
 slack:@username[?options]
 -------------------------
 
-[[Slack-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -80,9 +76,7 @@ The Slack component supports 6 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Slack-SlackComponent.1]]
-SlackComponent
-^^^^^^^^^^^^^^
+### SlackComponent
 
 The SlackComponent with XML must be configured as a Spring or Blueprint
 bean that contains the incoming webhook url for the integration as a
@@ -97,9 +91,7 @@ parameter.
 
 For Java you can configure this using Java code.
 
-[[Slack-Example]]
-Example
-^^^^^^^
+### Example
 
 A CamelContext with Blueprint could be as:
 
@@ -122,12 +114,9 @@ A CamelContext with Blueprint could be as:
 </blueprint>
 ---------------------------------------------------------------------------------------------------------------------------
 
-[[Slack-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-smpp/src/main/docs/smpp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-smpp/src/main/docs/smpp-component.adoc b/components/camel-smpp/src/main/docs/smpp-component.adoc
index 8db80ec..c83cf21 100644
--- a/components/camel-smpp/src/main/docs/smpp-component.adoc
+++ b/components/camel-smpp/src/main/docs/smpp-component.adoc
@@ -1,4 +1,4 @@
-# SMPP Component
+## SMPP Component
 
 *CamelSmppFinalStatusAvailable as of Camel 2.2*
 
@@ -27,9 +27,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SMPP-SMSlimitations]]
-SMS limitations
-^^^^^^^^^^^^^^^
+### SMS limitations
 
 SMS is neither reliable or secure.  Users who require reliable and
 secure delivery may want to consider using the XMPP or SIP components
@@ -56,9 +54,7 @@ schemes and other purposes where security is important.
 While the Camel component makes it as easy as possible to send messages
 to the SMS network, it can not offer an easy solution to these problems.
 
-[[SMPP-Datacoding,alphabetandinternationalcharactersets]]
-Data coding, alphabet and international character sets
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Data coding, alphabet and international character sets
 
 Data coding and alphabet can be specified on a per-message basis. 
 Default values can be specified for the endpoint.  It is important to
@@ -129,9 +125,7 @@ control panel option]. It is suggested that users check with their SMSC
 operator to confirm exactly which character set is being used as the
 default.
 
-[[SMPP-Messagesplittingandthrottling]]
-Message splitting and throttling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message splitting and throttling
 
 After transforming a message body from a String to a byte array, the
 Camel component is also responsible for splitting the message into parts
@@ -149,9 +143,7 @@ that has been split may be counted separately by the provider's
 throttling mechanism.  The Camel Throttler component can be useful for
 throttling messages in the SMPP route before handing them to the SMSC.
 
-[[SMPP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------------------
@@ -169,9 +161,7 @@ use SSLSocket to init a connection to the server.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SMPP-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 
@@ -255,9 +245,7 @@ You can have as many of these options as you like.
 smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer
 ------------------------------------------------------------------------------------------------------------------
 
-[[SMPP-ProducerMessageHeaders]]
-Producer Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Producer Message Headers
 
 The following message headers can be used to affect the behavior of the
 SMPP producer
@@ -392,9 +380,7 @@ converted in the following way:
 `org.jsmpp.bean.OptionalParameter.Null` -> `null`
 |=======================================================================
 
-[[SMPP-ConsumerMessageHeaders]]
-Consumer Message Headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Consumer Message Headers
 
 The following message headers are used by the SMPP consumer to set the
 request data from the SMSC in the message header
@@ -529,9 +515,7 @@ TIP: *JSMPP library*
 See the documentation of the http://jsmpp.org[JSMPP Library] for more
 details about the underlying library.
 
-[[SMPP-Exceptionhandling]]
-Exception handling
-^^^^^^^^^^^^^^^^^^
+### Exception handling
 
 This component supports the general Camel exception handling
 capabilities
@@ -564,9 +548,7 @@ from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&t
 Please refer to the http://smsforum.net/SMPP_v3_4_Issue1_2.zip[SMPP
 specification] for the complete list of error codes and their meanings.
 
-[[SMPP-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 A route which sends an SMS using the Java DSL:
 
@@ -613,9 +595,7 @@ If you need an SMSC simulator for your test, you can use the simulator
 provided by
 http://opensmpp.logica.com/CommonPart/Download/download2.html#simulator[Logica].
 
-[[SMPP-Debuglogging]]
-Debug logging
-^^^^^^^^^^^^^
+### Debug logging
 
 This component has log level *DEBUG*, which can be helpful in debugging
 problems. If you use log4j, you can add the following line to your
@@ -626,12 +606,9 @@ configuration:
 log4j.logger.org.apache.camel.component.smpp=DEBUG
 --------------------------------------------------
 
-[[SMPP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc b/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
index 10f4289..03d6e98 100644
--- a/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
+++ b/components/camel-snakeyaml/src/main/docs/yaml-snakeyaml-dataformat.adoc
@@ -1,4 +1,4 @@
-# YAML SnakeYAML DataFormat
+## YAML SnakeYAML DataFormat
 
 YAML is a link:data-format.html[Data Format] to marshal and unmarshal
 Java objects to and from http://www.yaml.org/[YAML].
@@ -12,9 +12,7 @@ Every library requires adding the special camel component (see
 "Dependency..." paragraphs further down). By default Camel uses the
 SnakeYAML library.
 
-[[YAML-Options]]
-YAML Options
-^^^^^^^^^^^^
+### YAML Options
 
 // dataformat options: START
 The YAML SnakeYAML dataformat supports 11 options which are listed below.
@@ -42,9 +40,7 @@ The YAML SnakeYAML dataformat supports 11 options which are listed below.
 
 WARNING: SnakeYAML can load any class from YAML definition which may lead to security breach so by default, SnakeYAML DataForma restrict the object it can load to standard Java objects like List or Long. If you want to load custom POJOs you need to add theirs type to SnakeYAML DataFormat type filter list. If your source is trusted, you can set the property allowAnyType to true so SnakeYAML DataForma won't perform any filter on the types.
 
-[[YAMLDataFormat-UsingYAMLdataformatwiththeSnakeYAMLlibrary]]
-Using YAML data format with the SnakeYAML library
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using YAML data format with the SnakeYAML library
 
 - Turn Object messages into yaml then send to MQSeries
 +
@@ -77,9 +73,7 @@ from("activemq:My.Queue")
   .to("mqseries:Another.Queue");
 ------------------------------------------------------------
 
-[[YAMLDataFormat-UsingYAMLinSpringDSL]]
-Using YAML in Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Using YAML in Spring DSL
 
 When using link:data-format.html[Data Format] in Spring DSL you need to
 declare the data formats first. This is done in the *DataFormats* XML
@@ -131,9 +125,7 @@ And then you can refer to those ids in the route:
 -------------------------------------
 
 
-[[YAMLDataFormat-DependenciesforSnakeYAML]]
-Dependencies for SnakeYAML
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Dependencies for SnakeYAML
 
 To use YAML in your camel routes you need to add the a dependency
 on *camel-snakeyaml* which implements this data format.
@@ -153,4 +145,4 @@ substituting the version number for the latest & greatest release
 
 Â 
 
- 
+ 
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-snmp/src/main/docs/snmp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-snmp/src/main/docs/snmp-component.adoc b/components/camel-snmp/src/main/docs/snmp-component.adoc
index 3cd76e0..9c3dad8 100644
--- a/components/camel-snmp/src/main/docs/snmp-component.adoc
+++ b/components/camel-snmp/src/main/docs/snmp-component.adoc
@@ -1,4 +1,4 @@
-# SNMP Component
+## SNMP Component
 
 *Available as of Camel 2.1*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SNMP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------
@@ -33,9 +31,7 @@ and receiving traps.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SNMP-Producer]]
-Snmp Producer
-^^^^^^^^^^^^^
+### Snmp Producer
 
 *Available from 2.18 release*
 
@@ -43,9 +39,7 @@ It can also be used to request information using GET method.
 
 The response body type is org.apache.camel.component.snmp.SnmpMessage
 
-[[SNMP-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -101,9 +95,7 @@ The SNMP component supports 36 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[SNMP-Theresultofapoll]]
-The result of a poll
-^^^^^^^^^^^^^^^^^^^^
+### The result of a poll
 
 Given the situation, that I poll for the following OIDs:
 
@@ -154,9 +146,7 @@ requested....1.3.6.1.2.1.1.1.0. +
 So it may absolutely happen, that you receive more than you
 requested...be prepared.
 
-[[SNMP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 Polling a remote device:
 
@@ -185,12 +175,9 @@ convertBodyTo(String.class).
 to("activemq:snmp.states");
 ------------------------------------------------------------------------------
 
-[[SNMP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
index 70d1d62..3e4aa17 100644
--- a/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
+++ b/components/camel-soap/src/main/docs/soapjaxb-dataformat.adoc
@@ -1,4 +1,4 @@
-# SOAP DataFormat
+## SOAP DataFormat
 
 *Available as of Camel 2.3*
 
@@ -16,9 +16,7 @@ onwards.
 See link:jaxb.html[JAXB] for details how you can control namespace
 prefix mappings when marshalling using link:soap.html[SOAP] data format.
 
-[[SOAP-Options]]
-SOAP Options
-^^^^^^^^^^^^
+### SOAP Options
 
 
 // dataformat options: START
@@ -43,9 +41,7 @@ The SOAP dataformat supports 7 options which are listed below.
 
 
 
-[[SOAP-ElementNameStrategy]]
-ElementNameStrategy
-^^^^^^^^^^^^^^^^^^^
+### ElementNameStrategy
 
 An element name strategy is used for two purposes. The first is to find
 a xml element name for a given object and soap action when marshaling
@@ -72,9 +68,7 @@ similar tool then you probably will want to use the
 ServiceInterfaceStrategy. In the case you have no annotated service
 interface you should use QNameStrategy or TypeNameStrategy.
 
-[[SOAP-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
 
 The following example uses a named DataFormat of _soap_ which is
 configured with the package com.example.customerservice to initialize
@@ -100,9 +94,7 @@ As the SOAP dataformat inherits from the link:jaxb.html[JAXB] dataformat
 most settings apply here as well
 
 
-[[SOAP-UsingSOAP1.2]]
-Using SOAP 1.2
-++++++++++++++
+#### Using SOAP 1.2
 
 *Available as of Camel 2.11*
 
@@ -140,9 +132,7 @@ And in the Camel route
 </route>
 ---------------------------------------------------------------------------------------------------------------
 
-[[SOAP-Multi-partMessages]]
-Multi-part Messages
-^^^^^^^^^^^^^^^^^^^
+### Multi-part Messages
 
 *Available as of Camel 2.8.1*
 
@@ -166,9 +156,7 @@ ServiceInterfaceStrategy strat =  new ServiceInterfaceStrategy(com.example.custo
 SoapJaxbDataFormat soapDataFormat = new SoapJaxbDataFormat("com.example.customerservice.multipart", strat);
 -------------------------------------------------------------------------------------------------------------------------------------------
 
-[[SOAP-Multi-partRequest]]
-Multi-part Request
-++++++++++++++++++
+#### Multi-part Request
 
 The payload parameters for a multi-part request are initiazlied using a
 `BeanInvocation` object that reflects the signature of the target
@@ -201,9 +189,7 @@ beanInvocation.setArgs(args);
 exchange.getIn().setBody(beanInvocation);
 ----------------------------------------------------------------------------------------
 
-[[SOAP-Multi-partResponse]]
-Multi-part Response
-+++++++++++++++++++
+#### Multi-part Response
 
 A multi-part soap response may include an element in the soap body and
 will have one or more elements in the soap header. The camel-soap
@@ -220,9 +206,7 @@ camel-jaxb.
 You can also have the camel-soap DataFormate ignore header content
 all-together by setting the `ignoreUnmarshalledHeaders` value to `true`.
 
-[[SOAP-HolderObjectmapping]]
-Holder Object mapping
-+++++++++++++++++++++
+#### Holder Object mapping
 
 JAX-WS specifies the use of a type-parameterized `javax.xml.ws.Holder`
 object for `In/Out` and `Out` parameters. A `Holder` object may be used
@@ -232,13 +216,9 @@ values in accordance with the JAXB mapping for the class of the
 `Holder`'s value. No mapping is provided for `Holder` objects in an
 unmarshalled response.
 
-[[SOAP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[SOAP-Webserviceclient]]
-Webservice client
-+++++++++++++++++
+#### Webservice client
 
 The following route supports marshalling the request and unmarshalling a
 response or fault.
@@ -273,9 +253,7 @@ CustomerService proxy = ProxyHelper.createProxy(startEndpoint, classLoader, Cust
 GetCustomersByNameResponse response = proxy.getCustomersByName(new GetCustomersByName());
 ---------------------------------------------------------------------------------------------------
 
-[[SOAP-WebserviceServer]]
-Webservice Server
-+++++++++++++++++
+#### Webservice Server
 
 Using the following route sets up a webservice server that listens on
 jms queue customerServiceQueue and processes requests using the class
@@ -297,9 +275,7 @@ from("jms://queue:customerServiceQueue")
   .marshal(soapDF);
 ---------------------------------------------------------------------------------------------------------------------------------------
 
-[[SOAP-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use the SOAP dataformat in your camel routes you need to add the
 following dependency to your pom.
@@ -311,4 +287,4 @@ following dependency to your pom.
   <artifactId>camel-soap</artifactId>
   <version>2.3.0</version>
 </dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-solr/src/main/docs/solr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-solr/src/main/docs/solr-component.adoc b/components/camel-solr/src/main/docs/solr-component.adoc
index ebcf0ce..4c5e957 100644
--- a/components/camel-solr/src/main/docs/solr-component.adoc
+++ b/components/camel-solr/src/main/docs/solr-component.adoc
@@ -1,4 +1,4 @@
-# Solr Component
+## Solr Component
 
 *Available as of Camel 2.9*
 
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Solr-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 *NOTE:* solrs and solrCloud are new added since *Camel 2.14*.
 
@@ -32,9 +30,7 @@ solrs://host[:port]/solr?[options]
 solrCloud://host[:port]/solr?[options]
 --------------------------------------
 
-[[Solr-Options]]
-Solr Options
-^^^^^^^^^^^^
+### Solr Options
 
 
 // component options: START
@@ -69,9 +65,7 @@ The Solr component supports 14 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Solr-MessageOperations]]
-Message Operations
-^^^^^^^^^^^^^^^^^^
+### Message Operations
 
 The following Solr operations are currently supported. Simply set an
 exchange header with a key of "SolrOperation" and a value set to one of
@@ -116,9 +110,7 @@ bean]
 optimize command
 |=======================================================================
 
-[[Solr-Example]]
-Example
-^^^^^^^
+### Example
 
 Below is a simple INSERT, DELETE and COMMIT example
 
@@ -177,9 +169,7 @@ delete routes and then call the commit route.
     template.sendBody("direct:commit", null);
 -----------------------------------------------
 
-[[Solr-QueryingSolr]]
-Querying Solr
-^^^^^^^^^^^^^
+### Querying Solr
 
 Currently, this component doesn't support querying data natively (may be
 added later). For now, you can query Solr using link:http.html[HTTP] as
@@ -203,12 +193,9 @@ Tutorial]
 
 http://wiki.apache.org/solr/SolrQuerySyntax[Solr Query Syntax]
 
-[[Solr-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc b/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
index c09f81c..db249c6 100644
--- a/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
+++ b/components/camel-spark-rest/src/main/docs/spark-rest-component.adoc
@@ -1,4 +1,4 @@
-# Spark Rest Component
+## Spark Rest Component
 
 *Available as of Camel 2.14*
 
@@ -20,18 +20,14 @@ for this component:
     </dependency>
 -------------------------------------------------
 
-[[Spark-rest-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------
   spark-rest://verb:path?[options]
 ----------------------------------
 
-[[Spark-rest-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 
@@ -87,9 +83,7 @@ The Spark Rest component supports 13 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Spark-rest-PathusingSparksyntax]]
-Path using Spark syntax
-^^^^^^^^^^^^^^^^^^^^^^^
+### Path using Spark syntax
 
 The path option is defined using a Spark REST syntax where you define
 the REST context path using support for parameters and splat. See more
@@ -113,9 +107,7 @@ header with the key "me".
     .transform().simple("Bye ${header.me}");
 --------------------------------------------
 
-[[Spark-rest-MappingtoCamelMessage]]
-Mapping to Camel Message
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Mapping to Camel Message
 
 The Spark Request object is mapped to a Camel Message as
 a `org.apache.camel.component.sparkrest.SparkMessage` which has access
@@ -135,9 +127,7 @@ Simple language to construct a response message.
     .transform().simple("Bye big ${header.splat[1]} from ${header.splat[0]}");
 ------------------------------------------------------------------------------
 
-[[Spark-rest-RestDSL]]
-Rest DSL
-^^^^^^^^
+### Rest DSL
 
 Apache Camel provides a new Rest DSL that allow to define the REST
 services in a nice REST style. For example we can define a REST hello
@@ -171,23 +161,18 @@ service as shown below:
 
 See more details at the link:rest-dsl.html[Rest DSL].
 
-[[Spark-rest-Moreexamples]]
-More examples
-^^^^^^^^^^^^^
+### More examples
 
 There is a *camel-example-spark-rest-tomcat* example in the Apache Camel
 distribution, that demonstrates how to use camel-spark-rest in a web
 application that can be deployed on Apache Tomcat, or similar web
 containers.
 
-[[Spark-rest-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:rest.html[Rest]
-
+* link:rest.html[Rest]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spark/src/main/docs/spark-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spark/src/main/docs/spark-component.adoc b/components/camel-spark/src/main/docs/spark-component.adoc
index fc71216..e5cc252 100644
--- a/components/camel-spark/src/main/docs/spark-component.adoc
+++ b/components/camel-spark/src/main/docs/spark-component.adoc
@@ -1,4 +1,4 @@
-# Apache Spark Component
+## Apache Spark Component
 
 INFO: Apache Spark component is available starting from Camel *2.17*.
 
@@ -10,9 +10,7 @@ message from various transports, dynamically choose a task to execute,
 use incoming message as input data for that task and finally deliver the
 results of the execution back to the Camel pipeline.
 
-[[ApacheSpark-Supportedarchitecturalstyles]]
-Supported architectural styles
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supported architectural styles
 
 Spark component can be used as a driver application deployed into an
 application server (or executed as a fat jar).
@@ -28,18 +26,14 @@ While Spark component is primary designed to work as a _long running
 job_ serving as an bridge between Spark cluster and the other endpoints,
 you can also use it as a _fire-once_ short job.   
 
-[[ApacheSpark-RunningSparkinOSGiservers]]
-Running Spark in OSGi servers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Running Spark in OSGi servers
 
 Currently the Spark component doesn't support execution in the OSGi
 container. Spark has been designed to be executed as a fat jar, usually
 submitted as a job to a cluster. For those reasons running Spark in an
 OSGi server is at least challenging and is not support by Camel as well.
 
-[[ApacheSpark-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 Currently the Spark component supports only producers - it it intended
 to invoke a Spark job and return results. You can call RDD, data frame
@@ -52,9 +46,7 @@ or Hive SQL job.
 spark:{rdd|dataframe|hive}
 --------------------------
 
-[[ApacheSpark-options]]
-Spark options
-+++++++++++++
+#### Spark options
 
 
 
@@ -95,9 +87,7 @@ The Apache Spark component supports 7 endpoint options which are listed below:
 // endpoint options: END
 
 Â 
-[[ApacheSpark-RDDjobs]]
-RDD jobs 
-^^^^^^^^^
+### RDD jobs 
 
 To invoke an RDD job, use the following URI:
 
@@ -166,9 +156,7 @@ JavaRDDLike myRdd(JavaSparkContext sparkContext) {
 }
 --------------------------------------------------
 
-[[ApacheSpark-VoidRDDcallbacks]]
-Void RDD callbacks
-++++++++++++++++++
+#### Void RDD callbacks
 
 If your RDD callback doesn't return any value back to a Camel pipeline,
 you can either return `null` value or use `VoidRddCallback` base class:
@@ -188,9 +176,7 @@ RddCallback<Void> rddCallback() {
 }
 ------------------------------------------------------------------
 
-[[ApacheSpark-ConvertingRDDcallbacks]]
-Converting RDD callbacks
-++++++++++++++++++++++++
+#### Converting RDD callbacks
 
 If you know what type of the input data will be sent to the RDD
 callback, you can use `ConvertingRddCallback` and let Camel to
@@ -213,9 +199,7 @@ RddCallback<Long> rddCallback(CamelContext context) {
 }
 ---------------------------------------------------------------------------
 
-[[ApacheSpark-AnnotatedRDDcallbacks]]
-Annotated RDD callbacks
-+++++++++++++++++++++++
+#### Annotated RDD callbacks
 
 Probably the easiest way to work with the RDD callbacks is to provide
 class with method marked with `@RddCallback` annotation:
@@ -282,9 +266,7 @@ long result = producerTemplate.requestBody("spark:rdd?rdd=#rdd&rddCallback=#rddC
 
 Â 
 
-[[ApacheSpark-DataFramejobs]]
-DataFrame jobs
-^^^^^^^^^^^^^^
+### DataFrame jobs
 
 Instead of working with RDDs Spark component can work with DataFrames as
 well. 
@@ -359,9 +341,7 @@ DataFrame cars(HiveContext hiveContext) {
 }
 ------------------------------------------------------------------------
 
-[[ApacheSpark-Hivejobs]]
-Hive jobs
-^^^^^^^^^
+### Hive jobs
 
 Â Instead of working with RDDs or DataFrame Spark component can also
 receive Hive SQL queries as payloads. To send Hive query to Spark
@@ -401,12 +381,9 @@ DataFrame cars(HiveContext hiveContext) {
 }
 ------------------------------------------------------------------------
 
-[[ApacheSpark-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-splunk/src/main/docs/splunk-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-splunk/src/main/docs/splunk-component.adoc b/components/camel-splunk/src/main/docs/splunk-component.adoc
index c45960c..c93716a 100644
--- a/components/camel-splunk/src/main/docs/splunk-component.adoc
+++ b/components/camel-splunk/src/main/docs/splunk-component.adoc
@@ -1,4 +1,4 @@
-# Splunk Component
+## Splunk Component
 
 *Available as of Camel 2.13*
 
@@ -19,18 +19,14 @@ for this component:
     </dependency>
 ---------------------------------------------
 
-[[Splunk-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
   splunk://[endpoint]?[options]
 -------------------------------
 
-[[Splunk-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -62,9 +58,7 @@ SplunkEvent.  See comment under message body.
 In this example a converter is required to convert to a SplunkEvent
 class.
 
-[[Splunk-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints:
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -87,9 +81,7 @@ name of the query in the savedSearch option.
 camel-splunk creates a route exchange per search result with a
 SplunkEvent in the body.
 
-[[Splunk-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 
@@ -165,9 +157,7 @@ The Splunk component supports 43 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Splunk-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
 
 Splunk operates on data in key/value pairs. The SplunkEvent class is a
 placeholder for such data, and should be in the message body for the producer.
@@ -178,9 +168,7 @@ As of Camel 2.16.0 you can send raw data to Splunk by setting the raw
 option on the producer endpoint. This is useful for eg. json/xml and
 other payloads where Splunk has build in support. 
 
-[[Splunk-UseCases]]
-Use Cases
-^^^^^^^^^
+### Use Cases
 
 Search Twitter for tweets with music and publish events to Splunk
 
@@ -229,21 +217,16 @@ Search Splunk for tweets
           .log("${body}");
 --------------------------------------------------------------------------------------------------------------------------------
 
-[[Splunk-Othercomments]]
-Other comments
-^^^^^^^^^^^^^^
+### Other comments
 
 Splunk comes with a variety of options for leveraging machine generated
 data with prebuilt apps for analyzing and displaying this.  +
  For example the jmx app. could be used to publish jmx attributes, eg.
 route and jvm metrics to Splunk, and displaying this on a dashboard.
 
-[[Splunk-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc b/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
index a7cfbcc..843a2cd 100644
--- a/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
+++ b/components/camel-spring-batch/src/main/docs/spring-batch-component.adoc
@@ -1,4 +1,4 @@
-# Spring Batch Component
+## Spring Batch Component
 
 The *spring-batch:* component and support classes provide integration
 bridge between Camel and http://www.springsource.org/spring-batch[Spring
@@ -17,9 +17,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SpringBatch-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------
@@ -34,9 +32,7 @@ WARNING:This component can only be used to define producer endpoints, which
 means that you cannot use the Spring Batch component in a `from()`
 statement.
 
-[[SpringBatch-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -83,9 +79,7 @@ The Spring Batch component supports 5 endpoint options which are listed below:
 
 
 
-[[SpringBatch-Usage]]
-Usage
-^^^^^
+### Usage
 
 When Spring Batch component receives the message, it triggers the job
 execution. The job will be executed using the
@@ -107,9 +101,7 @@ parameters. `String`, `Long`, `Double` and `java.util.Date` values are
 copied to the `org.springframework.batch.core.JobParametersBuilder` -
 other data types are converted to Strings.
 
-[[SpringBatch-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 Triggering the Spring Batch job execution:
 
@@ -140,16 +132,12 @@ JobExecution jobExecution = mockEndpoint.getExchanges().get(0).getIn().getBody(J
 BatchStatus currentJobStatus = jobExecution.getStatus();
 ---------------------------------------------------------------------------------------------------
 
-[[SpringBatch-Supportclasses]]
-Support classes
-^^^^^^^^^^^^^^^
+### Support classes
 
 Apart from the Component, Camel Spring Batch provides also support
 classes, which can be used to hook into Spring Batch infrastructure.
 
-[[SpringBatch-CamelItemReader]]
-CamelItemReader
-+++++++++++++++
+#### CamelItemReader
 
 `CamelItemReader` can be used to read batch data directly from the Camel
 infrastructure.
@@ -173,9 +161,7 @@ JMS queue.
 </batch:job>
 -----------------------------------------------------------------------------------------------
 
-[[SpringBatch-CamelItemWriter]]
-CamelItemWriter
-+++++++++++++++
+#### CamelItemWriter
 
 `CamelItemWriter` has similar purpose as `CamelItemReader`, but it is
 dedicated to write chunk of the processed data.
@@ -199,9 +185,7 @@ JMS queue.
 </batch:job>
 -----------------------------------------------------------------------------------------------
 
-[[SpringBatch-CamelItemProcessor]]
-CamelItemProcessor
-++++++++++++++++++
+#### CamelItemProcessor
 
 `CamelItemProcessor` is the implementation of Spring Batch
 `org.springframework.batch.item.ItemProcessor` interface. The latter
@@ -241,9 +225,7 @@ the http://camel.apache.org/simple.html[Simple expression language].
 </batch:job>
 -------------------------------------------------------------------------------------------------------------
 
-[[SpringBatch-CamelJobExecutionListener]]
-CamelJobExecutionListener
-+++++++++++++++++++++++++
+#### CamelJobExecutionListener
 
 `CamelJobExecutionListener` is the implementation of the
 `org.springframework.batch.core.JobExecutionListener` interface sending
@@ -274,4 +256,4 @@ JMS queue.
     <batch:listener ref="camelJobExecutionListener"/>
   </batch:listeners>
 </batch:job>
------------------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc b/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
index 3d3dc08..954991e 100644
--- a/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
+++ b/components/camel-spring-integration/src/main/docs/spring-integration-component.adoc
@@ -1,4 +1,4 @@
-# Spring Integration Component
+## Spring Integration Component
 
 The *spring-integration:* component provides a bridge for Camel
 components to talk to
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SpringIntegration-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------------------------
@@ -35,9 +33,7 @@ used by the Spring Integration Spring context. It will equal to the
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SpringIntegration-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -66,9 +62,7 @@ The Spring Integration component supports 8 endpoint options which are listed be
 // endpoint options: END
 
 
-[[SpringIntegration-Usage]]
-Usage
-^^^^^
+### Usage
 
 The Spring integration component is a bridge that connects Camel
 endpoints with Spring integration endpoints through the Spring
@@ -76,21 +70,15 @@ integration's input channels and output channels. Using this component,
 we can send Camel messages to Spring Integration endpoints or receive
 messages from Spring integration endpoints in a Camel routing context.
 
-[[SpringIntegration-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[SpringIntegration-UsingtheSpringintegrationendpoint]]
-Using the Spring integration endpoint
-+++++++++++++++++++++++++++++++++++++
+#### Using the Spring integration endpoint
 
 You can set up a Spring integration endpoint using a URI, as follows:
 
 Or directly using a Spring integration channel name:
 
-[[SpringIntegration-TheSourceandTargetadapter]]
-The Source and Target adapter
-+++++++++++++++++++++++++++++
+#### The Source and Target adapter
 
 Spring integration also provides the Spring integration's source and
 target adapters, which can route messages from a Spring integration
@@ -101,12 +89,9 @@ This example uses the following namespaces:
 
 You can bind your source or target to a Camel endpoint as follows:
 
-[[SpringIntegration-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc b/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
index df5f34e..48ee50b 100644
--- a/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
+++ b/components/camel-spring-ldap/src/main/docs/spring-ldap-component.adoc
@@ -1,4 +1,4 @@
-# Spring LDAP Component
+## Spring LDAP Component
 
 *Available since Camel 2.11*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SpringLDAP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------------
@@ -32,9 +30,7 @@ http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap
 LDAP Template bean]. In this bean, you configure the URL and the
 credentials for your LDAP access.
 
-[[SpringLDAP-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -59,9 +55,7 @@ The Spring LDAP component supports 4 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SpringLDAP-Usage]]
-Usage
-^^^^^
+### Usage
 
 The component supports producer endpoint only. An attempt to create a
 consumer endpoint will result in an `UnsupportedOperationException`. +
@@ -75,48 +69,36 @@ operations. For the `search` and `function_driven` operations, the body is set t
 the search, see
 http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap/core/LdapTemplate.html#search%28java.lang.String,%20java.lang.String,%20int,%20org.springframework.ldap.core.AttributesMapper%29[http://static.springsource.org/spring-ldap/site/apidocs/org/springframework/ldap/core/LdapTemplate.html#search%28java.lang.String,%20java.lang.String,%20int,%20org.springframework.ldap.core.AttributesMapper%29].
 
-[[SpringLDAP-Search]]
-Search
-++++++
+#### Search
 
 The message body must have an entry with the key *`filter`*. The value
 must be a `String` representing a valid LDAP filter, see
 http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol#Search_and_Compare[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol#Search_and_Compare].
 
-[[SpringLDAP-Bind]]
-Bind
-++++
+#### Bind
 
 The message body must have an entry with the key *`attributes`*. The
 value must be an instance of
 http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/Attributes.html[javax.naming.directory.Attributes]
 This entry specifies the LDAP node to be created.
 
-[[SpringLDAP-Unbind]]
-Unbind
-++++++
+#### Unbind
 
 No further entries necessary, the node with the specified *`dn`* is
 deleted.
 
-[[SpringLDAP-Authenticate]]
-Authenticate
-+++++++++++
+#### Authenticate
 
 The message body must have entries with the keys *`filter`* and  *`password`*. The
 values must be an instance of `String` representing a valid LDAP filter and a user password, respectively.
 
-[[SpringLDAP-ModifyAttributes]]
-Modify Attributes
-++++++++++++++++
+#### Modify Attributes
 
 The message body must have an entry with the key *`modificationItems`*. The
 value must be an instance of any array of type
 http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/ModificationItem.html[javax.naming.directory.ModificationItem]
 
-[[SpringLDAP-FunctionDriven]]
-Function-Driven
-++++++++++++++++
+#### Function-Driven
 
 The message body must have entries with the keys *`function`* and *`request`*. The *`function`* value must be of type `java.util.function.BiFunction<L, Q, S>`. The `L` type parameter must be of type `org.springframework.ldap.core.LdapOperations`. The *`request`* value must be the same type as the `Q` type parameter in the *`function`* and it must encapsulate the parameters expected by the LdapTemplate method being invoked within the *`function`*. The `S` type parameter represents the response type as returned by the LdapTemplate method being invoked.
 This operation allows dynamic invocation of LdapTemplate methods that are not covered by the operations mentioned above.
@@ -132,5 +114,4 @@ in `org.apache.camel.springldap.SpringLdapProducer`:
 * public static final String PASSWORD = "password";
 * public static final String MODIFICATION_ITEMS = "modificationItems";
 * public static final String FUNCTION = "function";
-* public static final String REQUEST = "request";
-
+* public static final String REQUEST = "request";
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc b/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
index cdc2286..7a96cca 100644
--- a/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
+++ b/components/camel-spring-redis/src/main/docs/spring-redis-component.adoc
@@ -1,4 +1,4 @@
-# Spring Redis Component
+## Spring Redis Component
 
 *Available as of Camel 2.11*
 
@@ -15,9 +15,7 @@ INFO:*Prerequisites*
 In order to use this component, you must have a Redis server running.
 
 
-[[SpringRedis-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------------
@@ -27,9 +25,7 @@ spring-redis://host:port[?options]
 You can append query options to the URI in the following format,
 `?options=value&option2=value&...`
 
-[[SpringRedis-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 // component options: START
@@ -62,16 +58,12 @@ The Spring Redis component supports 12 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SpringRedis-Usage]]
-Usage
-^^^^^
+### Usage
 
 See also the unit tests available
 at https://github.com/apache/camel/tree/master/components/camel-spring-redis/src/test/java/org/apache/camel/component/redis[https://github.com/apache/camel/tree/master/components/camel-spring-redis/src/test/java/org/apache/camel/component/redis].
 
-[[SpringRedis-MessageheadersevaluatedbytheRedisproducer]]
-Message headers evaluated by the Redis producer
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Redis producer
 
 The producer issues commands to the server and each command has
 different set of parameters with specific types. The result from the
@@ -343,9 +335,7 @@ milliseconds |CamelRedis.Key (String), CamelRedis.Timestamp (Long) |Boolean
 |`PUBLISH` |Post a message to a channel |CamelRedis.Channel (String), CamelRedis.Message (Object) |void
 |=======================================================================
 
-[[SpringRedis-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -363,12 +353,9 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel
 (2.11 or higher).
 
-[[SpringRedis-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
index 5bdbab2..45331bb 100644
--- a/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
+++ b/components/camel-spring-ws/src/main/docs/spring-ws-component.adoc
@@ -1,4 +1,4 @@
-# Spring WebService Component
+## Spring WebService Component
 
 *Available as of Camel 2.6*
 
@@ -33,9 +33,7 @@ module is also included in Spring-WS 1.5.9 (see
 http://stackoverflow.com/questions/3313314/can-spring-ws-1-5-be-used-with-spring-3[this
 post])
 
-[[SpringWebServices-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for this component is as follows
 
@@ -79,9 +77,7 @@ calling upon.
 You can append query *options* to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SpringWebServices-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -127,9 +123,7 @@ The Spring WebService component supports 25 endpoint options which are listed be
 // endpoint options: END
 
 
-[[SpringWebServices-Messageheaders]]
-Message headers
-+++++++++++++++
+#### Message headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -160,9 +154,7 @@ outputAction option if present
 faultAction option if present
 |=======================================================================
 
-[[SpringWebServices-Accessingwebservices]]
-Accessing web services
-~~~~~~~~~~~~~~~~~~~~~~
+### Accessing web services
 
 To call a web service at `http://foo.com/bar` simply define a route:
 
@@ -181,9 +173,7 @@ template.requestBody("direct:example", "<foobar xmlns=\"http://foo.com\"><msg>te
 Remember if it's a SOAP service you're calling you don't have to include
 SOAP tags. Spring-WS will perform the XML-to-SOAP marshaling.
 
-[[SpringWebServices-SendingSOAPandWS-Addressingactionheaders]]
-Sending SOAP and WS-Addressing action headers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending SOAP and WS-Addressing action headers
 
 When a remote web service requires a SOAP action or use of the
 WS-Addressing standard you define your route as:
@@ -203,9 +193,7 @@ template.requestBodyAndHeader("direct:example",
 SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
 --------------------------------------------------------------------
 
-[[SpringWebServices-UsingSOAPheaders]]
-Using SOAP headers
-^^^^^^^^^^^^^^^^^^
+### Using SOAP headers
 
 *Available as of Camel 2.11.1*
 
@@ -237,9 +225,7 @@ For an example see this
 https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring-ws/src/test/java/org/apache/camel/component/spring/ws/SoapHeaderTest.java[unit
 test].
 
-[[SpringWebServices-Theheaderandattachmentpropagation]]
-The header and attachment propagation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The header and attachment propagation
 
 Spring WS Camel supports propagation of the headers and attachments into
 Spring-WS WebServiceMessage response since version *2.10.3*. The
@@ -258,9 +244,7 @@ Note: If the exchange header in the pipeline contains text, it generates
 Qname(key)=value attribute in the soap header. Recommended is to create
 a QName class directly and put into any key into header.
 
-[[SpringWebServices-HowtouseMTOMattachments]]
-How to use MTOM attachments
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to use MTOM attachments
 
 The BasicMessageFilter provides all required information for Apache
 Axiom in order to produce MTOM message. If you want to use Apache Camel
@@ -318,9 +302,7 @@ from("direct:send")
 - Now, your producer will generate MTOM message with otpmized
 attachments.
 
-[[SpringWebServices-Thecustomheaderandattachmentfiltering]]
-The custom header and attachment filtering
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The custom header and attachment filtering
 
 If you need to provide your custom processing of either headers or
 attachments, extend existing BasicMessageFilter and override the
@@ -363,9 +345,7 @@ protected void doProcessSoapAttachements(Message inOrOut, SoapMessage response)
 { your code /*no need to call super*/ }
 -------------------------------------------------------------------------------
 
-[[SpringWebServices-UsingacustomMessageSenderandMessageFactory]]
-Using a custom MessageSender and MessageFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a custom MessageSender and MessageFactory
 
 A custom message sender or factory in the registry can be referenced
 like this:
@@ -398,9 +378,7 @@ Spring configuration:
 </bean>
 ---------------------------------------------------------------------------------------------------------------------
 
-[[SpringWebServices-Exposingwebservices]]
-Exposing web services
-~~~~~~~~~~~~~~~~~~~~~
+### Exposing web services
 
 In order to expose a web service using this component you first need to
 set-up a
@@ -459,9 +437,7 @@ comes in). Also don't forget to check out the
 link:spring-ws-example.html[Spring Web Services Example] included in the
 Camel distribution.
 
-[[SpringWebServices-Endpointmappinginroutes]]
-Endpoint mapping in routes
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Endpoint mapping in routes
 
 With the XML configuration in-place you can now use Camel's DSL to
 define what web service requests are handled by your endpoint:
@@ -503,9 +479,7 @@ from("spring-ws:xpathresult:abc?expression=//foobar&endpointMapping=#endpointMap
 .convertBodyTo(String.class).to(mock:example)
 --------------------------------------------------------------------------------------
 
-[[SpringWebServices-Alternativeconfiguration,usingexistingendpointmappings]]
-Alternative configuration, using existing endpoint mappings
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Alternative configuration, using existing endpoint mappings
 
 For every endpoint with mapping-type `beanname` one bean of type
 `CamelEndpointDispatcher` with a corresponding name is required in the
@@ -548,9 +522,7 @@ An example of a route using `beanname`:
 <bean id="FutureEndpointDispatcher" class="org.apache.camel.component.spring.ws.bean.CamelEndpointDispatcher" />
 ------------------------------------------------------------------------------------------------------------------------
 
-[[SpringWebServices-POJO-unmarshalling]]
-POJO (un)marshalling
-~~~~~~~~~~~~~~~~~~~~
+### POJO (un)marshalling
 
 Camel's link:data-format.html[pluggable data formats] offer support for
 pojo/xml marshalling using libraries such as JAXB, XStream, JibX, Castor
@@ -577,12 +549,9 @@ from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointM
 .to("mock:example").marshal(jaxb);
 --------------------------------------------------------------------------------------------------------
 
-[[SpringWebServices-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring/src/main/docs/spel-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring/src/main/docs/spel-language.adoc b/components/camel-spring/src/main/docs/spel-language.adoc
index 8efff63..3020b22 100644
--- a/components/camel-spring/src/main/docs/spel-language.adoc
+++ b/components/camel-spring/src/main/docs/spel-language.adoc
@@ -1,4 +1,4 @@
-# SpEL Language
+## SpEL Language
 
 *Available as of Camel 2.7*
 
@@ -8,9 +8,7 @@ to be used as an link:expression.html[Expression] or
 link:predicate.html[Predicate] in the link:dsl.html[DSL] or
 link:xml-configuration.html[Xml Configuration].
 
-[[SpEL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 The following variables are available in expressions and predicates
 written in SpEL:
@@ -42,9 +40,7 @@ written in SpEL:
 |property(name, type) |Type |the property by the given name as the given type
 |=======================================================================
 
-[[SpEL-Options]]
-Options
-^^^^^^^
+### Options
 
 // language options: START
 The SpEL language supports 1 options which are listed below.
@@ -60,13 +56,9 @@ The SpEL language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[SpEL-Samples]]
-Samples
-^^^^^^^
+### Samples
 
-[[SpEL-Expressiontemplating]]
-Expression templating
-+++++++++++++++++++++
+#### Expression templating
 
 SpEL expressions need to be surrounded by `#{` `}` delimiters since
 expression templating is enabled. This allows you to combine SpEL
@@ -106,9 +98,7 @@ template.sendBodyAndHeader("direct:example", "World", "dayOrNight", "day");
 The output on `mock:result` will be _"Hello World! What a beautiful
 day"_
 
-[[SpEL-Beanintegration]]
-Bean integration
-++++++++++++++++
+#### Bean integration
 
 You can reference beans defined in the link:registry.html[Registry]
 (most likely an `ApplicationContext`) in your SpEL expressions. For
@@ -120,9 +110,7 @@ can invoke the "bar" method on this bean like this:
 #{@foo.bar == 'xyz'}
 --------------------
 
-[[SpEL-SpELinenterpriseintegrationpatterns]]
-SpEL in enterprise integration patterns
-+++++++++++++++++++++++++++++++++++++++
+#### SpEL in enterprise integration patterns
 
 You can use SpEL as an expression for link:recipient-list.html[Recipient
 List] or as a predicate inside a link:message-filter.html[Message
@@ -146,9 +134,7 @@ And the equivalent in Java DSL:
    from("direct:foo").filter().spel("#{request.headers['foo'] == 'bar'}").to("direct:bar");
 -------------------------------------------------------------------------------------------
 
-[[SpEL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -162,9 +148,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").spel("resource:classpath:myspel.txt")
 ------------------------------------------------------------
 
-[[SpEL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 You need Spring 3.0 or higher to use Spring Expression Language. If you
 use Maven you could just add the following to your `pom.xml`:
@@ -177,4 +161,4 @@ use Maven you could just add the following to your `pom.xml`:
   <version>xxx</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-spring/src/main/docs/spring-event-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-spring/src/main/docs/spring-event-component.adoc b/components/camel-spring/src/main/docs/spring-event-component.adoc
index 1de4c1d..0a8c65a 100644
--- a/components/camel-spring/src/main/docs/spring-event-component.adoc
+++ b/components/camel-spring/src/main/docs/spring-event-component.adoc
@@ -1,4 +1,4 @@
-# Spring Event Component
+## Spring Event Component
 
 The *spring-event:* component provides access to the Spring
 `ApplicationEvent` objects. This allows you to publish
@@ -8,9 +8,7 @@ link:enterprise-integration-patterns.html[Enterprise Integration
 Patterns] to process them such as link:message-filter.html[Message
 Filter].
 
-[[SpringEvent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------
@@ -20,9 +18,7 @@ spring-event://default[?options]
 Note, at the moment there are no options for this component. That can
 easily change in future releases, so please check back.
 
-[[Spring-Event-Options]]
-Spring Event Options
-^^^^^^^^^^^^^^^^^^^^
+### Spring Event Options
 
 
 
@@ -60,12 +56,9 @@ The Spring Event component supports 5 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SpringEvent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sql/src/main/docs/sql-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc b/components/camel-sql/src/main/docs/sql-component.adoc
index ee3c325..6bef6d2 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -1,4 +1,4 @@
-# SQL Component
+## SQL Component
 
 The *sql:* component allows you to work with databases using JDBC
 queries. The difference between this component and link:jdbc.html[JDBC]
@@ -29,9 +29,7 @@ further below.
 * a JDBC based repository for the link:aggregator2.html[Aggregator] EIP
 pattern. See further below.
 
-[[SQLComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 WARNING:From Camel 2.11 onwards this component can create both consumer (e.g.
 `from()`) and producer endpoints (e.g. `to()`).
@@ -102,9 +100,7 @@ also use comments such as the – dash line.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SQLComponent-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -184,9 +180,7 @@ The SQL component supports 46 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SQLComponent-Treatmentofthemessagebody]]
-Treatment of the message body
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Treatment of the message body
 
 The SQL component tries to convert the message body to an object of
 `java.util.Iterator` type and then uses this iterator to fill the query
@@ -211,9 +205,7 @@ parameters must be provided in a header with the
 key SqlConstants.SQL_PARAMETERS. This allows the SQL component to work
 more dynamic as the SQL query is from the message body.
 
-[[SQLComponent-Resultofthequery]]
-Result of the query
-^^^^^^^^^^^^^^^^^^^
+### Result of the query
 
 For `select` operations, the result is an instance of
 `List<Map<String, Object>>` type, as returned by the
@@ -235,9 +227,7 @@ from("jms:order.inbox")
     .to("jms:order.booking");
 -------------------------------------------------------------------------------------------
 
-[[SQLComponent-UsingStreamList]]
-Using StreamList
-^^^^^^^^^^^^^^^^
+### Using StreamList
 
 From*Camel 2.18* onwards the producer supports outputType=StreamList
 that uses an iterator to stream the output of the query. This allows to
@@ -258,9 +248,7 @@ from("direct:withSplitModel")
 
 Â 
 
-[[SQLComponent-Headervalues]]
-Header values
-^^^^^^^^^^^^^
+### Header values
 
 When performing `update` operations, the SQL Component stores the update
 count in the following message headers:
@@ -295,9 +283,7 @@ message headers (*Available as of Camel 2.12.4, 2.13.1*):
 |CamelSqlGeneratedKeyRows |Rows that contains the generated keys (a list of maps of keys).
 |=======================================================================
 
-[[SQLComponent-Generatedkeys]]
-Generated keys
-^^^^^^^^^^^^^^
+### Generated keys
 
 *Available as of Camel 2.12.4, 2.13.1 and 2.14 *
 
@@ -312,9 +298,7 @@ You can see more details in this
 https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob_plain;f=components/camel-sql/src/test/java/org/apache/camel/component/sql/SqlGeneratedKeysTest.java;hb=3962b23f94bb4bc23011b931add08c3f6833c82e[unit
 test].
 
-[[SQLComponent-Configuration]]
-Configuration
-^^^^^^^^^^^^^
+### Configuration
 
 You can now set a reference to a `DataSource` in the URI directly:
 
@@ -323,9 +307,7 @@ You can now set a reference to a `DataSource` in the URI directly:
 sql:select * from table where id=# order by name?dataSource=myDS
 ----------------------------------------------------------------
 
-[[SQLComponent-Sample]]
-Sample
-^^^^^^
+### Sample
 
 In the sample below we execute a query and retrieve the result as a
 `List` of rows, where each row is a `Map<String, Object` and the key is
@@ -354,9 +336,7 @@ We could configure the `DataSource` in Spring XML as follows:
  <jee:jndi-lookup id="myDS" jndi-name="jdbc/myDataSource"/>
 -----------------------------------------------------------
 
-[[SQLComponent-Usingnamedparameters]]
-Using named parameters
-++++++++++++++++++++++
+#### Using named parameters
 
 *Available as of Camel 2.11*
 
@@ -385,9 +365,7 @@ parameters will be taken from the body.
      .to("sql:select * from projects where license = :#lic and id > :#min order by id")
 ---------------------------------------------------------------------------------------
 
-[[SQLComponent-Usingexpressionparameters]]
-Using expression parameters
-+++++++++++++++++++++++++++
+#### Using expression parameters
 
 *Available as of Camel 2.14*
 
@@ -403,9 +381,7 @@ from("direct:projects")
   .to("sql:select * from projects where license = :#${body} and id > :#${property.min} order by id")
 ----------------------------------------------------------------------------------------------------
 
-[[SQLComponent-UsingINquerieswithdynamicvalues]]
-Using IN queries with dynamic values
-++++++++++++++++++++++++++++++++++++
+#### Using IN queries with dynamic values
 
 *Available as of Camel 2.17*
 
@@ -474,9 +450,7 @@ from("direct:query")
 
 Â 
 
-[[SQLComponent-UsingtheJDBCbasedidempotentrepository]]
-Using the JDBC based idempotent repository
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using the JDBC based idempotent repository
 
 *Available as of Camel 2.7*: In this section we will use the JDBC based
 idempotent repository.
@@ -751,9 +725,7 @@ class="org.apache.camel.processor.aggregate.jdbc.DefaultJdbcOptimisticLockingExc
 -------------------------------------------------------------------------------
 Â 
 
-[[SQLComponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -762,4 +734,4 @@ See Also
 
 link:sql-stored-procedure.html[SQL Stored Procedure]
 
-link:jdbc.html[JDBC]
+link:jdbc.html[JDBC]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sql/src/main/docs/sql-stored-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sql/src/main/docs/sql-stored-component.adoc b/components/camel-sql/src/main/docs/sql-stored-component.adoc
index 2a2d174..6145378 100644
--- a/components/camel-sql/src/main/docs/sql-stored-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-stored-component.adoc
@@ -1,4 +1,4 @@
-# SQL StoredProcedure Component
+## SQL StoredProcedure Component
 
 *Available as of Camel 2.17*
 
@@ -23,9 +23,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SQLStoredProcedure-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The SQL component uses the following endpoint URI notation:
 
@@ -60,9 +58,7 @@ SUBNUMBERS(
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SQLStoredProcedure-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -102,9 +98,7 @@ The SQL StoredProcedure component supports 7 endpoint options which are listed b
 // endpoint options: END
 
 
-[[SQLStoredProcedure-Declaringthestoredproceduretemplate]]
-Declaring the stored procedure template
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Declaring the stored procedure template
 
 The template is declared using a syntax that would be similar to a Java
 method signature. The name of the stored procedure, and then the
@@ -127,14 +121,11 @@ In SQL term the stored procedure could be declared as:
 CREATE PROCEDURE SUBNUMBERS(VALUE1 INTEGER, VALUE2 INTEGER,OUT RESULT INTEGER)
 ------------------------------------------------------------------------------
 
-[[SQLStoredProcedure-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:sql-component.html[SQL Component]
-
+* link:sql-component.html[SQL Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ssh/src/main/docs/ssh-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ssh/src/main/docs/ssh-component.adoc b/components/camel-ssh/src/main/docs/ssh-component.adoc
index 5eaaf98..542616e 100644
--- a/components/camel-ssh/src/main/docs/ssh-component.adoc
+++ b/components/camel-ssh/src/main/docs/ssh-component.adoc
@@ -1,4 +1,4 @@
-# SSH Component
+## SSH Component
 
 *Available as of Camel 2.10*
 
@@ -18,18 +18,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SSH-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------------------------
 ssh:[username[:password]@]host[:port][?options]
 -----------------------------------------------
 
-[[SSH-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -100,9 +96,7 @@ The SSH component supports 28 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SSH-UsageasaProducerendpoint]]
-Usage as a Producer endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Usage as a Producer endpoint
 
 When the SSH Component is used as a Producer (`.to("ssh://...")`), it
 will send the message body as the command to execute on the remote SSH
@@ -123,9 +117,7 @@ an XML encoded newline (`&#10;`).
 </route>
 ----------------------------------------------
 
-[[SSH-Authentication]]
-Authentication
-^^^^^^^^^^^^^^
+### Authentication
 
 The SSH Component can authenticate against the remote SSH server using
 one of two mechanisms: Public Key certificate or username/password.
@@ -192,19 +184,14 @@ of Camel you are using.
 </dependency>
 -----------------------------------------
 
-[[SSH-Example]]
-Example
-^^^^^^^
+### Example
 
 See the `examples/camel-example-ssh` and
 `examples/camel-example-ssh-security` in the Camel distribution.
 
-[[SSH-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-stax/src/main/docs/stax-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stax/src/main/docs/stax-component.adoc b/components/camel-stax/src/main/docs/stax-component.adoc
index d56cc01..d4c5070 100644
--- a/components/camel-stax/src/main/docs/stax-component.adoc
+++ b/components/camel-stax/src/main/docs/stax-component.adoc
@@ -1,4 +1,4 @@
-# StAX Component
+## StAX Component
 
 *Available as of Camel 2.9*
 
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[StAX-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------
@@ -46,9 +44,7 @@ using the # syntax as shown:
 stax:#myHandler
 ---------------
 
-[[Stax-Options]]
-Options
-~~~~~~~
+### Options
 
 
 // component options: START
@@ -71,9 +67,7 @@ The StAX component supports 2 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[StAX-UsageofacontenthandlerasStAXparser]]
-Usage of a content handler as StAX parser
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Usage of a content handler as StAX parser
 
 The message body after the handling is the handler itself.
 
@@ -93,9 +87,7 @@ from("file:target/in")
   });
 --------------------------------------------------------------------------------------------------------
 
-[[StAX-IterateoveracollectionusingJAXBandStAX]]
-Iterate over a collection using JAXB and StAX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Iterate over a collection using JAXB and StAX
 
 First we suppose you have JAXB objects.
 
@@ -199,18 +191,13 @@ from("file:target/in")
         .to("mock:records");
 -------------------------------------------------
 
-[[StAX-ThepreviousexamplewithXMLDSL]]
-The previous example with XML DSL
-+++++++++++++++++++++++++++++++++
+#### The previous example with XML DSL
 
 The example above could be implemented as follows in XML DSL
 
-[[StAX-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-stomp/src/main/docs/stomp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stomp/src/main/docs/stomp-component.adoc b/components/camel-stomp/src/main/docs/stomp-component.adoc
index 41dc26d..3c9d48c 100644
--- a/components/camel-stomp/src/main/docs/stomp-component.adoc
+++ b/components/camel-stomp/src/main/docs/stomp-component.adoc
@@ -1,4 +1,4 @@
-# Stomp Component
+## Stomp Component
 
 *Available as of Camel 2.12*
 
@@ -20,9 +20,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Stomp-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------
@@ -31,9 +29,7 @@ stomp:queue:destination[?options]
 
 Where *destination* is the name of the queue.
 
-[[Stomp-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -85,9 +81,7 @@ The Stomp component supports 10 endpoint options which are listed below:
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Stomp-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 Sending messages:
 
@@ -103,9 +97,7 @@ Consuming messages:
 from("stomp:queue:test").transform(body().convertToString()).to("mock:result")
 ------------------------------------------------------------------------------
 
-[[Stomp-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
 
 Camel supports the link:message-endpoint.html[Message Endpoint] pattern
 using the
@@ -134,12 +126,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
 consuming message exchanges from the endpoint via a
 http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
 
-[[Stomp-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:message-endpoint.html[Message Endpoint] pattern
 * link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-stream/src/main/docs/stream-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stream/src/main/docs/stream-component.adoc b/components/camel-stream/src/main/docs/stream-component.adoc
index 8655e51..cf8f3d5 100644
--- a/components/camel-stream/src/main/docs/stream-component.adoc
+++ b/components/camel-stream/src/main/docs/stream-component.adoc
@@ -1,4 +1,4 @@
-# Stream Component
+## Stream Component
 
 The *stream:* component provides access to the `System.in`, `System.out`
 and `System.err` streams as well as allowing streaming of file and URL.
@@ -16,9 +16,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Stream-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------
@@ -43,9 +41,7 @@ producers (that is, it cannot appear in `from()`).
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Stream-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -85,9 +81,7 @@ The Stream component supports 19 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Stream-Messagecontent]]
-Message content
-^^^^^^^^^^^^^^^
+### Message content
 
 The *stream:* component supports either `String` or `byte[]` for writing
 to streams. Just add either `String` or `byte[]` content to the
@@ -100,9 +94,7 @@ add a `java.io.OutputStream` object to `message.in.header` in the key
 `header`. +
  See samples for an example.
 
-[[Stream-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 In the following sample we route messages from the `direct:in` endpoint
 to the `System.out` stream:
@@ -138,12 +130,9 @@ file will be re-opened and scanned with each iteration of
 scanStreamDelay. Until NIO2 is available we cannot reliably detect when
 a file is deleted/recreated.
 
-[[Stream-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stringtemplate/src/main/docs/string-template-component.adoc b/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
index 1c63368..8fe61b3 100644
--- a/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
+++ b/components/camel-stringtemplate/src/main/docs/string-template-component.adoc
@@ -1,4 +1,4 @@
-# String Template Component
+## String Template Component
 
 The *string-template:* component allows you to process a message using a
 http://www.stringtemplate.org/[String Template]. This can be ideal when
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[StringTemplate-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------------
@@ -33,9 +31,7 @@ invoke; or the complete URL of the remote template.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[StringTemplate-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -61,26 +57,20 @@ The String Template component supports 5 endpoint options which are listed below
 // endpoint options: END
 
 
-[[StringTemplate-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 Camel will store a reference to the resource in the message header with
 key, `org.apache.camel.stringtemplate.resource`. The Resource is an
 `org.springframework.core.io.Resource` object.
 
-[[StringTemplate-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
 
 The string template resource is by default hot-reloadable for both file
 and classpath resources (expanded jar). If you set `contentCache=true`,
 Camel loads the resource only once and hot-reloading is not possible.
 This scenario can be used in production when the resource never changes.
 
-[[StringTemplate-StringTemplateAttributes]]
-StringTemplate Attributes
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### StringTemplate Attributes
 
 Since Camel 2.14, you can define the custom context map by setting the
 message header "*CamelStringTemplateVariableMap*" just like the below
@@ -97,9 +87,7 @@ variableMap.put("exchange", exchange);
 exchange.getIn().setHeader("CamelStringTemplateVariableMap", variableMap);
 --------------------------------------------------------------------------
 
-[[StringTemplate-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use a string template as follows in order to
 formulate a response to a message:
@@ -110,9 +98,7 @@ from("activemq:My.Queue").
   to("string-template:com/acme/MyResponse.tm");
 -----------------------------------------------
 
-[[StringTemplate-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
 
 In this sample we want to use a string template to send an order
 confirmation email. The email template is laid out in `StringTemplate`
@@ -131,12 +117,9 @@ Regards Camel Riders Bookstore
 
 And the java code is as follows:
 
-[[StringTemplate-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
index 8c985d7..c09d2ff 100644
--- a/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
+++ b/components/camel-syslog/src/main/docs/syslog-dataformat.adoc
@@ -1,4 +1,4 @@
-# Syslog DataFormat
+## Syslog DataFormat
 
 *Available as of Camel 2.6*
 
@@ -31,9 +31,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Syslog-RFC3164Syslogprotocol]]
-RFC3164 Syslog protocol
-^^^^^^^^^^^^^^^^^^^^^^^
+### RFC3164 Syslog protocol
 
 Syslog uses the user datagram protocol (UDP)
 https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=CAMEL&title=1&linkCreation=true&fromPageId=24185759[1]
@@ -46,9 +44,7 @@ where we just use the `Rfc3164SyslogDataFormat` to marshal and unmarshal
 messages. Notice that from *Camel 2.14* onwards the syslog dataformat is
 renamed to `SyslogDataFormat`.
 
-[[Syslog-Dataformat-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The Syslog dataformat supports 1 options which are listed below.
@@ -64,9 +60,7 @@ The Syslog dataformat supports 1 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[Syslog-RFC5424Syslogprotocol]]
-RFC5424 Syslog protocol
-^^^^^^^^^^^^^^^^^^^^^^^
+### RFC5424 Syslog protocol
 
 *Available as of Camel 2.14*
 
@@ -75,9 +69,7 @@ existing link:mina.html[camel-mina] component
 or link:netty.html[camel-netty] where we just use
 the `SyslogDataFormat` to marshal and unmarshal messages
 
-[[Syslog-ExposingaSysloglistener]]
-Exposing a Syslog listener
-++++++++++++++++++++++++++
+#### Exposing a Syslog listener
 
 In our Spring XML file, we configure an endpoint to listen for udp
 messages on port 10514, note that in netty we disable the defaultCodec,
@@ -121,9 +113,7 @@ The same route using link:mina.html[camel-mina]
 </camelContext>
 -------------------------------------------------------------------------
 
-[[Syslog-Sendingsyslogmessagestoaremotedestination]]
-Sending syslog messages to a remote destination
-+++++++++++++++++++++++++++++++++++++++++++++++
+#### Sending syslog messages to a remote destination
 
 [source,xml]
 -------------------------------------------------------------------------
@@ -142,12 +132,9 @@ Sending syslog messages to a remote destination
 </camelContext>
 -------------------------------------------------------------------------
 
-[[Syslog-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc b/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
index d9a0c3e..999e675 100644
--- a/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
+++ b/components/camel-tagsoup/src/main/docs/tidyMarkup-dataformat.adoc
@@ -1,4 +1,4 @@
-# TidyMarkup DataFormat
+## TidyMarkup DataFormat
 
 TidyMarkup is a link:data-format.html[Data Format] that uses the
 http://www.ccil.org/~cowan/XML/tagsoup/[TagSoup] to tidy up HTML. It can
@@ -15,9 +15,7 @@ link:tidymarkup.html[TidyMarkup] only supports the *unmarshal* operation
 as we really don't want to turn well formed HTML into ugly HTML
 image:https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png[(smile)]
 
-[[TidyMarkup-Options]]
-TidyMarkup Options
-^^^^^^^^^^^^^^^
+### TidyMarkup Options
 
 
 
@@ -40,9 +38,7 @@ The TidyMarkup dataformat supports 3 options which are listed below.
 
 
 
-[[TidyMarkup-JavaDSLExample]]
-Java DSL Example
-^^^^^^^^^^^^^^^^
+### Java DSL Example
 
 An example where the consumer provides some HTML
 
@@ -51,9 +47,7 @@ An example where the consumer provides some HTML
 from("file://site/inbox").unmarshal().tidyMarkup().to("file://site/blogs");
 ---------------------------------------------------------------------------
 
-[[TidyMarkup-SpringXMLExample]]
-Spring XML Example
-^^^^^^^^^^^^^^^^^^
+### Spring XML Example
 
 The following example shows how to use link:tidymarkup.html[TidyMarkup]
 to unmarshal using Spring
@@ -71,9 +65,7 @@ to unmarshal using Spring
 </camelContext>
 -----------------------------------------------------------------------
 
-[[TidyMarkup-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use TidyMarkup in your camel routes you need to add the a dependency
 on *camel-tagsoup* which implements this data format.
@@ -89,4 +81,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-tagsoup</artifactId>
   <version>x.x.x</version>
 </dependency>
-----------------------------------------
+----------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc b/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
index 0aa9699..92c1997 100644
--- a/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
+++ b/components/camel-tarfile/src/main/docs/tarfile-dataformat.adoc
@@ -1,4 +1,4 @@
-# Tar File DataFormat
+## Tar File DataFormat
 
 TIP:*Available since Camel 2.18.0*
 
@@ -10,9 +10,7 @@ entry can be unmarshalled (decompressed) to the original file contents.
 There is also a aggregation strategy that can
 aggregate multiple messages into a single Tar File.
 
-[[TarFile-Options]]
-TarFile Options
-^^^^^^^^^^^^^^^
+### TarFile Options
 
 
 // dataformat options: START
@@ -31,9 +29,7 @@ The Tar File dataformat supports 2 options which are listed below.
 // dataformat options: END
 
 
-[[TarFileDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
 
 In this example we marshal a regular text/XML payload to a compressed
 payload using Tar File compression, and send it to an ActiveMQ queue
@@ -74,9 +70,7 @@ from("direct:start").setHeader(Exchange.FILE_NAME, constant("report.txt")).marsh
 This route would result in a Tar File named "report.txt.tar" in the
 output directory, containing a single Tar entry named "report.txt".
 
-[[TarFileDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
 
 In this example we unmarshal a Tar File payload from an ActiveMQ queue
 called MY_QUEUE to its original format, and forward it for processing to
@@ -116,9 +110,7 @@ like this
 ----------------------------------------------------------------------------------------------------
 
 
-[[TarFileDataFormat-Aggregate]]
-Aggregate
-^^^^^^^^^
+### Aggregate
 
 INFO:Please note that this aggregation strategy requires eager completion
 check to work properly.
@@ -152,9 +144,7 @@ the `CamelFileName` header explicitly in your route:
    .to("file:output/directory");
 ------------------------------------------------------------
 
-[[TarFileDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Tar Files in your camel routes you need to add a dependency on
 *camel-tarfile* which implements this data format.
@@ -171,4 +161,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-telegram/src/main/docs/telegram-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-telegram/src/main/docs/telegram-component.adoc b/components/camel-telegram/src/main/docs/telegram-component.adoc
index 625c579..b9bbb42 100644
--- a/components/camel-telegram/src/main/docs/telegram-component.adoc
+++ b/components/camel-telegram/src/main/docs/telegram-component.adoc
@@ -1,4 +1,4 @@
-# Telegram Component
+## Telegram Component
 
 *Available as of Camel 2.18*
 
@@ -30,9 +30,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Telegram-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------------------------
@@ -42,9 +40,7 @@ telegram:type/authorizationToken[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Telegram-Options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The Telegram component supports 1 options which are listed below.
@@ -100,9 +96,7 @@ The Telegram component supports 24 endpoint options which are listed below:
 
 
 
-[[Telegram-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="20%,80%",options="header",]
 |=======================================================================
@@ -122,16 +116,12 @@ for outgoing binary messages.
 
 |=======================================================================
 
-[[Telegram-Usage]]
-Usage
-^^^^^
+### Usage
 
 The Telegram component supports both consumer and producer endpoints.
 It can also be used in *reactive chat-bot mode* (to consume, then produce messages).
 
-[[Telegram-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
 
 The following is a basic example of how to send a message to a Telegram chat through the
 Telegram Bot API.
@@ -172,9 +162,7 @@ The following message bodies are allowed for a producer endpoint (messages of ty
 |===================================================
 
 
-[[Telegram-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
 
 The following is a basic example of how to receive all messages that telegram users are sending to the configured Bot.
 In Java DSL
@@ -227,9 +215,7 @@ Supported types for incoming messages are
 
 
 
-[[Telegram-ReactiveChatBot]]
-Reactive Chat-Bot Example
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reactive Chat-Bot Example
 
 The reactive chat-bot mode is a simple way of using the Camel component to build a simple
 chat bot that replies directly to chat messages received from the Telegram users.
@@ -278,9 +264,7 @@ public class ChatBotLogic {
 Every non-null string returned by the `chatBotProcess` method is automatically routed to the
 chat that originated the request (as the `CamelTelegramChatId` header is used to route the message).
 
-[[Telegram-GettingTheChatId]]
-Getting the Chat ID
-^^^^^^^^^^^^^^^^^^^
+### Getting the Chat ID
 
 If you want to push messages to a specific Telegram chat when an event occurs, you need to
 retrieve the corresponding chat ID. The chat ID is not currently shown in the telegram client,
@@ -306,4 +290,4 @@ from("timer:tick")
 to("telegram:bots/123456789:AAE_dLq5C19xwGjw3yiC2NvEUrZcejK21-Q987654321:AAE_dLq5C19xwOmg5yiC2NvSrkT3wj5Q1-L?chatId=123456")
 ---------------------------------------------------------
 
-Note that the corresponding URI parameter is simply `chatId`.
+Note that the corresponding URI parameter is simply `chatId`.
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[04/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quartz2/src/main/docs/quartz2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quartz2/src/main/docs/quartz2-component.adoc b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
index 2ad143b..71a3e1e 100644
--- a/components/camel-quartz2/src/main/docs/quartz2-component.adoc
+++ b/components/camel-quartz2/src/main/docs/quartz2-component.adoc
@@ -1,4 +1,4 @@
-# Quartz2 Component
+## Quartz2 Component
 
 *Available as of Camel 2.12.0*
 
@@ -24,9 +24,7 @@ for this component:
 remain on old Quartz 1.x, please +
  use the old link:quartz.html[Quartz] component instead.
 
-[[Quartz2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------------
@@ -44,9 +42,7 @@ name.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Quartz2-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -130,9 +126,7 @@ to the <camelContext> that this id is unique, as this is
 required by the `QuartzScheduler` in the OSGi container. If you do not
 set any `id` on <camelContext> then a unique id is auto assigned, and there is no problem.
 
-[[Quartz2-Configuringquartz.propertiesfile]]
-Configuring quartz.properties file
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring quartz.properties file
 
 By default Quartz will look for a `quartz.properties` file in the
 `org/quartz` directory of the classpath. If you are using WAR
@@ -160,9 +154,7 @@ To do this you can configure this in Spring XML as follows
 </bean>
 -------------------------------------------------------------------------------
 
-[[Quartz2-EnablingQuartzschedulerinJMX]]
-Enabling Quartz scheduler in JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Quartz scheduler in JMX
 
 You need to configure the quartz scheduler properties to enable JMX. +
  That is typically setting the option
@@ -172,9 +164,7 @@ configuration file.
 From Camel 2.13 onwards Camel will automatic set this option to true,
 unless explicit disabled.
 
-[[Quartz2-StartingtheQuartzscheduler]]
-Starting the Quartz scheduler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Starting the Quartz scheduler
 
 The link:quartz2.html[Quartz2] component offers an option to let the
 Quartz scheduler be started delayed, or not auto started at all.
@@ -188,9 +178,7 @@ This is an example:
 </bean>
 ------------------------------------------------------------------------------
 
-[[Quartz2-Clustering]]
-Clustering
-^^^^^^^^^^
+### Clustering
 
 If you use Quartz in clustered mode, e.g. the `JobStore` is clustered.
 Then the link:quartz2.html[Quartz2] component will *not* pause/remove
@@ -200,9 +188,7 @@ to keep running on the other nodes in the cluster.
 *Note*: When running in clustered node no checking is done to ensure
 unique job name/group for endpoints.
 
-[[Quartz2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel adds the getters from the Quartz Execution Context as header
 values. The following headers are added: +
@@ -214,9 +200,7 @@ values. The following headers are added: +
 The `fireTime` header contains the `java.util.Date` of when the exchange
 was fired.
 
-[[Quartz2-UsingCronTriggers]]
-Using Cron Triggers
-^^^^^^^^^^^^^^^^^^^
+### Using Cron Triggers
 
 Quartz supports
 http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger[Cron-like
@@ -249,9 +233,7 @@ valid URI syntax:
 |`+` | _Space_
 |=======================================================================
 
-[[Quartz2-Specifyingtimezone]]
-Specifying time zone
-^^^^^^^^^^^^^^^^^^^^
+### Specifying time zone
 
 The Quartz Scheduler allows you to configure time zone per trigger. For
 example to use a timezone of your country, then you can do as follows:
@@ -263,9 +245,7 @@ quartz2://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&trigger.timeZone=Euro
 
 The timeZone value is the values accepted by `java.util.TimeZone`.
 
-[[Quartz2-UsingQuartzScheduledPollConsumerScheduler]]
-Using QuartzScheduledPollConsumerScheduler
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using QuartzScheduledPollConsumerScheduler
 
 The link:quartz2.html[Quartz2] component provides a
 link:polling-consumer.html[Polling Consumer] scheduler which allows to
@@ -325,9 +305,7 @@ use the following as well:
        .to("bean:process");
 --------------------------------------------------------------------
 
-[[Quartz2-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -335,5 +313,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:quartz.html[Quartz]
-* link:timer.html[Timer]
-
+* link:timer.html[Timer]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quickfix/src/main/docs/quickfix-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quickfix/src/main/docs/quickfix-component.adoc b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
index 7b09d03..aa0f021 100644
--- a/components/camel-quickfix/src/main/docs/quickfix-component.adoc
+++ b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
@@ -1,8 +1,6 @@
-# QuickFix Component
+## QuickFix Component
 [[ConfluenceContent]]
-[[Quickfix-QuickFIXJComponent]]
-QuickFIX/J Component
-~~~~~~~~~~~~~~~~~~~~
+### QuickFIX/J Component
 
 The *quickfix* component adapts the
 http://www.quickfixj.org/[QuickFIX/J] FIX engine for using in Camel .
@@ -32,9 +30,7 @@ for this component:
 </dependency>
 ----
 
-[[Quickfix-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
@@ -69,9 +65,7 @@ quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange
 quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange&lazyCreateEngine=true
 ----
 
-[[Quickfix-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
 
 FIX sessions are endpoints for the *quickfix* component. An endpoint URI
 may specify a single session or all sessions managed by a specific
@@ -87,9 +81,7 @@ include the session-related fields in the FIX message being sent. If a
 session is specified in the URI then the component will automatically
 inject the session-related fields into the FIX message.
 
-[[Quickfix-Options]]
-Options
-~~~~~~~
+### Options
 
 // component options: START
 The QuickFix component supports 5 options which are listed below.
@@ -127,9 +119,7 @@ The QuickFix component supports 7 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[Quickfix-ExchangeFormat]]
-Exchange Format
-^^^^^^^^^^^^^^^
+### Exchange Format
 
 The exchange headers include information to help with exchange
 filtering, routing and other processing. The following headers are
@@ -157,9 +147,7 @@ dictionary to parse certain types of messages (with repeating groups,
 for example). By injecting a DataDictionary header in the route after
 receiving a message string, the FIX engine can properly parse the data.
 
-[[Quickfix-QuickFIXJConfigurationExtensions]]
-QuickFIX/J Configuration Extensions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### QuickFIX/J Configuration Extensions
 
 When using QuickFIX/J directly, one typically writes code to create
 instances of logging adapters, message stores and communication
@@ -174,9 +162,7 @@ QuickFIX/J configuration, see the
 http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html[QFJ
 user manual].
 
-[[Quickfix-CommunicationConnectors]]
-Communication Connectors
-++++++++++++++++++++++++
+#### Communication Connectors
 
 When the component detects an initiator or acceptor session setting in
 the QuickFIX/J configuration file it will automatically create the
@@ -205,9 +191,7 @@ and must be placed in the settings default section.
 `ThreadedSocketAcceptor`
 |=======================================================================
 
-[[Quickfix-Logging]]
-Logging
-+++++++
+#### Logging
 
 The QuickFIX/J logger implementation can be specified by including the
 following settings in the default section of the configuration file. The
@@ -234,9 +218,7 @@ will cause this log to be used.
 |`JdbcDriver` |Use a `JdbcLog`
 |=======================================================================
 
-[[Quickfix-MessageStore]]
-Message Store
-+++++++++++++
+#### Message Store
 
 The QuickFIX/J message store implementation can be specified by
 including the following settings in the default section of the
@@ -255,18 +237,14 @@ QuickFIX/J settings file.
 |`SleepycatDatabaseDir` |Use a `SleepcatStore`
 |=============================================
 
-[[Quickfix-MessageFactory]]
-Message Factory
-+++++++++++++++
+#### Message Factory
 
 A message factory is used to construct domain objects from raw FIX
 messages. The default message factory is `DefaultMessageFactory`.
 However, advanced applications may require a custom message factory.
 This can be set on the QuickFIX/J component.
 
-[[Quickfix-JMX]]
-JMX
-+++
+#### JMX
 
 [width="100%",cols="10%,90%",options="header",]
 |============================================
@@ -274,9 +252,7 @@ JMX
 |`UseJmx` |if `Y`, then enable QuickFIX/J JMX
 |============================================
 
-[[Quickfix-OtherDefaults]]
-Other Defaults
-++++++++++++++
+#### Other Defaults
 
 The component provides some default settings for what are normally
 required settings in QuickFIX/J configuration files. `SessionStartTime`
@@ -284,9 +260,7 @@ and `SessionEndTime` default to "00:00:00", meaning the session will not
 be automatically started and stopped. The `HeartBtInt` (heartbeat
 interval) defaults to 30 seconds.
 
-[[Quickfix-MinimalInitiatorConfigurationExample]]
-Minimal Initiator Configuration Example
-+++++++++++++++++++++++++++++++++++++++
+#### Minimal Initiator Configuration Example
 
 [source]
 ----
@@ -297,9 +271,7 @@ SenderCompID=YOUR_SENDER
 TargetCompID=YOUR_TARGET
 ----
 
-[[Quickfix-UsingtheInOutMessageExchangePattern]]
-Using the InOut Message Exchange Pattern
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the InOut Message Exchange Pattern
 
 *Camel 2.8+*
 
@@ -311,9 +283,7 @@ be a single request message and single reply message to the request.
 Examples include an
 OrderStatusRequest message and UserRequest.
 
-[[Quickfix-ImplementingInOutExchangesforConsumers]]
-Implementing InOut Exchanges for Consumers
-++++++++++++++++++++++++++++++++++++++++++
+#### Implementing InOut Exchanges for Consumers
 
 Add "exchangePattern=InOut" to the QuickFIX/J enpoint URI. The
 `MessageOrderStatusService` in
@@ -329,9 +299,7 @@ to the requestor session.
         .bean(new MarketOrderStatusService());
 ----
 
-[[Quickfix-ImplementingInOutExchangesforProducers]]
-Implementing InOut Exchanges for Producers
-++++++++++++++++++++++++++++++++++++++++++
+#### Implementing InOut Exchanges for Producers
 
 For producers, sending a message will block until a reply is received or
 a timeout occurs. There
@@ -367,9 +335,7 @@ exchange.setProperty(QuickfixjProducer.CORRELATION_CRITERIA_KEY,
         .withField(OrderID.FIELD, request.getString(OrderID.FIELD)));
 ----
 
-[[Quickfix-Example]]
-Example
-+++++++
+#### Example
 
 The source code contains an example called `RequestReplyExample` that
 demonstrates the InOut exchanges
@@ -385,9 +351,7 @@ provided as the web response.
 The Spring configuration have changed from Camel 2.9 onwards. See
 further below for example.
 
-[[Quickfix-SpringConfiguration]]
-Spring Configuration
-^^^^^^^^^^^^^^^^^^^^
+### Spring Configuration
 
 *Camel 2.6 - 2.8.x*
 
@@ -462,9 +426,7 @@ settings for both sessions.
 include::../../test/resources/org/apache/camel/component/quickfixj/QuickfixjSpringTest-context.xml[tags=e1]
 ----
 
-[[Quickfix-Exceptionhandling]]
-Exception handling
-^^^^^^^^^^^^^^^^^^
+### Exception handling
 
 QuickFIX/J behavior can be modified if certain exceptions are thrown
 during processing of a message. If a `RejectLogon` exception is thrown
@@ -481,9 +443,7 @@ being processed __synchronously__. If it is processed asynchronously (on
 another thread), the FIX engine will immediately send the unmodified
 outgoing message when it's callback method returns.
 
-[[Quickfix-FIXSequenceNumberManagement]]
-FIX Sequence Number Management
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### FIX Sequence Number Management
 
 If an application exception is thrown during _synchronous_ exchange
 processing, this will cause QuickFIX/J to not increment incoming FIX
@@ -508,9 +468,7 @@ sending messages.
 See the FIX protocol specifications and the QuickFIX/J documentation for
 more details about FIX sequence number management.
 
-[[Quickfix-RouteExamples]]
-Route Examples
-^^^^^^^^^^^^^^
+### Route Examples
 
 Several examples are included in the QuickFIX/J component source code
 (test subdirectories). One of these examples implements a trival trade
@@ -546,9 +504,7 @@ from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:TRADER->MARKET").
     bean(new MyTradeExecutionProcessor());
 ----
 
-[[Quickfix-QuickFIXJComponentPriortoCamel2.5]]
-QuickFIX/J Component Prior to Camel 2.5
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### QuickFIX/J Component Prior to Camel 2.5
 
 The *quickfix* component is an implementation of the
 http://www.quickfixj.org/[QuickFIX/J] engine for Java . This engine
@@ -559,9 +515,7 @@ standard.
 *Note:* The component can be used to send/receives messages to a FIX
 server.
 
-[[Quickfix-URIformat.1]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
@@ -581,9 +535,7 @@ The quickfix-server endpoint must be used to receive from FIX server FIX
 messages and quickfix-client endpoint in the case that you want to send
 messages to a FIX gateway.
 
-[[Quickfix-Exchangedataformat]]
-Exchange data format
-^^^^^^^^^^^^^^^^^^^^
+### Exchange data format
 
 The QuickFIX/J engine is like CXF component a messaging bus using MINA
 as protocol layer to create the socket connection with the FIX engine
@@ -602,9 +554,7 @@ dataformat] to transform the FIX message into your own java POJO
 When a message must be send to QuickFix, then you must create a
 QuickFix.Message instance.
 
-[[Quickfix-Lazycreatingengines]]
-Lazy creating engines
-^^^^^^^^^^^^^^^^^^^^^
+### Lazy creating engines
 
 From *Camel 2.12.3* onwards, you can configure the QuickFixComponent to
 lazy create and start the engines, which then only start these
@@ -612,9 +562,7 @@ on-demand. For example you can use this when you have multiple Camel
 applications in a cluster with master/slaves. And want the slaves to be
 standby.
 
-[[Quickfix-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 Direction : to FIX gateway
 
@@ -638,11 +586,9 @@ Direction : from FIX gateway
 </route>
 ----
 
-[[Quickfix-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
index 15e99e4..cf8a122 100644
--- a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
+++ b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
@@ -1,4 +1,4 @@
-# RabbitMQ Component
+## RabbitMQ Component
 
 *Available as of Camel 2.12*
 
@@ -20,9 +20,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[RabbitMQ-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------------
@@ -35,9 +33,7 @@ RabbitMQ client default (5672). The exchange name determines which
 exchange produced messages will sent to. In the case of consumers, the
 exchange name determines which exchange the queue will bind to.
 
-[[RabbitMQ-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -122,9 +118,7 @@ See
 http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html[http://www.rabbitmq.com/releases/rabbitmq-java-client/current-javadoc/com/rabbitmq/client/ConnectionFactory.html]
 and the AMQP specification for more information on connection options.
 
-[[RabbitMQ-Customconnectionfactory]]
-Custom connection factory
-~~~~~~~~~~~~~~~~~~~~~~~~~
+### Custom connection factory
 
 [source,xml]
 ----------------------------------------------------------------------------------------
@@ -210,18 +204,14 @@ producer will also set the headers for downstream processors once the
 exchange has taken place. Any headers set prior to production that the
 producer sets will be overriden.
 
-[[RabbitMQ-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 The component will use the camel exchange in body as the rabbit mq
 message body. The camel exchange in object must be convertible to a byte
 array. Otherwise the producer will throw an exception of unsupported
 body type.
 
-[[RabbitMQ-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 To receive messages from a queue that is bound to an exchange A with the
 routing key B,
@@ -246,12 +236,9 @@ To send messages to an exchange called C
 ...to("rabbitmq://localhost/B")
 -------------------------------
 
-[[RabbitMQ-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-restlet/src/main/docs/restlet-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-restlet/src/main/docs/restlet-component.adoc b/components/camel-restlet/src/main/docs/restlet-component.adoc
index 55d6abe..99e7c47 100644
--- a/components/camel-restlet/src/main/docs/restlet-component.adoc
+++ b/components/camel-restlet/src/main/docs/restlet-component.adoc
@@ -1,4 +1,4 @@
-# Restlet Component
+## Restlet Component
 
 The *Restlet* component provides http://www.restlet.org[Restlet] based
 link:endpoint.html[endpoints] for consuming and producing RESTful
@@ -17,9 +17,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Restlet-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------
@@ -57,9 +55,7 @@ synchronous=true as option on the endpoint uris, Or set it on the
 RestletComponent as a global option so all endpoints inherit this
 option.
 
-[[Restlet-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -133,9 +129,7 @@ The Restlet component supports 22 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Restlet-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -185,21 +179,15 @@ create responses using the API from Restlet. See examples below.
 the List of CacheDirective of Restlet from the camel message header.
 |=======================================================================
 
-[[Restlet-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 Camel will store the restlet response from the external server on the
 OUT body. All headers from the IN message will be copied to the OUT
 message, so that headers are preserved during routing.
 
-[[Restlet-Samples]]
-Samples
-^^^^^^^
+### Samples
 
-[[Restlet-RestletEndpointwithAuthentication]]
-Restlet Endpoint with Authentication
-++++++++++++++++++++++++++++++++++++
+#### Restlet Endpoint with Authentication
 
 The following route starts a `restlet` consumer endpoint that listens
 for `POST` requests on http://localhost:8080. The processor creates a
@@ -237,9 +225,7 @@ The sample client gets a response like the following:
 received [<order foo='1'/>] as an order id = 89531
 --------------------------------------------------
 
-[[Restlet-SinglerestletendpointtoservicemultiplemethodsandURItemplates]]
-Single restlet endpoint to service multiple methods and URI templates
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Single restlet endpoint to service multiple methods and URI templates
 
 It is possible to create a single route to service multiple HTTP methods
 using the `restletMethods` option. This snippet also shows how to
@@ -264,9 +250,7 @@ The `restletUriPatterns=#uriTemplates` option references the
 </util:list>
 --------------------------------------------------------
 
-[[Restlet-UsingRestletAPItopopulateresponse]]
-Using Restlet API to populate response
-++++++++++++++++++++++++++++++++++++++
+#### Using Restlet API to populate response
 
 *Available as of Camel 2.8*
 
@@ -277,9 +261,7 @@ the response from an inlined Camel link:processor.html[Processor]:
 
 *Generating response using Restlet Response API*
 
-[[Restlet-Configuringmaxthreadsoncomponent]]
-Configuring max threads on component
-++++++++++++++++++++++++++++++++++++
+#### Configuring max threads on component
 
 To configure the max threads options you must do this on the component,
 such as:
@@ -291,9 +273,7 @@ such as:
 </bean>
 -------------------------------------------------------------------------------
 
-[[Restlet-UsingtheRestletservletwithinawebapp]]
-Using the Restlet servlet within a webapp
-+++++++++++++++++++++++++++++++++++++++++
+#### Using the Restlet servlet within a webapp
 
 *Available as of Camel 2.8* +
  There are
@@ -386,12 +366,9 @@ well:
 </repository>
 --------------------------------------------------
 
-[[Restlet-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rmi/src/main/docs/rmi-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rmi/src/main/docs/rmi-component.adoc b/components/camel-rmi/src/main/docs/rmi-component.adoc
index 83f6b5c..f550f54 100644
--- a/components/camel-rmi/src/main/docs/rmi-component.adoc
+++ b/components/camel-rmi/src/main/docs/rmi-component.adoc
@@ -1,4 +1,4 @@
-# RMI Component
+## RMI Component
 
 The *rmi:* component binds link:exchange.html[Exchange]s to the RMI
 protocol (JRMP).
@@ -24,9 +24,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[RMI-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------------------------------------
@@ -43,9 +41,7 @@ rmi://localhost:1099/path/to/service
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[RMI-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -75,9 +71,7 @@ The RMI component supports 9 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[RMI-Using]]
-Using
-^^^^^
+### Using
 
 To call out to an existing RMI service registered in an RMI registry,
 create a route similar to the following:
@@ -110,12 +104,9 @@ In XML DSL you can do as follows from *Camel 2.7* onwards:
     </camel:route>
 ------------------------------------------------------------------------------------------------------------------------
 
-[[RMI-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-routebox/src/main/docs/routebox-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-routebox/src/main/docs/routebox-component.adoc b/components/camel-routebox/src/main/docs/routebox-component.adoc
index 23139f7..12a61fc 100644
--- a/components/camel-routebox/src/main/docs/routebox-component.adoc
+++ b/components/camel-routebox/src/main/docs/routebox-component.adoc
@@ -1,4 +1,4 @@
-# RouteBox Component
+## RouteBox Component
 
 *Available as of Camel 2.6*
 
@@ -49,9 +49,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Routebox-TheneedforaCamelRouteboxendpoint]]
-The need for a Camel Routebox endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### The need for a Camel Routebox endpoint
 
 The routebox component is designed to ease integration in complex
 environments needing
@@ -87,9 +85,7 @@ delegate requests to inner fine grained routes to achieve a specific
 integration objective, collect the final inner result, and continue to
 progress to the next step along the coarse-grained route.
 
-[[Routebox-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
@@ -99,9 +95,7 @@ routebox:routeboxname[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Routebox-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -140,18 +134,14 @@ The RouteBox component supports 18 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Routebox-SendingReceivingMessagestofromtheroutebox]]
-Sending/Receiving Messages to/from the routebox
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending/Receiving Messages to/from the routebox
 
 Before sending requests it is necessary to properly configure the
 routebox by loading the required URI parameters into the Registry as
 shown below. In the case of Spring, if the necessary beans are declared
 correctly, the registry is automatically populated by Camel.
 
-[[Routebox-Step1:LoadinginnerroutedetailsintotheRegistry]]
-Step 1: Loading inner route details into the Registry
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Step 1: Loading inner route details into the Registry
 
 [source,java]
 ------------------------------------------------------------------------------------------------------------
@@ -188,9 +178,7 @@ private JndiRegistry createInnerRegistry() throws Exception {
 CamelContext context = new DefaultCamelContext(createRegistry());
 ------------------------------------------------------------------------------------------------------------
 
-[[Routebox-Step2:OptionalyusingaDispatchStrategyinsteadofaDispatchMap]]
-Step 2: Optionaly using a Dispatch Strategy instead of a Dispatch Map
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Step 2: Optionaly using a Dispatch Strategy instead of a Dispatch Map
 
 Using a dispatch Strategy involves implementing the interface
 _org.apache.camel.component.routebox.strategy.RouteboxDispatchStrategy_
@@ -220,9 +208,7 @@ public class SimpleRouteDispatchStrategy implements RouteboxDispatchStrategy {
 }
 -------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[Routebox-Step2:Launchingarouteboxconsumer]]
-Step 2: Launching a routebox consumer
-+++++++++++++++++++++++++++++++++++++
+#### Step 2: Launching a routebox consumer
 
 When creating a route consumer, note that the # entries in the
 routeboxUri are matched to the created inner registry, routebuilder list
@@ -252,9 +238,7 @@ public void testRouteboxRequests() throws Exception {
 }
 ----------------------------------------------------------------------------------------------------------------------
 
-[[Routebox-Step3:Usingarouteboxproducer]]
-Step 3: Using a routebox producer
-+++++++++++++++++++++++++++++++++
+#### Step 3: Using a routebox producer
 
 When sending requests to the routebox, it is not necessary for producers
 do not need to know the inner route endpoint URI and they can simply
@@ -276,4 +260,4 @@ from ("direct:sendToMapBasedRoutebox")
     .setHeader("ROUTE_DISPATCH_KEY", constant("addToCatalog"))
     .to("routebox:multipleRoutes?innerRegistry=#registry&routeBuilders=#routes&dispatchMap=#map")
     .to("log:Routes operation performed?showAll=true");
------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rss/src/main/docs/rss-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rss/src/main/docs/rss-component.adoc b/components/camel-rss/src/main/docs/rss-component.adoc
index 79e56c1..460170a 100644
--- a/components/camel-rss/src/main/docs/rss-component.adoc
+++ b/components/camel-rss/src/main/docs/rss-component.adoc
@@ -1,4 +1,4 @@
-# RSS Component
+## RSS Component
 
 The *rss:* component is used for polling RSS feeds. Camel will default
 poll the feed every 60th seconds.
@@ -24,9 +24,7 @@ version] of http://rometools.github.io/rome/[ROME] hosted on ServiceMix
 to solve some OSGi https://issues.apache.org/jira/browse/SMX4-510[class
 loading issues].
 
-[[RSS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------
@@ -38,9 +36,7 @@ Where `rssUri` is the URI to the RSS feed to poll.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[RSS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -89,9 +85,7 @@ The RSS component supports 28 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[RSS-Exchangedatatypes]]
-Exchange data types
-^^^^^^^^^^^^^^^^^^^
+### Exchange data types
 
 Camel initializes the In body on the Exchange with a ROME `SyndFeed`.
 Depending on the value of the `splitEntries` flag, Camel returns either
@@ -106,9 +100,7 @@ a `SyndFeed` with one `SyndEntry` or a `java.util.List` of `SyndEntrys`.
 |`splitEntries` |`false` |The entire list of entries from the current feed is set in the exchange.
 |=======================================================================
 
-[[RSS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -117,9 +109,7 @@ Message Headers
 |`CamelRssFeed` |The entire `SyncFeed` object.
 |=======================================================================
 
-[[RSS-RSSDataformat]]
-RSS Dataformat
-^^^^^^^^^^^^^^
+### RSS Dataformat
 
 The RSS component ships with an RSS dataformat that can be used to
 convert between String (as XML) and ROME RSS model objects.
@@ -140,9 +130,7 @@ understand them as well, for example if the feed uses `alt=rss`, then
 you can for example do
 `from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss");`
 
-[[RSS-Filteringentries]]
-Filtering entries
-^^^^^^^^^^^^^^^^^
+### Filtering entries
 
 You can filter out entries quite easily using XPath, as shown in the
 data format section above. You can also exploit Camel's
@@ -152,14 +140,11 @@ would be:
 
 The custom bean for this would be:
 
-[[RSS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:atom.html[Atom]
-
+* link:atom.html[Atom]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-rss/src/main/docs/rss-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-rss/src/main/docs/rss-dataformat.adoc b/components/camel-rss/src/main/docs/rss-dataformat.adoc
index b43e2cc..1275169 100644
--- a/components/camel-rss/src/main/docs/rss-dataformat.adoc
+++ b/components/camel-rss/src/main/docs/rss-dataformat.adoc
@@ -1,4 +1,4 @@
-# RSS DataFormat
+## RSS DataFormat
 
 The RSS component ships with an RSS dataformat that can be used to
 convert between String (as XML) and ROME RSS model objects.
@@ -18,9 +18,7 @@ understand them as well, for example if the feed uses `alt=rss`, then
 you can for example do
 `from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss");`
 
-[[RSS-RSSDataformat-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The RSS dataformat supports 1 options which are listed below.
@@ -34,6 +32,4 @@ The RSS dataformat supports 1 options which are listed below.
 | contentTypeHeader | false | Boolean | Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML or application/json for data formats marshalling to JSon etc.
 |=======================================================================
 {% endraw %}
-// dataformat options: END
-
-
+// dataformat options: END
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
index b68ff28..b8b2657 100644
--- a/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
+++ b/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc
@@ -1,4 +1,4 @@
-# Salesforce Component
+## Salesforce Component
 
 *Available as of Camel 2.12*
 
@@ -20,9 +20,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Salesforce-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a salesforce component is as follows
 
@@ -34,18 +32,14 @@ salesforce:topic?options
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Salesforce-SupportedSalesforceAPIs]]
-Supported Salesforce APIs
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Supported Salesforce APIs
 
 The component supports the following Salesforce APIs
 
 Producer endpoints can use the following APIs. Most of the APIs process
 one record at a time, the Query API can retrieve multiple Records.
 
-[[Salesforce-RestAPI]]
-Rest API
-++++++++
+#### Rest API
 
 * getVersions - Gets supported Salesforce REST API versions
 * getResources - Gets available Salesforce REST Resource endpoints
@@ -86,9 +80,7 @@ list of errors while creating the new object.
     ...to("salesforce:upsertSObject?sObjectIdName=Name")...
 -----------------------------------------------------------
 
-[[Salesforce-RestBulkAPI]]
-Rest Bulk API
-+++++++++++++
+#### Rest Bulk API
 
 Producer endpoints can use the following APIs. All Job data formats,
 i.e. xml, csv, zip/xml, and zip/csv are supported.  +
@@ -124,9 +116,7 @@ error.
     ...to("salesforce:createBatchJob")..
 ----------------------------------------
 
-[[Salesforce-RestStreamingAPI]]
-Rest Streaming API
-++++++++++++++++++
+#### Rest Streaming API
 
 Consumer endpoints can use the following sytax for streaming endpoints
 to receive Salesforce notifications on create/update.
@@ -145,13 +135,9 @@ To subscribe to an existing topic
     from("salesforce:CamelTestTopic&sObjectName=Merchandise__c")...
 -------------------------------------------------------------------
 
-[[Salesforce-Examples]]
-Examples
-~~~~~~~~
+### Examples
 
-[[Salesforce-UploadingadocumenttoaContentWorkspace]]
-Uploading a document to a ContentWorkspace
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Uploading a document to a ContentWorkspace
 
 Create the ContentVersion in Java, using a Processor instance:
 
@@ -191,9 +177,7 @@ Give the output from the processor to the Salesforce component:
         .to("salesforce:createSObject");
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-LimitsAPI]]
-Using Salesforce Limits API
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Limits API
 
 With `salesforce:limits` operation you can fetch of API limits from Salesforce and then act upon that data received.
 The result of `salesforce:limits` operation is mapped to `org.apache.camel.component.salesforce.api.dto.Limits`
@@ -221,9 +205,7 @@ from("direct:querySalesforce")
     .endChoice()
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-Approval]]
-Working with approvals
-^^^^^^^^^^^^^^^^^^^^^^
+### Working with approvals
 
 All the properties are named exactly the same as in the Salesforce REST API prefixed with `approval.`. You can set
 approval properties by setting `approval.PropertyName` of the Endpoint these will be used as template -- meaning
@@ -268,9 +250,7 @@ body.put("nextApproverIds", userId);
 final ApprovalResult result = template.requestBody("direct:example1", body, ApprovalResult.class);
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-RecentItems]]
-Using Salesforce Recent Items API
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Recent Items API
 
 To fetch the recent items use `salesforce:recent` operation. This operation returns an `java.util.List` of
 `org.apache.camel.component.salesforce.api.dto.RecentItem` objects (`List<RecentItem>`) that in turn contain
@@ -285,8 +265,7 @@ from("direct:fetchRecentItems")
             .log("${body.name} at ${body.attributes.url}");
 -----------------------------------------------------------------------------------------------------
 
-Working with approvals
-^^^^^^^^^^^^^^^^^^^^^^
+### Working with approvals
 
 All the properties are named exactly the same as in the Salesforce REST API prefixed with `approval.`. You can set
 approval properties by setting `approval.PropertyName` of the Endpoint these will be used as template -- meaning
@@ -331,9 +310,7 @@ body.put("nextApproverIds", userId);
 final ApprovalResult result = template.requestBody("direct:example1", body, ApprovalResult.class);
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-CompositeAPI-Tree]]
-Using Salesforce Composite API to submit SObject tree
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Composite API to submit SObject tree
 
 To create up to 200 records including parent-child relationships use `salesforce:composite-tree` operation. This
 requires an instance of `org.apache.camel.component.salesforce.api.dto.composite.SObjectTree` in the input
@@ -375,9 +352,7 @@ final List<SObjectNode> succeeded = result.get(false);
 final String firstId = succeeded.get(0).getId();
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-CompositeAPI-Batch]]
-Using Salesforce Composite API to submit multiple requests in a batch
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Using Salesforce Composite API to submit multiple requests in a batch
 The Composite API batch operation (`composite-batch`) allows you to accumulate multiple requests in a batch and then
 submit them in one go, saving the round trip cost of multiple individual requests. Each response is then received in a
 list of responses with the order perserved, so that the n-th requests response is in the n-th place of the response.
@@ -434,16 +409,12 @@ final Object updateResultData = deleteResult.getResult(); // probably null
 
 -----------------------------------------------------------------------------------------------------
 
-[[Salesforce-CamelSalesforceMavenPlugin]]
-Camel Salesforce Maven Plugin
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Camel Salesforce Maven Plugin
 
 This Maven plugin generates DTOs for the Camel
 link:salesforce.html[Salesforce].
 
-[[Salesforce-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -560,12 +531,9 @@ The generated DTOs use Jackson and XStream annotations. All Salesforce
 field types are supported. Date and time fields are mapped to Joda
 DateTime, and picklist fields are mapped to generated Java Enumerations.
 
-[[Salesforce-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc b/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
index 3720b4d..b594cb1 100644
--- a/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
+++ b/components/camel-sap-netweaver/src/main/docs/sap-netweaver-component.adoc
@@ -1,4 +1,4 @@
-# SAP NetWeaver Component
+## SAP NetWeaver Component
 
 *Available as of Camel 2.12*
 
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[SAPNetWeaver-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a sap netweaver gateway component is as follows
 
@@ -35,9 +33,7 @@ sap-netweaver:https://host:8080/path?username=foo&password=secret
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SAPNetWeaver-Prerequisites]]
-Prerequisites
-^^^^^^^^^^^^^
+### Prerequisites
 
 You would need to have an account to the SAP NetWeaver system to be able
 to leverage this component. SAP provides a
@@ -47,9 +43,7 @@ requires for an account.
 This component uses the basic authentication scheme for logging into SAP
 NetWeaver.
 
-[[SAPNetWeaver-Componentandendpointoptions]]
-SAPNetWeaver options
-^^^^^^^^^^^^^^^^^^^^
+### SAPNetWeaver options
 
 
 // component options: START
@@ -77,9 +71,7 @@ The SAP NetWeaver component supports 7 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[SAPNetWeaver-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The following headers can be used by the producer.
 
@@ -92,9 +84,7 @@ http://msdn.microsoft.com/en-us/library/cc956153.aspx[MS ADO.Net Data
 Service] format.
 |=======================================================================
 
-[[SAPNetWeaver-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 This example is using the flight demo example from SAP, which is
 available online over the internet
@@ -176,14 +166,11 @@ Destination city: SAN FRANCISCO
 Destination airport: SFO
 -------------------------------
 
-[[SAPNetWeaver-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:http.html[HTTP]
-
+* link:http.html[HTTP]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-saxon/src/main/docs/xquery-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-saxon/src/main/docs/xquery-component.adoc b/components/camel-saxon/src/main/docs/xquery-component.adoc
index ba4730b..4f62111 100644
--- a/components/camel-saxon/src/main/docs/xquery-component.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-component.adoc
@@ -1,4 +1,4 @@
-# XQuery Component
+## XQuery Component
 
 Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
 link:expression.html[Expression] or link:predicate.html[Predicate] to be
@@ -8,9 +8,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List].
 
-[[XQuery-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -74,9 +72,7 @@ The XQuery component supports 31 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[XQuery-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 [source,java]
 ---------------------------
@@ -96,9 +92,7 @@ from("direct:start").
   recipientList().xquery("concat('mock:foo.', /person/@city)", String.class);
 -----------------------------------------------------------------------------
 
-[[XQuery-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 The IN message body will be set as the `contextItem`. Besides this these
 Variables is also added as parameters:
@@ -125,9 +119,7 @@ with they own key name, for instance if there is an IN header with the
 key name *foo* then its added as *foo*.
 |=======================================================================
 
-[[XQuery-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
 
 If you prefer to configure your routes in your link:spring.html[Spring]
 XML file then you can use XPath expressions as follows
@@ -165,9 +157,7 @@ attribute:
     <xquery type="java.lang.String">concat('mock:foo.', /person/@city)</xquery>
 -------------------------------------------------------------------------------
 
-[[XQuery-UsingXQueryastransformation]]
-Using XQuery as transformation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as transformation
 
 We can do a message translation using transform or setBody in the route,
 as shown below:
@@ -190,9 +180,7 @@ from("direct:start").
 
 Â 
 
-[[XQuery-UsingXQueryasanendpoint]]
-Using XQuery as an endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as an endpoint
 
 Sometimes an XQuery expression can be quite large; it can essentally be
 used for link:templating.html[Templating]. So you may want to use an
@@ -213,9 +201,7 @@ The following example shows how to take a message of an ActiveMQ queue
   </camelContext>
 -------------------------------------------------------------------------
 
-[[XQuery-Examples.1]]
-Examples
-^^^^^^^^
+### Examples
 
 Here is a simple
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java/org/apache/camel/builder/saxon/XQueryFilterTest.java[example]
@@ -227,9 +213,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java
 uses XQuery with namespaces as a predicate in a
 link:message-filter.html[Message Filter]
 
-[[XQuery-LearningXQuery]]
-Learning XQuery
-^^^^^^^^^^^^^^^
+### Learning XQuery
 
 XQuery is a very powerful language for querying, searching, sorting and
 returning XML. For help learning XQuery try these tutorials
@@ -242,9 +226,7 @@ Tutorial]
 You might also find the http://www.w3.org/TR/xpath-functions/[XQuery
 function reference] useful
 
-[[XQuery-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -258,9 +240,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").xquery("resource:classpath:myxquery.txt", String.class)
 ------------------------------------------------------------------------------
 
-[[XQuery-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use XQuery in your camel routes you need to add the a dependency on
 *camel-saxon* which implements the XQuery language.
@@ -276,4 +256,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-saxon</artifactId>
   <version>x.x.x</version>
 </dependency>
---------------------------------------
+--------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-saxon/src/main/docs/xquery-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-saxon/src/main/docs/xquery-language.adoc b/components/camel-saxon/src/main/docs/xquery-language.adoc
index 852c9f2..4f31903 100644
--- a/components/camel-saxon/src/main/docs/xquery-language.adoc
+++ b/components/camel-saxon/src/main/docs/xquery-language.adoc
@@ -1,4 +1,4 @@
-# XQuery Language
+## XQuery Language
 
 Camel supports http://www.w3.org/TR/xquery/[XQuery] to allow an
 link:expression.html[Expression] or link:predicate.html[Predicate] to be
@@ -8,9 +8,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List].
 
-[[XQuery-Options]]
-XQuery Language options
-^^^^^^^^^^^^^^^^^^^^^^^
+### XQuery Language options
 
 // language options: START
 The XQuery language supports 3 options which are listed below.
@@ -28,9 +26,7 @@ The XQuery language supports 3 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[XQuery-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 [source,java]
 ---------------------------
@@ -50,9 +46,7 @@ from("direct:start").
   recipientList().xquery("concat('mock:foo.', /person/@city)", String.class);
 -----------------------------------------------------------------------------
 
-[[XQuery-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 The IN message body will be set as the `contextItem`. Besides this these
 Variables is also added as parameters:
@@ -79,9 +73,7 @@ with they own key name, for instance if there is an IN header with the
 key name *foo* then its added as *foo*.
 |=======================================================================
 
-[[XQuery-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
 
 If you prefer to configure your routes in your link:spring.html[Spring]
 XML file then you can use XPath expressions as follows
@@ -119,9 +111,7 @@ attribute:
     <xquery type="java.lang.String">concat('mock:foo.', /person/@city)</xquery>
 -------------------------------------------------------------------------------
 
-[[XQuery-UsingXQueryastransformation]]
-Using XQuery as transformation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as transformation
 
 We can do a message translation using transform or setBody in the route,
 as shown below:
@@ -144,9 +134,7 @@ from("direct:start").
 
 Â 
 
-[[XQuery-UsingXQueryasanendpoint]]
-Using XQuery as an endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using XQuery as an endpoint
 
 Sometimes an XQuery expression can be quite large; it can essentally be
 used for link:templating.html[Templating]. So you may want to use an
@@ -167,9 +155,7 @@ The following example shows how to take a message of an ActiveMQ queue
   </camelContext>
 -------------------------------------------------------------------------
 
-[[XQuery-Examples.1]]
-Examples
-^^^^^^^^
+### Examples
 
 Here is a simple
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java/org/apache/camel/builder/saxon/XQueryFilterTest.java[example]
@@ -181,9 +167,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-saxon/src/test/java
 uses XQuery with namespaces as a predicate in a
 link:message-filter.html[Message Filter]
 
-[[XQuery-LearningXQuery]]
-Learning XQuery
-^^^^^^^^^^^^^^^
+### Learning XQuery
 
 XQuery is a very powerful language for querying, searching, sorting and
 returning XML. For help learning XQuery try these tutorials
@@ -196,9 +180,7 @@ Tutorial]
 You might also find the http://www.w3.org/TR/xpath-functions/[XQuery
 function reference] useful
 
-[[XQuery-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -212,9 +194,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").xquery("resource:classpath:myxquery.txt", String.class)
 ------------------------------------------------------------------------------
 
-[[XQuery-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use XQuery in your camel routes you need to add the a dependency on
 *camel-saxon* which implements the XQuery language.
@@ -230,4 +210,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-saxon</artifactId>
   <version>x.x.x</version>
 </dependency>
---------------------------------------
+--------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-schematron/src/main/docs/schematron-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-schematron/src/main/docs/schematron-component.adoc b/components/camel-schematron/src/main/docs/schematron-component.adoc
index 2de9dfa..bb5c23b 100644
--- a/components/camel-schematron/src/main/docs/schematron-component.adoc
+++ b/components/camel-schematron/src/main/docs/schematron-component.adoc
@@ -1,4 +1,4 @@
-# Schematron Component
+## Schematron Component
 
 *Available as of Camel 2.14*
 
@@ -17,18 +17,14 @@ written in a way that Schematron rules are loaded at the start of the
 endpoint (only once) this is to minimise the overhead of instantiating a
 Java Templates object representing the rules.
 
-[[Schematron-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------
 schematron://path?[options]
 ---------------------------
 
-[[Schematron-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
 
 
 // component options: START
@@ -58,9 +54,7 @@ The Schematron component supports 5 endpoint options which are listed below:
 
 
 
-[[Schematron-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -71,9 +65,7 @@ Headers
 |CamelSchematronValidationReport |The schematrion report body in XML format. See an example below |String |IN
 |=======================================================================
 
-[[Schematron-URIandpathsyntax]]
-URI and path syntax
-^^^^^^^^^^^^^^^^^^^
+### URI and path syntax
 
 The following example shows how to invoke the schematron processor in
 Java DSL. The schematron rules file is sourced from the class path:
@@ -124,9 +116,7 @@ an update, all you need is to restart the route or the component. No
 harm in storing these rules in the class path though, but you will have
 to build and deploy the component to pick up the changes.
 
-[[Schematron-Schematronrulesandreportsamples]]
-Schematron rules and report samples
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Schematron rules and report samples
 
 Here is an example of schematron rules
 
@@ -175,5 +165,4 @@ TIP: *Useful Links and resources*
 to Schematron] by Mulleberry technologies. An excellent document in PDF
 to get you started on Schematron.
 * http://www.schematron.com[Schematron official site]. This contains
-links to other resources
-
+links to other resources
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/javaScript-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/javaScript-language.adoc b/components/camel-script/src/main/docs/javaScript-language.adoc
index 2dc2fca..a4dfdfa 100644
--- a/components/camel-script/src/main/docs/javaScript-language.adoc
+++ b/components/camel-script/src/main/docs/javaScript-language.adoc
@@ -1,4 +1,4 @@
-# JavaScript Language
+## JavaScript Language
 
 Camel supports
 http://en.wikipedia.org/wiki/JavaScript[JavaScript/ECMAScript] among
@@ -19,9 +19,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[JavaScript-Language-options]]
-Javascript Language Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Javascript Language Options
 
 // language options: START
 The JavaScript language supports 1 options which are listed below.
@@ -37,9 +35,7 @@ The JavaScript language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[JavaScript-Example]]
-Example
-^^^^^^^
+### Example
 
 In the sample below we use JavaScript to create a
 link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -72,9 +68,7 @@ And a Spring DSL sample as well:
     </route>
 -------------------------------------------------------------------------------
 
-[[JavaScript-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
 
 The JSR-223 scripting languages ScriptContext is pre configured with the
 following attributes all set at `ENGINE_SCOPE`:
@@ -102,9 +96,7 @@ further below for example.
 See link:scripting-languages.html[Scripting Languages] for the list of
 languages with explicit DSL support.
 
-[[JavaScript-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
 
 *Available as of Camel 2.8*
 
@@ -112,9 +104,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
 header on the Camel message with the key `CamelScriptArguments`. +
  See this example:
 
-[[JavaScript-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
 
 *Available as of Camel 2.9*
 
@@ -139,9 +129,7 @@ same example is simpler:
 .setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
 -------------------------------------------------------------------------------
 
-[[JavaScript-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -155,9 +143,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
 -------------------------------------------------------------------
 
-[[JavaScript-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
 
 *Available as of Camel 2.14*
 
@@ -177,9 +163,7 @@ result = body * 2 + 1
 
 Â 
 
-[[JavaScript-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use scripting languages in your camel routes you need to add the a
 dependency on *camel-script* which integrates the JSR-223 scripting
@@ -196,4 +180,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-script</artifactId>
   <version>x.x.x</version>
 </dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/php-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/php-language.adoc b/components/camel-script/src/main/docs/php-language.adoc
index c7dcb13..d7c8a01 100644
--- a/components/camel-script/src/main/docs/php-language.adoc
+++ b/components/camel-script/src/main/docs/php-language.adoc
@@ -1,4 +1,4 @@
-# PHP Language
+## PHP Language
 
 Camel supports http://www.php.net/[PHP] among other
 link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[PHP-Language-options]]
-PHP Language Options
-^^^^^^^^^^^^^^^^^^^^
+### PHP Language Options
 
 // language options: START
 The PHP language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The PHP language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[PHP-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
 
 The JSR-223 scripting languages ScriptContext is pre configured with the
 following attributes all set at `ENGINE_SCOPE`:
@@ -66,9 +62,7 @@ further below for example.
 See link:scripting-languages.html[Scripting Languages] for the list of
 languages with explicit DSL support.
 
-[[PHP-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
 
 *Available as of Camel 2.8*
 
@@ -76,9 +70,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
 header on the Camel message with the key `CamelScriptArguments`. +
  See this example:
 
-[[PHP-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
 
 *Available as of Camel 2.9*
 
@@ -103,9 +95,7 @@ same example is simpler:
 .setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
 -------------------------------------------------------------------------------
 
-[[PHP-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -119,9 +109,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
 -------------------------------------------------------------------
 
-[[PHP-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
 
 *Available as of Camel 2.14*
 
@@ -141,9 +129,7 @@ result = body * 2 + 1
 
 Â 
 
-[[PHP-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use scripting languages in your camel routes you need to add the a
 dependency on *camel-script* which integrates the JSR-223 scripting
@@ -160,4 +146,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-script</artifactId>
   <version>x.x.x</version>
 </dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/python-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/python-language.adoc b/components/camel-script/src/main/docs/python-language.adoc
index aa4fd07..b9d26b7 100644
--- a/components/camel-script/src/main/docs/python-language.adoc
+++ b/components/camel-script/src/main/docs/python-language.adoc
@@ -1,4 +1,4 @@
-# Python Language
+## Python Language
 
 Camel supports http://www.python.org/[Python] among other
 link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[Python-Language-options]]
-Python Language Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Python Language Options
 
 // language options: START
 The Python language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The Python language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[Python-Example]]
-Example
-^^^^^^^
+### Example
 
 In the sample below we use Python to create a
 link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -71,9 +67,7 @@ And a Spring DSL sample as well:
     </route>
 -------------------------------------------------------------------
 
-[[Python-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
 
 The JSR-223 scripting languages ScriptContext is pre configured with the
 following attributes all set at `ENGINE_SCOPE`:
@@ -101,9 +95,7 @@ further below for example.
 See link:scripting-languages.html[Scripting Languages] for the list of
 languages with explicit DSL support.
 
-[[Python-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
 
 *Available as of Camel 2.8*
 
@@ -111,9 +103,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
 header on the Camel message with the key `CamelScriptArguments`. +
  See this example:
 
-[[Python-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
 
 *Available as of Camel 2.9*
 
@@ -138,9 +128,7 @@ same example is simpler:
 .setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
 -------------------------------------------------------------------------------
 
-[[Python-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -154,9 +142,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
 -------------------------------------------------------------------
 
-[[Python-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
 
 *Available as of Camel 2.14*
 
@@ -176,9 +162,7 @@ result = body * 2 + 1
 
 Â 
 
-[[Python-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use scripting languages in your camel routes you need to add the a
 dependency on *camel-script* which integrates the JSR-223 scripting
@@ -195,4 +179,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-script</artifactId>
   <version>x.x.x</version>
 </dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-script/src/main/docs/ruby-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-script/src/main/docs/ruby-language.adoc b/components/camel-script/src/main/docs/ruby-language.adoc
index 7a3e83e..6f11c00 100644
--- a/components/camel-script/src/main/docs/ruby-language.adoc
+++ b/components/camel-script/src/main/docs/ruby-language.adoc
@@ -1,4 +1,4 @@
-# Ruby Language
+## Ruby Language
 
 Camel supports http://www.ruby-lang.org/en/[Ruby] among other
 link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[Ruby-Language-options]]
-Ruby Language Options
-^^^^^^^^^^^^^^^^^^^^^
+### Ruby Language Options
 
 // language options: START
 The Ruby language supports 1 options which are listed below.
@@ -36,9 +34,7 @@ The Ruby language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[Ruby-Example]]
-Example
-^^^^^^^
+### Example
 
 In the sample below we use Ruby to create a
 link:predicate.html[Predicate] use in the route path, to route exchanges
@@ -71,9 +67,7 @@ And a Spring DSL sample as well:
     </route>
 ----------------------------------------------------------------
 
-[[Ruby-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
 
 The JSR-223 scripting languages ScriptContext is pre configured with the
 following attributes all set at `ENGINE_SCOPE`:
@@ -101,9 +95,7 @@ further below for example.
 See link:scripting-languages.html[Scripting Languages] for the list of
 languages with explicit DSL support.
 
-[[Ruby-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
 
 *Available as of Camel 2.8*
 
@@ -111,9 +103,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
 header on the Camel message with the key `CamelScriptArguments`. +
  See this example:
 
-[[Ruby-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
 
 *Available as of Camel 2.9*
 
@@ -138,9 +128,7 @@ same example is simpler:
 .setHeader("myHeader").groovy("properties.resolve(request.headers.get('foo'))")
 -------------------------------------------------------------------------------
 
-[[Ruby-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -154,9 +142,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
 -------------------------------------------------------------------
 
-[[Ruby-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
 
 *Available as of Camel 2.14*
 
@@ -176,9 +162,7 @@ result = body * 2 + 1
 
 Â 
 
-[[Ruby-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use scripting languages in your camel routes you need to add the a
 dependency on *camel-script* which integrates the JSR-223 scripting
@@ -195,4 +179,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-script</artifactId>
   <version>x.x.x</version>
 </dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-servicenow/src/main/docs/servicenow-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-servicenow/src/main/docs/servicenow-component.adoc b/components/camel-servicenow/src/main/docs/servicenow-component.adoc
index 258ec81..8ce386b 100644
--- a/components/camel-servicenow/src/main/docs/servicenow-component.adoc
+++ b/components/camel-servicenow/src/main/docs/servicenow-component.adoc
@@ -1,4 +1,4 @@
-# ServiceNow Component
+## ServiceNow Component
 
 *Available as of Camel 2.18*
 
@@ -19,18 +19,14 @@ for this component:
     </dependency>
 -------------------------------------------------
 
-[[ServiceNow-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------
     servicenow://instanceName?[options]
 ---------------------------------------
 
-[[ServiceNow-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -108,9 +104,7 @@ The ServiceNow component supports 41 endpoint options which are listed below:
 
 
 
-[[ServiceNow-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 [width="100%",cols="10%,10%,10%,10%,60%",options="header",]
 |===
@@ -263,9 +257,7 @@ NOTE: link:http://wiki.servicenow.com/index.php?title=REST_API#Available_APIs[Fu
 
 NOTE: https://docs.servicenow.com/bundle/helsinki-servicenow-platform/page/integrate/inbound-rest/reference/r_RESTResources.html[Helsinki REST API Documentation]
 
-[[ServiceNow-Usageexamples]]
-Usage examples:
-^^^^^^^^^^^^^^^
+### Usage examples:
 Â 
 {% raw %}
 [source,java]
@@ -292,4 +284,4 @@ FluentProducerTemplate.on(context)
     .to("direct:servicenow")
     .send();
 -------------------------------------------------------------------------------------------------------------------
-{% endraw %}
+{% endraw %}
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-servlet/src/main/docs/servlet-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-servlet/src/main/docs/servlet-component.adoc b/components/camel-servlet/src/main/docs/servlet-component.adoc
index bc35e2e..30209cd 100644
--- a/components/camel-servlet/src/main/docs/servlet-component.adoc
+++ b/components/camel-servlet/src/main/docs/servlet-component.adoc
@@ -1,4 +1,4 @@
-# Servlet Component
+## Servlet Component
 
 The *servlet:* component provides HTTP based
 link:endpoint.html[endpoints] for consuming HTTP requests that arrive at
@@ -27,9 +27,7 @@ body appears to be empty or you need to access the data multiple times
 link:stream-caching.html[Stream caching] or convert the message body to
 a `String` which is safe to be read multiple times.
 
-[[SERVLET-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------
@@ -39,9 +37,7 @@ servlet://relative_path[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[SERVLET-Options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The Servlet component supports 7 options which are listed below.
@@ -96,9 +92,7 @@ The Servlet component supports 22 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[SERVLET-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel will apply the same Message Headers as the link:http.html[HTTP]
 component.
@@ -108,18 +102,14 @@ Camel will also populate *all* `request.parameter` and
 `http://myserver/myserver?orderid=123`, the exchange will contain a
 header named `orderid` with the value 123.
 
-[[SERVLET-Usage]]
-Usage
-^^^^^
+### Usage
 
 You can consume only from endpoints generated by the Servlet component.
 Therefore, it should be used only as input into your Camel routes. To
 issue HTTP requests against other HTTP endpoints, use the
 link:http.html[HTTP Component]
 
-[[SERVLET-PuttingCamelJARsintheappserverbootclasspath]]
-Putting Camel JARs in the app server boot classpath
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Putting Camel JARs in the app server boot classpath
 
 If you put the Camel JARs such as `camel-core`, `camel-servlet`, etc. in
 the boot classpath of your application server (eg usually in its lib
@@ -178,9 +168,7 @@ But its *strongly advised* to use unique servlet-name for each Camel
 application to avoid this duplication clash, as well any unforeseen
 side-effects.
 
-[[SERVLET-Sample]]
-Sample
-^^^^^^
+### Sample
 
 INFO: From Camel 2.7 onwards it's easier to use link:servlet.html[Servlet] in
 Spring web applications. See link:servlet-tomcat-example.html[Servlet
@@ -204,15 +192,11 @@ endpoint uses the relative path to specify the endpoint's URL. A client
 can access the `camel-servlet` endpoint through the servlet publish
 address: `("http://localhost:8080/camel/services") + RELATIVE_PATH("/hello")`.
 
-[[SERVLET-SamplewhenusingSpring3.x]]
-Sample when using Spring 3.x
-++++++++++++++++++++++++++++
+#### Sample when using Spring 3.x
 
 See link:servlet-tomcat-example.html[Servlet Tomcat Example]
 
-[[SERVLET-SamplewhenusingSpring2.x]]
-Sample when using Spring 2.x
-++++++++++++++++++++++++++++
+#### Sample when using Spring 2.x
 
 When using the Servlet component in a Camel/Spring application it's
 often required to load the Spring ApplicationContext _after_ the Servlet
@@ -243,9 +227,7 @@ like this:
 <web-app>
 -------------------------------------------------------------------------
 
-[[SERVLET-SamplewhenusingOSGi]]
-Sample when using OSGi
-++++++++++++++++++++++
+#### Sample when using OSGi
 
 From *Camel 2.6.0*, you can publish the
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/CamelHttpTransportServlet.java[CamelHttpTransportServlet]
@@ -258,9 +240,7 @@ the
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/CamelHttpTransportServlet.java[CamelHttpTransportServlet]
 on the OSGi platform
 
-[[SERVLET-Spring-Boot]]
-Usage with Spring-Boot
-++++++++++++++++++++++
+#### Usage with Spring-Boot
 
 From *Camel 2.19.0* onwards, the _camel-servlet-starter_ library binds automatically all the rest endpoints under the "/camel/*" context path.
 The following table summarizes the additional configuration properties available in the camel-servlet-starter library.
@@ -276,9 +256,7 @@ The automatic mapping of the Camel servlet can also be disabled.
 |=======================================================================
 {% endraw %}
 
-[[SERVLET-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -289,5 +267,4 @@ See Also
 * link:servlet-tomcat-no-spring-example.html[Servlet Tomcat No Spring
 Example]
 * link:http.html[HTTP]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sip/src/main/docs/sip-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sip/src/main/docs/sip-component.adoc b/components/camel-sip/src/main/docs/sip-component.adoc
index 082d621..4b405ed 100644
--- a/components/camel-sip/src/main/docs/sip-component.adoc
+++ b/components/camel-sip/src/main/docs/sip-component.adoc
@@ -1,4 +1,4 @@
-# SIP Component
+## SIP Component
 
 *Available as of Camel 2.5*
 
@@ -45,9 +45,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Sip-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a sip endpoint is as follows:
 
@@ -63,9 +61,7 @@ UDP.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Sip-Options]]
-Options
-^^^^^^^
+### Options
 
 The SIP Component offers an extensive set of configuration options &
 capability to create custom stateful headers needed to propagate state
@@ -134,13 +130,9 @@ The SIP component supports 45 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[Sip-SendingMessagestofromaSIPendpoint]]
-Sending Messages to/from a SIP endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a SIP endpoint
 
-[[Sip-CreatingaCamelSIPPublisher]]
-Creating a Camel SIP Publisher
-++++++++++++++++++++++++++++++
+#### Creating a Camel SIP Publisher
 
 In the example below, a SIP Publisher is created to send SIP Event
 publications to  +
@@ -164,9 +156,7 @@ producerTemplate.sendBodyAndHeader(
     Request.PUBLISH);  
 ----------------------------------------------------------------------------------------------------------------------------------------------
 
-[[Sip-CreatingaCamelSIPSubscriber]]
-Creating a Camel SIP Subscriber
-+++++++++++++++++++++++++++++++
+#### Creating a Camel SIP Subscriber
 
 In the example below, a SIP Subscriber is created to receive SIP Event
 publications sent to  +
@@ -208,4 +198,4 @@ and is capable of communicating with both Publisher as well as
 Subscriber. It has a separate SIP stackName distinct from Publisher as
 well as Subscriber. While it is set up as a Camel Consumer, it does not
 actually send any messages along the route to the endpoint
-"mock:neverland".
+"mock:neverland".
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
index 98d6671..241b47d 100644
--- a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
@@ -1,8 +1,6 @@
-# Simple JMS Batch Component
+## Simple JMS Batch Component
 [[ConfluenceContent]]
-[[SJMSBatch-SJMSBatchComponent]]
-SJMS Batch Component
-~~~~~~~~~~~~~~~~~~~~
+### SJMS Batch Component
 
 *Available as of Camel 2.16*
 
@@ -78,9 +76,7 @@ for this component:
 </dependency>
 ----
 
-[[SJMSBatch-URIformat]]
-URI format
-++++++++++
+#### URI format
 
 [source]
 ----
@@ -110,9 +106,7 @@ broker. A plain link:sjms.html[SJMS] consumer endpoint can be used in
 conjunction with a regular non-persistence backed
 link:aggregator2.html[aggregator] in this scenario.
 
-[[SJMSBatch-ComponentOptionsandConfigurations]]
-Component Options and Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Component Options and Configurations
 
 
 
@@ -182,4 +176,4 @@ The Simple JMS Batch component supports 23 endpoint options which are listed bel
 
 The `completionSize` endpoint attribute is used in conjunction with
 `completionTimeout`, where the first condition to be met will cause the
-aggregated `Exchange` to be emitted down the route.
+aggregated `Exchange` to be emitted down the route.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-sjms/src/main/docs/sjms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-sjms/src/main/docs/sjms-component.adoc b/components/camel-sjms/src/main/docs/sjms-component.adoc
index 7cb31cc..3e74bfc 100644
--- a/components/camel-sjms/src/main/docs/sjms-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-component.adoc
@@ -1,4 +1,4 @@
-# Simple JMS Component
+## Simple JMS Component
 ifdef::env-github[]
 :icon-smile: :smiley:
 :caution-caption: :boom:
@@ -14,9 +14,7 @@ ifndef::env-github[]
 endif::[]
 
 [[ConfluenceContent]]
-[[SJMS-SJMSComponent]]
-SJMS Component
-~~~~~~~~~~~~~~
+### SJMS Component
 
 *Available as of Camel 2.11*
 
@@ -61,9 +59,7 @@ for this component:
 </dependency>
 ----
 
-[[SJMS-URIformat]]
-URI format
-++++++++++
+#### URI format
 
 [source]
 ----
@@ -97,9 +93,7 @@ sjms:topic:Stocks.Prices
 You append query options to the URI using the following format,
 `?option=value&option=value&...`
 
-[[SJMS-ComponentOptionsandConfigurations]]
-Component Options and Configurations
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Component Options and Configurations
 
 
 
@@ -212,13 +206,9 @@ component.setConnectionResource(connectionResource);
 component.setMaxConnections(1);
 ----
 
-[[SJMS-ProducerUsage]]
-Producer Usage
-^^^^^^^^^^^^^^
+### Producer Usage
 
-[[SJMS-InOnlyProducer]]
-InOnly Producer - (Default)
-+++++++++++++++++++++++++++
+#### InOnly Producer - (Default)
 
 The _InOnly_ producer is the default behavior of the SJMS Producer
 Endpoint.
@@ -229,9 +219,7 @@ from("direct:start")
     .to("sjms:queue:bar");
 ----
 
-[[SJMS-InOutProducer]]
-InOut Producer
-++++++++++++++
+#### InOut Producer
 
 To enable _InOut_ behavior append the `exchangePattern` attribute to the
 URI. By default it will use a dedicated TemporaryQueue for each
@@ -252,13 +240,9 @@ from("direct:start")
     .to("sjms:queue:bar?exchangePattern=InOut&namedReplyTo=my.reply.to.queue");
 ----
 
-[[SJMS-ConsumerUsage]]
-Consumer Usage
-^^^^^^^^^^^^^^
+### Consumer Usage
 
-[[SJMS-InOnlyConsumer]]
-InOnly Consumer - (Default)
-+++++++++++++++++++++++++++
+#### InOnly Consumer - (Default)
 
 The _InOnly_ xonsumer is the default Exchange behavior of the SJMS
 Consumer Endpoint.
@@ -269,9 +253,7 @@ from("sjms:queue:bar")
     .to("mock:result");
 ----
 
-[[SJMS-InOutConsumer]]
-InOut Consumer
-++++++++++++++
+#### InOut Consumer
 
 To enable _InOut_ behavior append the `exchangePattern` attribute to the
 URI.
@@ -282,13 +264,9 @@ from("sjms:queue:in.out.test?exchangePattern=InOut")
     .transform(constant("Bye Camel"));
 ----
 
-[[SJMS-AdvancedUsageNotes]]
-Advanced Usage Notes
-^^^^^^^^^^^^^^^^^^^^
+### Advanced Usage Notes
 
-[[SJMS-PlugableConnectionResourceManagementconnectionresource]]
-Plugable Connection Resource Management [[SJMS-connectionresource]]
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Plugable Connection Resource Management [[SJMS-connectionresource]]
 
 SJMS provides JMS
 http://docs.oracle.com/javaee/5/api/javax/jms/Connection.html[`Connection`]
@@ -370,15 +348,11 @@ camelContext.addComponent("sjms", component);
 To see the full example of its usage please refer to the
 https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java[`ConnectionResourceIT`].
 
-[[SJMS-Session,Consumer,&ProducerPooling&CachingManagement]]
-Session, Consumer, & Producer Pooling & Caching Management
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Session, Consumer, & Producer Pooling & Caching Management
 
 Coming soon ...
 
-[[SJMS-BatchMessageSupport]]
-Batch Message Support
-+++++++++++++++++++++
+#### Batch Message Support
 
 The SjmsProducer supports publishing a collection of messages by
 creating an Exchange that encapsulates a `List`. This SjmsProducer will
@@ -411,9 +385,7 @@ Then publish the list:
 template.sendBody("sjms:queue:batch.queue", messages);
 ----
 
-[[SJMS-CustomizableTransactionCommitStrategies]]
-Customizable Transaction Commit Strategies (Local JMS Transactions only)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Customizable Transaction Commit Strategies (Local JMS Transactions only)
 
 SJMS provides a developer the means to create a custom and plugable
 transaction strategy through the use of the
@@ -426,9 +398,7 @@ is the
 https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/tx/BatchTransactionCommitStrategy.java[`BatchTransactionCommitStrategy`]
 which is detailed further in the next section.
 
-[[SJMS-TransactedBatchConsumersAndProducers]]
-Transacted Batch Consumers & Producers
-++++++++++++++++++++++++++++++++++++++
+#### Transacted Batch Consumers & Producers
 
 The SJMS component has been designed to support the batching of local JMS
 transactions on both the Producer and Consumer endpoints. How they are
@@ -499,13 +469,9 @@ Now publish the List with transactions enabled:
 template.sendBody("sjms:queue:batch.queue?transacted=true", messages);
 ----
 
-[[SJMS-AdditionalNotes]]
-Additional Notes
-^^^^^^^^^^^^^^^^
+### Additional Notes
 
-[[SJMS-MessageHeaderFormat]]
-Message Header Format
-+++++++++++++++++++++
+#### Message Header Format
 
 The SJMS Component uses the same header format strategy that is used in
 the Camel JMS Component. This plugable strategy ensures that messages
@@ -530,9 +496,7 @@ custom strategy for formatting keys.
 For the `exchange.in.header`, the following rules apply for the header
 values:
 
-[[SJMS-MessageContent]]
-Message Content
-+++++++++++++++
+#### Message Content
 
 To deliver content over the wire we must ensure that the body of the
 message that is being delivered adheres to the JMS Message
@@ -542,9 +506,7 @@ The types, `String`, `CharSequence`, `Date`, `BigDecimal` and `BigInteger` are a
 converted to their `toString()` representation. All other types are
 dropped.
 
-[[SJMS-Clustering]]
-Clustering
-++++++++++
+#### Clustering
 
 When using _InOut_ with SJMS in a clustered environment you must either
 use TemporaryQueue destinations or use a unique named reply to
@@ -561,17 +523,13 @@ The _InOut_ Consumer uses this strategy as well ensuring that all
 responses messages to the included `JMSReplyTo` destination also have the
 `JMSCorrelationId` copied from the request as well.
 
-[[SJMS-TransactionSupporttransactions]]
-Transaction Support [[SJMS-transactions]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Transaction Support [[SJMS-transactions]]
 
 SJMS currently only supports the use of internal JMS Transactions. There
 is no support for the Camel Transaction Processor or the Java
 Transaction API (JTA).
 
-[[SJMS-DoesSpringlessMeanICantUseSpring]]
-Does Springless Mean I Can't Use Spring?
-++++++++++++++++++++++++++++++++++++++++
+#### Does Springless Mean I Can't Use Spring?
 
 Not at all. Below is an example of the SJMS component using the Spring
 DSL:
@@ -589,4 +547,4 @@ DSL:
 
 Springless refers to moving away from the dependency on the Spring JMS
 API. A new JMS client API is being developed from the ground up to power
-SJMS.
+SJMS.
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[05/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty-http/src/main/docs/netty-http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty-http/src/main/docs/netty-http-component.adoc b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
index 03545f9..6fb6476 100644
--- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
+++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
@@ -1,4 +1,4 @@
-# Netty HTTP Component
+## Netty HTTP Component
 
 *Available as of Camel 2.12*
 
@@ -35,9 +35,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[NettyHTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a netty component is as follows
 
@@ -64,9 +62,7 @@ headers (like `CamelHttpQuery`). Endpoint options can be specified only
 at the endpoint URI definition level (like `to` or `from` DSL elements).
 
 
-[[NettyHTTP-HTTPOptions]]
-HTTP Options
-^^^^^^^^^^^^
+### HTTP Options
 
 INFO: *A lot more options*. *Important:* This component inherits all the options from
 link:netty.html[Netty]. So make sure to look at the
@@ -200,9 +196,7 @@ The Netty HTTP component supports 82 endpoint options which are listed below:
 
 
 
-[[NettyHTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The following headers can be used on the producer to control the HTTP
 request.
@@ -267,9 +261,7 @@ with the value `Basic`.
 |`Content-Type` |`String` | The content type if provided. For example: `text/plain; charset="UTF-8"`.
 |=======================================================================
 
-[[NettyHTTP-AccesstoNettytypes]]
-Access to Netty types
-^^^^^^^^^^^^^^^^^^^^^
+### Access to Netty types
 
 This component uses the
 `org.apache.camel.component.netty.http.NettyHttpMessage` as the message
@@ -283,9 +275,7 @@ accessible at all times.
 org.jboss.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
 -----------------------------------------------------------------------------------------------------------------
 
-[[NettyHTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 In the route below we use link:netty-http.html[Netty HTTP] as a HTTP
 server, which returns back a hardcoded "Bye World" message.
@@ -307,9 +297,7 @@ link:producertemplate.html[ProducerTemplate] as shown below:
 
 And we get back "Bye World" as the output.
 
-[[NettyHTTP-HowdoIletNettymatchwildcards]]
-How do I let Netty match wildcards
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How do I let Netty match wildcards
 
 By default link:netty-http.html[Netty HTTP] will only match on exact
 uri's. But you can instruct Netty to match prefixes. For example
@@ -340,9 +328,7 @@ To match *any* endpoint you can do:
 from("netty-http:http://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
 ----------------------------------------------------------------------------
 
-[[NettyHTTP-Usingmultiplerouteswithsameport]]
-Using multiple routes with same port
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using multiple routes with same port
 
 In the same link:camelcontext.html[CamelContext] you can have multiple
 routes from link:netty-http.html[Netty HTTP] that shares the same port
@@ -395,9 +381,7 @@ from("netty-http:http://0.0.0.0:{{port}}/bar?ssl=true")
   .transform().constant("Bye Camel");
 --------------------------------------------------------------------------------------
 
-[[NettyHTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes]]
-Reusing same server bootstrap configuration with multiple routes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes
 
 By configuring the common server bootstrap option in an single instance
 of a
@@ -435,16 +419,12 @@ And in the routes you refer to this option as shown below
 </route>
 ---------------------------------------------------------------------------------------------------------
 
-[[NettyHTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer]]
-Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
 
 See the link:netty-http-server-example.html[Netty HTTP Server Example]
 for more details and example how to do that.
 
-[[NettyHTTP-UsingHTTPBasicAuthentication]]
-Using HTTP Basic Authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using HTTP Basic Authentication
 
 The link:netty-http.html[Netty HTTP] consumer supports HTTP basic
 authentication by specifying the security realm name to use, as shown
@@ -467,9 +447,7 @@ End user of Apache Karaf / ServiceMix has a karaf realm out of the box,
 and hence why the example above would work out of the box in these
 containers.
 
-[[NettyHTTP-SpecifyingACLonwebresources]]
-Specifying ACL on web resources
-+++++++++++++++++++++++++++++++
+#### Specifying ACL on web resources
 
 The `org.apache.camel.component.netty.http.SecurityConstraint` allows to
 define constrains on web resources. And the
@@ -521,9 +499,7 @@ below:
 </route>
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[NettyHTTP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -532,5 +508,4 @@ See Also
 
 * link:netty.html[Netty]
 * link:netty-http-server-example.html[Netty HTTP Server Example]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty/src/main/docs/netty-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty/src/main/docs/netty-component.adoc b/components/camel-netty/src/main/docs/netty-component.adoc
index 57132d0..694e578 100644
--- a/components/camel-netty/src/main/docs/netty-component.adoc
+++ b/components/camel-netty/src/main/docs/netty-component.adoc
@@ -1,4 +1,4 @@
-# Netty Component
+## Netty Component
 
 *Available as of Camel 2.3*
 
@@ -33,9 +33,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Netty-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a netty component is as follows
 
@@ -51,9 +49,7 @@ UDP.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Netty-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -165,9 +161,7 @@ The Netty component supports 70 endpoint options which are listed below:
 
 
 
-[[Netty-RegistrybasedOptions]]
-Registry based Options
-^^^^^^^^^^^^^^^^^^^^^^
+### Registry based Options
 
 Codec Handlers and SSL Keystores can be enlisted in the
 link:registry.html[Registry], such as in the Spring XML file.
@@ -223,9 +217,7 @@ so Camel knows it should lookup.
 
 *Important:* Read below about using non shareable encoders/decoders.
 
-[[Netty-Usingnonshareableencodersordecoders]]
-Using non shareable encoders or decoders
-++++++++++++++++++++++++++++++++++++++++
+#### Using non shareable encoders or decoders
 
 If your encoders or decoders is not shareable (eg they have the
 @Shareable class annotation), then your encoder/decoder must implement
@@ -239,13 +231,9 @@ The Netty component offers a
 `org.apache.camel.component.netty.ChannelHandlerFactories` factory
 class, that has a number of commonly used methods.
 
-[[Netty-SendingMessagestoandfromaNettyendpoint]]
-Sending Messages to/from a Netty endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a Netty endpoint
 
-[[Netty-NettyProducer]]
-Netty Producer
-++++++++++++++
+#### Netty Producer
 
 In Producer mode, the component provides the ability to send payloads to
 a socket endpoint +
@@ -254,9 +242,7 @@ a socket endpoint +
 The producer mode supports both one-way and request-response based
 operations.
 
-[[Netty-NettyConsumer]]
-Netty Consumer
-++++++++++++++
+#### Netty Consumer
 
 In Consumer mode, the component provides the ability to:
 
@@ -269,9 +255,7 @@ object based payloads and
 The consumer mode supports both one-way and request-response based
 operations.
 
-[[Netty-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 The following headers are filled for the exchanges created by the Netty
 consumer:
@@ -292,13 +276,9 @@ netty.
 |`NettyConstants.NETTY_LOCAL_ADDRESS` / `CamelNettyLocalAddress` |`java.net.SocketAddress` |Local address of the incoming socket connection.
 |=======================================================================
 
-[[Netty-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
 
-[[Netty-AUDPNettyendpointusingRequest-Replyandserializedobjectpayload]]
-A UDP Netty endpoint using Request-Reply and serialized object payload
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A UDP Netty endpoint using Request-Reply and serialized object payload
 
 [source,java]
 ------------------------------------------------------------------
@@ -316,9 +296,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 ------------------------------------------------------------------
 
-[[Netty-ATCPbasedNettyconsumerendpointusingOne-waycommunication]]
-A TCP based Netty consumer endpoint using One-way communication
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A TCP based Netty consumer endpoint using One-way communication
 
 [source,java]
 -------------------------------------------
@@ -330,9 +308,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 -------------------------------------------
 
-[[Netty-AnSSLTCPbasedNettyconsumerendpointusingRequest-Replycommunication]]
-An SSL/TCP based Netty consumer endpoint using Request-Reply communication
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### An SSL/TCP based Netty consumer endpoint using Request-Reply communication
 
 [[Netty-UsingtheJSSEConfigurationUtility]]
 Using the JSSE Configuration Utility
@@ -444,9 +420,7 @@ enriches the Camel link:message.html[Message] with headers having
 details about the client certificate. For example the subject name is
 readily available in the header `CamelNettySSLClientCertSubjectName`.
 
-[[Netty-UsingMultipleCodecs]]
-Using Multiple Codecs
-+++++++++++++++++++++
+#### Using Multiple Codecs
 
 In certain cases it may be necessary to add chains of encoders and
 decoders to the netty pipeline. To add multpile codecs to a camel netty
@@ -470,9 +444,7 @@ a comma separated list or contained in a List e.g.
 
 or via spring.
 
-[[Netty-ClosingChannelWhenComplete]]
-Closing Channel When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Channel When Complete
 
 When acting as a server you sometimes want to close the channel when,
 for example, a client conversion is finished. +
@@ -500,9 +472,7 @@ written the bye message back to the client:
         });
 --------------------------------------------------------------------------------------------------------
 
-[[Netty-Addingcustomchannelpipelinefactoriestogaincompletecontroloveracreatedpipeline]]
-Adding custom channel pipeline factories to gain complete control over a created pipeline
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding custom channel pipeline factories to gain complete control over a created pipeline
 
 *Available as of Camel 2.5*
 
@@ -576,9 +546,7 @@ context.addRoutes(new RouteBuilder() {
 });
 -------------------------------------------------------------------
 
-[[Netty-ReusingNettybossandworkerthreadpools]]
-Reusing Netty boss and worker thread pools
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reusing Netty boss and worker thread pools
 
 *Available as of Camel 2.12*
 
@@ -637,9 +605,7 @@ And if we have another route we can refer to the shared worker pool:
 
 ... and so forth.
 
-[[Netty-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -647,5 +613,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:netty-http.html[Netty HTTP]
-* link:mina.html[MINA]
-
+* link:mina.html[MINA]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
index 79f724a..a90eb96 100644
--- a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
+++ b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
@@ -1,4 +1,4 @@
-# Netty4 HTTP Component
+## Netty4 HTTP Component
 
 *Available as of Camel 2.14*
 
@@ -32,9 +32,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Netty4HTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a netty component is as follows
 
@@ -62,9 +60,7 @@ Keep also in mind that you cannot specify endpoint options using dynamic
 headers (like `CamelHttpQuery`). Endpoint options can be specified only
 at the endpoint URI definition level (like `to` or `from` DSL elements).
 
-[[Netty4HTTP-HTTPOptions]]
-HTTP Options
-^^^^^^^^^^^^
+### HTTP Options
 
 
 INFO: *A lot more options*. *Important:* This component inherits all the options from
@@ -205,9 +201,7 @@ The Netty4 HTTP component supports 83 endpoint options which are listed below:
 
 
 
-[[Netty4HTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The following headers can be used on the producer to control the HTTP
 request.
@@ -271,9 +265,7 @@ with the value `Basic`.
 `text/plain; charset="UTF-8"`.
 |=======================================================================
 
-[[Netty4HTTP-AccesstoNettytypes]]
-Access to Netty types
-^^^^^^^^^^^^^^^^^^^^^
+### Access to Netty types
 
 This component uses the
 `org.apache.camel.component.netty4.http.NettyHttpMessage` as the message
@@ -287,9 +279,7 @@ accessible at all times.
 io.netty.handler.codec.http.HttpRequest request = exchange.getIn(NettyHttpMessage.class).getHttpRequest();
 ----------------------------------------------------------------------------------------------------------
 
-[[Netty4HTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 In the route below we use Netty4 HTTP as a HTTP server, which returns
 back a hardcoded "Bye World" message.
@@ -311,9 +301,7 @@ link:producertemplate.html[ProducerTemplate] as shown below:
 
 And we get back "Bye World" as the output.
 
-[[Netty4HTTP-HowdoIletNettymatchwildcards]]
-How do I let Netty match wildcards
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How do I let Netty match wildcards
 
 By default Netty4 HTTP will only match on exact uri's. But you can
 instruct Netty to match prefixes. For example
@@ -344,9 +332,7 @@ To match *any* endpoint you can do:
 from("netty4-http:http://0.0.0.0:8123?matchOnUriPrefix=true").to("mock:foo");
 -----------------------------------------------------------------------------
 
-[[Netty4HTTP-Usingmultiplerouteswithsameport]]
-Using multiple routes with same port
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using multiple routes with same port
 
 In the same link:camelcontext.html[CamelContext] you can have multiple
 routes from Netty4 HTTP that shares the same port (eg a
@@ -399,9 +385,7 @@ from("netty4-http:http://0.0.0.0:{{port}}/bar?ssl=true")
   .transform().constant("Bye Camel");
 --------------------------------------------------------------------------------------
 
-[[Netty4HTTP-Reusingsameserverbootstrapconfigurationwithmultipleroutes]]
-Reusing same server bootstrap configuration with multiple routes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes
 
 By configuring the common server bootstrap option in an single instance
 of a
@@ -438,16 +422,12 @@ And in the routes you refer to this option as shown below
 </route>
 ----------------------------------------------------------------------------------------------------------
 
-[[Netty4HTTP-ReusingsameserverbootstrapconfigurationwithmultipleroutesacrossmultiplebundlesinOSGicontainer]]
-Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Reusing same server bootstrap configuration with multiple routes across multiple bundles in OSGi container
 
 See the link:netty-http-server-example.html[Netty HTTP Server Example]
 for more details and example how to do that.
 
-[[Netty4HTTP-UsingHTTPBasicAuthentication]]
-Using HTTP Basic Authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using HTTP Basic Authentication
 
 The Netty HTTP consumer supports HTTP basic authentication by specifying
 the security realm name to use, as shown below
@@ -469,9 +449,7 @@ End user of Apache Karaf / ServiceMix has a karaf realm out of the box,
 and hence why the example above would work out of the box in these
 containers.
 
-[[Netty4HTTP-SpecifyingACLonwebresources]]
-Specifying ACL on web resources
-+++++++++++++++++++++++++++++++
+#### Specifying ACL on web resources
 
 The `org.apache.camel.component.netty4.http.SecurityConstraint` allows
 to define constrains on web resources. And the
@@ -523,9 +501,7 @@ below:
 </route>
 -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[Netty4HTTP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -534,5 +510,4 @@ See Also
 
 * link:netty.html[Netty]
 * link:netty-http-server-example.html[Netty HTTP Server Example]
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-netty4/src/main/docs/netty4-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-netty4/src/main/docs/netty4-component.adoc b/components/camel-netty4/src/main/docs/netty4-component.adoc
index d03e858..5b8da98 100644
--- a/components/camel-netty4/src/main/docs/netty4-component.adoc
+++ b/components/camel-netty4/src/main/docs/netty4-component.adoc
@@ -1,4 +1,4 @@
-# Netty4 Component
+## Netty4 Component
 
 *Available as of Camel 2.14*
 
@@ -30,9 +30,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Netty4-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a netty component is as follows
 
@@ -48,9 +46,7 @@ UDP.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Netty4-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -173,9 +169,7 @@ The Netty4 component supports 74 endpoint options which are listed below:
 
 
 
-[[Netty4-RegistrybasedOptions]]
-Registry based Options
-^^^^^^^^^^^^^^^^^^^^^^
+### Registry based Options
 
 Codec Handlers and SSL Keystores can be enlisted in the
 link:registry.html[Registry], such as in the Spring XML file.
@@ -231,9 +225,7 @@ so Camel knows it should lookup.
 
 *Important:* Read below about using non shareable encoders/decoders.
 
-[[Netty4-Usingnonshareableencodersordecoders]]
-Using non shareable encoders or decoders
-++++++++++++++++++++++++++++++++++++++++
+#### Using non shareable encoders or decoders
 
 If your encoders or decoders is not shareable (eg they have the
 @Shareable class annotation), then your encoder/decoder must implement
@@ -247,13 +239,9 @@ The Netty component offers a
 `org.apache.camel.component.netty.ChannelHandlerFactories` factory
 class, that has a number of commonly used methods.
 
-[[Netty4-SendingMessagestofromaNettyendpoint]]
-Sending Messages to/from a Netty endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to/from a Netty endpoint
 
-[[Netty4-NettyProducer]]
-Netty Producer
-++++++++++++++
+#### Netty Producer
 
 In Producer mode, the component provides the ability to send payloads to
 a socket endpoint +
@@ -262,9 +250,7 @@ a socket endpoint +
 The producer mode supports both one-way and request-response based
 operations.
 
-[[Netty4-NettyConsumer]]
-Netty Consumer
-++++++++++++++
+#### Netty Consumer
 
 In Consumer mode, the component provides the ability to:
 
@@ -277,13 +263,9 @@ object based payloads and
 The consumer mode supports both one-way and request-response based
 operations.
 
-[[Netty4-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
 
-[[Netty4-AUDPNettyendpointusingRequest-Replyandserializedobjectpayload]]
-A UDP Netty endpoint using Request-Reply and serialized object payload
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A UDP Netty endpoint using Request-Reply and serialized object payload
 
 [source,java]
 ------------------------------------------------------------------
@@ -301,9 +283,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 ------------------------------------------------------------------
 
-[[Netty4-ATCPbasedNettyconsumerendpointusingOne-waycommunication]]
-A TCP based Netty consumer endpoint using One-way communication
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### A TCP based Netty consumer endpoint using One-way communication
 
 [source,java]
 -------------------------------------------
@@ -315,9 +295,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 -------------------------------------------
 
-[[Netty4-AnSSLTCPbasedNettyconsumerendpointusingRequest-Replycommunication]]
-An SSL/TCP based Netty consumer endpoint using Request-Reply communication
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### An SSL/TCP based Netty consumer endpoint using Request-Reply communication
 
 [[Netty4-UsingtheJSSEConfigurationUtility]]
 Using the JSSE Configuration Utility
@@ -429,9 +407,7 @@ enriches the Camel link:message.html[Message] with headers having
 details about the client certificate. For example the subject name is
 readily available in the header `CamelNettySSLClientCertSubjectName`.
 
-[[Netty4-UsingMultipleCodecs]]
-Using Multiple Codecs
-+++++++++++++++++++++
+#### Using Multiple Codecs
 
 In certain cases it may be necessary to add chains of encoders and
 decoders to the netty pipeline. To add multpile codecs to a camel netty
@@ -538,9 +514,7 @@ or via spring.
     </camelContext>
 -------------------------------------------------------------------------------------------------------------
 
-[[Netty4-ClosingChannelWhenComplete]]
-Closing Channel When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Channel When Complete
 
 When acting as a server you sometimes want to close the channel when,
 for example, a client conversion is finished. +
@@ -570,8 +544,7 @@ written the bye message back to the client:
 
 [[Netty4-Addingcustomchannelpipelinefactoriestogaincompletecontroloveracreatedpipeline]]
 Adding custom channel pipeline factories to gain complete control over a
-created pipeline
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### created pipeline
 
 Custom channel pipelines provide complete control to the user over the
 handler/interceptor chain by inserting custom handler(s), encoder(s) &
@@ -641,9 +614,7 @@ context.addRoutes(new RouteBuilder() {
 });
 ----------------------------------------------------------------------
 
-[[Netty4-ReusingNettybossandworkerthreadpools]]
-Reusing Netty boss and worker thread pools
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reusing Netty boss and worker thread pools
 
 *Available as of Camel 2.12*
 
@@ -702,9 +673,7 @@ And if we have another route we can refer to the shared worker pool:
 
 ... and so forth.
 
-[[Netty4-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -712,4 +681,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:netty-http.html[Netty HTTP]
-* link:mina.html[MINA]
+* link:mina.html[MINA]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ognl/src/main/docs/ognl-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ognl/src/main/docs/ognl-language.adoc b/components/camel-ognl/src/main/docs/ognl-language.adoc
index afaa8b8..a189a74 100644
--- a/components/camel-ognl/src/main/docs/ognl-language.adoc
+++ b/components/camel-ognl/src/main/docs/ognl-language.adoc
@@ -1,4 +1,4 @@
-# OGNL Language
+## OGNL Language
 
 Camel allows http://commons.apache.org/proper/commons-ognl/[OGNL] to be
 used as an link:expression.html[Expression] or
@@ -21,9 +21,7 @@ you can construct the syntax as follows:
 "getRequest().getBody().getFamilyName()"
 ----------------------------------------
 
-[[OGNL-Options]]
-OGNL Options
-^^^^^^^^^^^^
+### OGNL Options
 
 
 // language options: START
@@ -42,9 +40,7 @@ The OGNL language supports 1 options which are listed below.
 
 
 
-[[OGNL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -71,9 +67,7 @@ Variables
 |property(name, type) |Type |the property by the given name as the given type
 |=======================================================================
 
-[[OGNL-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use OGNL inside a link:message-filter.html[Message
 Filter] in XML
@@ -96,9 +90,7 @@ And the sample using Java DSL:
    from("seda:foo").filter().ognl("request.headers.foo == 'bar'").to("seda:bar");
 ---------------------------------------------------------------------------------
 
-[[OGNL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -112,9 +104,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").ognl("resource:classpath:myognl.txt")
 ------------------------------------------------------------
 
-[[OGNL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use OGNL in your camel routes you need to add the a dependency on
 *camel-ognl* which implements the OGNL language.
@@ -133,4 +123,4 @@ link:download.html[the download page for the latest versions]).
 -------------------------------------
 
 Otherwise, you'll also need
-http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.ognl/2.7.3_4/org.apache.servicemix.bundles.ognl-2.7.3_4.jar[OGNL]
+http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.ognl/2.7.3_4/org.apache.servicemix.bundles.ognl-2.7.3_4.jar[OGNL]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
index 28a432c..50aa53a 100644
--- a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
+++ b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
@@ -1,4 +1,4 @@
-# Olingo2 Component
+## Olingo2 Component
 
 *Available as of Camel 2.14*
 
@@ -30,18 +30,14 @@ for this component:
     </dependency>
 ----------------------------------------------
 
-[[Olingo2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------------------
     olingo2://endpoint/<resource-path>?[options]
 ------------------------------------------------
 
-[[Olingo2-Olingo2Component]]
-Olingo2 Options
-^^^^^^^^^^^^^^^
+### Olingo2 Options
 
 
 
@@ -93,9 +89,7 @@ The Olingo2 component supports 16 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Olingo2-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
 
 Producer endpoints can use endpoint names and options listed
 next. Producer endpoints can also use a special option *`inBody`* that
@@ -139,9 +133,7 @@ org.apache.olingo.odata2.api.commons.HttpStatusCodes for other OData resources
 |update |data, resourcePath |PUT |org.apache.olingo.odata2.api.commons.HttpStatusCodes
 |=======================================================================
 
-[[Olingo2-ODataResourceTypeMapping]]
-OData Resource Type Mapping
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### OData Resource Type Mapping
 
 The result of *read* endpoint and data type of *data* option depends on
 the OData resource being queried, created or modified. 
@@ -174,9 +166,7 @@ java.util.List<java.util.Map<String, Object>> containing list of key property na
 |Count |<resource-uri>/$count |java.lang.Long
 |=======================================================================
 
-[[Olingo2-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 
 Only the *read* endpoint can be used as a consumer endpoint. Consumer
 endpoints can
@@ -187,16 +177,12 @@ collection will generate one exchange per element, and their routes will
 be executed once for each exchange. This behavior can be disabled by
 setting the endpoint property *consumer.splitResult=false*. 
 
-[[Olingo2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Any URI option can be provided in a message header for producer
 endpoints with a *`CamelOlingo2.`* prefix.
 
-[[Olingo2-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 All result message bodies utilize objects provided by the underlying
 http://olingo.apache.org/javadoc/odata2/index.html[Apache Olingo 2.0
@@ -206,9 +192,7 @@ parameter. For endpoints that return an array or collection, a consumer
 endpoint will map every element to distinct messages, unless
 *consumer.splitResult* is set to *false*.
 
-[[Olingo2-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
 
 The following route reads top 5 entries from the Manufacturer feed
 ordered by ascending Name property. 
@@ -265,5 +249,4 @@ consumer endpoint will produce an *ODataFeed* value the first time, and
 ---------------------------------------------------------------------------------------------------------
 from("olingo2://read/Manufacturers?queryParams=#paramsBean&consumer.timeUnit=SECONDS&consumer.delay=30")
     .to("bean:blah");
----------------------------------------------------------------------------------------------------------
-
+---------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openshift/src/main/docs/openshift-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openshift/src/main/docs/openshift-component.adoc b/components/camel-openshift/src/main/docs/openshift-component.adoc
index d68834a..6d36b61 100644
--- a/components/camel-openshift/src/main/docs/openshift-component.adoc
+++ b/components/camel-openshift/src/main/docs/openshift-component.adoc
@@ -1,4 +1,4 @@
-# OpenShift Component
+## OpenShift Component
 
 *Available as of Camel 2.14*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Openshift-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------
@@ -30,9 +28,7 @@ openshift:clientId[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Openshift-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -95,13 +91,9 @@ The OpenShift component supports 27 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Openshift-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[Openshift-Listingallapplications]]
-Listing all applications
-++++++++++++++++++++++++
+#### Listing all applications
 
 [source,java]
 --------------------------------------------------------------------------
@@ -114,9 +106,7 @@ from("direct:apps")
 In this case the information about all the applications is returned as
 pojo. If you want a json response, then set mode=json.
 
-[[Openshift-Stoppinganapplication]]
-Stopping an application
-+++++++++++++++++++++++
+#### Stopping an application
 
 [source,java]
 ---------------------------------------------------------------------------------------------
@@ -160,12 +150,9 @@ following headers is included.
 |CamelOpenShiftEventNewState |No |The new state, for any of the event types
 |=======================================================================
 
-[[Openshift-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc b/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
index 53d008d..f21dcc6 100644
--- a/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-cinder-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Cinder Component
+## OpenStack Cinder Component
 
 *Available as of Camel 2.19*
 
 The openstack-cinder component allows messages to be sent to an OpenStack block storage services.
 
-[[openstack-cinder-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-cinder-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -36,9 +32,7 @@ openstack-cinder://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-cinder-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Cinder component has no options.
@@ -66,17 +60,12 @@ The OpenStack Cinder component supports 10 endpoint options which are listed bel
 // endpoint options: END
 
 
-[[openstack-cinder-Usage]]
-Usage
-^^^^^
+### Usage
 You can use following settings for each subsystem:
 
-volumes
-~~~~~~~
+### volumes
 
-[[openstack-cinder-OperationsYouCanPerformWiththeVolumeProducer]]
-Operations you can perform with the Volume producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Volume producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -94,9 +83,7 @@ Operations you can perform with the Volume producer
 |`delete` | Delete the volume.
 |=========================================================================
 
-[[openstack-cinder-MessageheadersevaluatedbytheVolumeProducer]]
-Message headers evaluated by the Volume producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Volume producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -123,12 +110,9 @@ Message headers evaluated by the Volume producer
 
 If you need more precise volume settings you can create new object of the type *org.openstack4j.model.storage.block.Volume* and send in the message body.
 
-snapshots
-~~~~~~~~~
+### snapshots
 
-[[openstack-cinder-OperationsYouCanPerformWiththeSnapshotProducer]]
-Operations you can perform with the Snapshot producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Snapshot producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -145,9 +129,7 @@ Operations you can perform with the Snapshot producer
 
 |=========================================================================
 
-[[openstack-cinder-MessageheadersevaluatedbytheSnapshotProducer]]
-Message headers evaluated by the Snapshot producer
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Snapshot producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -169,14 +151,11 @@ Message headers evaluated by the Snapshot producer
 
 If you need more precise server settings you can create new object of the type *org.openstack4j.model.storage.block.VolumeSnapshot* and send in the message body.
 
-[[CamelOpenstack-cinder-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-glance-component.adoc b/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
index 168e4f8..db76a0c 100644
--- a/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-glance-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Glance Component
+## OpenStack Glance Component
 
 *Available as of Camel 2.19*
 
 The openstack-glance component allows messages to be sent to an OpenStack image services.
 
-[[openstack-glance-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-glance-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -36,9 +32,7 @@ openstack-glance://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-glance-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Glance component has no options.
@@ -65,9 +59,7 @@ The OpenStack Glance component supports 9 endpoint options which are listed belo
 // endpoint options: END
 
 
-[[openstack-glance-Usage]]
-Usage
-^^^^^
+### Usage
 
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
@@ -88,9 +80,7 @@ Usage
 |`delete` | Delete the image.
 |=========================================================================
 
-[[openstack-glance-MessageheadersevaluatedbytheGlanceProducer]]
-Message headers evaluated by the Glance producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Glance producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -121,14 +111,11 @@ Message headers evaluated by the Glance producer
 |`properties` | `Map` | Image properties.
 |=========================================================================
 
-[[CamelOpenstack-glance-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc b/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
index 4460243..6e1b10f 100644
--- a/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-keystone-component.adoc
@@ -1,4 +1,4 @@
-# OpenStack Keystone Component
+## OpenStack Keystone Component
 
 *Available as of Camel 2.19*
 
@@ -6,9 +6,7 @@ The openstack-keystone component allows messages to be sent to an OpenStack iden
 
 *The openstack-keystone component supports only Identity API v3!*
 
-[[openstack-keystone-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -26,9 +24,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-keystone-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -38,9 +34,7 @@ openstack-keystone://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-keystone-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Keystone component has no options.
@@ -67,17 +61,12 @@ The OpenStack Keystone component supports 9 endpoint options which are listed be
 // endpoint options: END
 
 
-[[openstack-keystone-Usage]]
-Usage
-^^^^^
+### Usage
 You can use following settings for each subsystem:
 
-domains
-~~~~~~~
+### domains
 
-[[openstack-keystone-OperationsYouCanPerformWithDomainProducer]]
-Operations you can perform with the Domain producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Domain producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -93,9 +82,7 @@ Operations you can perform with the Domain producer
 |`delete` | Delete the domain.
 |=========================================================================
 
-[[openstack-keystone-MessageHeadersEvaluatedByTheDomainProducer]]
-Message headers evaluated by the Domain producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Domain producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -112,12 +99,9 @@ Message headers evaluated by the Domain producer
 
 If you need more precise domain settings you can create new object of the type *org.openstack4j.model.identity.v3.Domain* and send in the message body.
 
-groups
-~~~~~~
+### groups
 
-[[openstack-keystone-OperationsYouCanPerformWithGroupProducer]]
-Operations you can perform with the Group producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Group producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -139,9 +123,7 @@ Operations you can perform with the Group producer
 |`removeUserFromGroup` | Remove the user from the group.
 |=========================================================================
 
-[[openstack-keystone-MessageHeadersEvaluatedByTheGroupProducer]]
-Message headers evaluated by the Group producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Group producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -162,12 +144,9 @@ Message headers evaluated by the Group producer
 
 If you need more precise group settings you can create new object of the type *org.openstack4j.model.identity.v3.Group* and send in the message body.
 
-projects
-~~~~~~~~
+### projects
 
-[[openstack-keystone-OperationsYouCanPerformWithProjectProducer]]
-Operations you can perform with the Project producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Project producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -183,9 +162,7 @@ Operations you can perform with the Project producer
 |`delete` | Delete the project.
 |=========================================================================
 
-[[openstack-keystone-MessageHeadersEvaluatedByTheProjectProducer]]
-Message headers evaluated by the Project producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Project producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -206,12 +183,9 @@ Message headers evaluated by the Project producer
 
 If you need more precise project settings you can create new object of the type *org.openstack4j.model.identity.v3.Project* and send in the message body.
 
-regions
-~~~~~~~
+### regions
 
-[[openstack-keystone-OperationsYouCanPerformWithRegionProducer]]
-Operations you can perform with the Region producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Region producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -227,9 +201,7 @@ Operations you can perform with the Region producer
 |`delete` | Delete the region.
 |=========================================================================
 
-[[openstack-keystone-MessageHeadersEvaluatedByTheRegionProducer]]
-Message headers evaluated by the Region producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Region producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -244,12 +216,9 @@ Message headers evaluated by the Region producer
 
 If you need more precise region settings you can create new object of the type *org.openstack4j.model.identity.v3.Region* and send in the message body.
 
-users
-~~~~~
+### users
 
-[[openstack-keystone-OperationsYouCanPerformWithUserProducer]]
-Operations you can perform with the User producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the User producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -265,9 +234,7 @@ Operations you can perform with the User producer
 |`delete` | Delete the user.
 |=========================================================================
 
-[[openstack-keystone-MessageHeadersEvaluatedByTheUserProducer]]
-Message headers evaluated by the User producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the User producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -290,14 +257,11 @@ Message headers evaluated by the User producer
 
 If you need more precise user settings you can create new object of the type *org.openstack4j.model.identity.v3.User* and send in the message body.
 
-[[CamelOpenstack-keystone-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc b/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
index 90e9ccd..61f0661 100644
--- a/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-neutron-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Neutron Component
+## OpenStack Neutron Component
 
 *Available as of Camel 2.19*
 
 The openstack-neutron component allows messages to be sent to an OpenStack network services.
 
-[[openstack-neutron-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-neutron-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -36,9 +32,7 @@ openstack-neutron://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-neutron-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Neutron component has no options.
@@ -66,17 +60,12 @@ The OpenStack Neutron component supports 10 endpoint options which are listed be
 // endpoint options: END
 
 
-[[openstack-neutron-Usage]]
-Usage
-^^^^^
+### Usage
 You can use following settings for each subsystem:
 
-networks
-~~~~~~~~
+### networks
 
-[[openstack-neutron-OperationsYouCanPerformWiththeNetworkProducer]]
-Operations you can perform with the Network producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Network producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -90,9 +79,7 @@ Operations you can perform with the Network producer
 |`delete` | Delete the network.
 |=========================================================================
 
-[[openstack-neutron-MessageheadersevaluatedbytheNetworkProducer]]
-Message headers evaluated by the Network producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Network producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -121,12 +108,9 @@ Message headers evaluated by the Network producer
 
 If you need more precise network settings you can create new object of the type *org.openstack4j.model.network.Network* and send in the message body.
 
-subnets
-~~~~~~~
+### subnets
 
-[[openstack-neutron-OperationsYouCanPerformWiththeSubnetProducer]]
-Operations you can perform with the Subnet producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Subnet producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -142,9 +126,7 @@ Operations you can perform with the Subnet producer
 |`action` | Perform an action on the subnet.
 |=========================================================================
 
-[[openstack-neutron-MessageheadersevaluatedbytheSubnetProducer]]
-Message headers evaluated by the Subnet producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Subnet producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -165,12 +147,9 @@ Message headers evaluated by the Subnet producer
 
 If you need more precise subnet settings you can create new object of the type *org.openstack4j.model.network.Subnet* and send in the message body.
 
-ports
-~~~~~
+### ports
 
-[[openstack-neutron-OperationsYouCanPerformWiththePortProducer]]
-Operations you can perform with the Port producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Port producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -187,9 +166,7 @@ Operations you can perform with the Port producer
 
 |=========================================================================
 
-[[openstack-neutron-MessageheadersevaluatedbythePortProducer]]
-Message headers evaluated by the Port producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Port producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -208,12 +185,9 @@ Message headers evaluated by the Port producer
 |`macAddress` | `String` | MAC address.
 |=========================================================================
 
-routers
-~~~~~~~
+### routers
 
-[[openstack-neutron-OperationsYouCanPerformWiththeRouterProducer]]
-Operations you can perform with the Router producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Router producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -234,9 +208,7 @@ Operations you can perform with the Router producer
 
 |=========================================================================
 
-[[openstack-neutron-MessageheadersevaluatedbytheRouterProducer]]
-Message headers evaluated by the Port producer
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Port producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -258,14 +230,11 @@ Message headers evaluated by the Port producer
 |=========================================================================
 
 
-[[CamelOpenstack-neutron-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-nova-component.adoc b/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
index f37d49c..743f328 100644
--- a/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-nova-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Nova Component
+## OpenStack Nova Component
 
 *Available as of Camel 2.19*
 
 The openstack-nova component allows messages to be sent to an OpenStack compute services.
 
-[[openstack-nova-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-nova-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -36,9 +32,7 @@ openstack-nova://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-nova-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Nova component has no options.
@@ -66,17 +60,12 @@ The OpenStack Nova component supports 10 endpoint options which are listed below
 // endpoint options: END
 
 
-[[openstack-nova-Usage]]
-Usage
-^^^^^
+### Usage
 You can use following settings for each subsystem:
 
-flavors
-~~~~~~~
+### flavors
 
-[[openstack-nova-OperationsYouCanPerformWiththeFlavorProducer]]
-Operations you can perform with the Flavor producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Flavor producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -90,9 +79,7 @@ Operations you can perform with the Flavor producer
 |`delete` | Delete the flavor.
 |=========================================================================
 
-[[openstack-nova-MessageheadersevaluatedbytheFlavorProducer]]
-Message headers evaluated by the Flavor producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Flavor producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -117,12 +104,9 @@ Message headers evaluated by the Flavor producer
 
 If you need more precise flavor settings you can create new object of the type *org.openstack4j.model.compute.Flavor* and send in the message body.
 
-servers
-~~~~~~~
+### servers
 
-[[openstack-nova-OperationsYouCanPerformWiththeServerProducer]]
-Operations you can perform with the Server producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Server producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -140,9 +124,7 @@ Operations you can perform with the Server producer
 |`action` | Perform an action on the server.
 |=========================================================================
 
-[[openstack-nova-MessageheadersevaluatedbytheServerProducer]]
-Message headers evaluated by the Server producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Server producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -169,12 +151,9 @@ Message headers evaluated by the Server producer
 
 If you need more precise server settings you can create new object of the type *org.openstack4j.model.compute.ServerCreate* and send in the message body.
 
-keypairs
-~~~~~~~~
+### keypairs
 
-[[openstack-nova-OperationsYouCanPerformWiththeKeypairProducer]]
-Operations you can perform with the Keypair producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Keypair producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -189,9 +168,7 @@ Operations you can perform with the Keypair producer
 
 |=========================================================================
 
-[[openstack-nova-MessageheadersevaluatedbytheKeypairProducer]]
-Message headers evaluated by the Keypair producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Keypair producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -203,14 +180,11 @@ Message headers evaluated by the Keypair producer
 
 |=========================================================================
 
-[[CamelOpenstack-nova-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-openstack/src/main/docs/openstack-swift-component.adoc b/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
index e7581a0..f19769f 100644
--- a/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
+++ b/components/camel-openstack/src/main/docs/openstack-swift-component.adoc
@@ -1,12 +1,10 @@
-# OpenStack Swift Component
+## OpenStack Swift Component
 
 *Available as of Camel 2.19*
 
 The openstack-swift component allows messages to be sent to an OpenStack object storage services.
 
-[[openstack-swift-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -24,9 +22,7 @@ Maven users will need to add the following dependency to their pom.xml.
 where `${camel-version`} must be replaced by the actual version of Camel.
 
 
-[[openstack-swift-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 ----------------------------
@@ -36,9 +32,7 @@ openstack-swift://hosturl[?options]
 You can append query options to the URI in the following format
 `?options=value&option2=value&...`
 
-[[openstack-swift-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 // component options: START
 The OpenStack Swift component has no options.
@@ -66,17 +60,12 @@ The OpenStack Swift component supports 10 endpoint options which are listed belo
 // endpoint options: END
 
 
-[[openstack-swift-Usage]]
-Usage
-^^^^^
+### Usage
 You can use following settings for each subsystem:
 
-containers
-~~~~~~~~~~
+### containers
 
-[[openstack-swift-OperationsYouCanPerformWiththeContainerProducer]]
-Operations you can perform with the Container producer
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Container producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -98,9 +87,7 @@ Operations you can perform with the Container producer
 |`deleteMetadata` | Delete metadata.
 |=========================================================================
 
-[[openstack-swift-MessageheadersevaluatedbytheVolumeProducer]]
-Message headers evaluated by the Volume producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Volume producer
 
 [width="100%",cols="20%,10%,70%",options="header",]
 |=========================================================================
@@ -133,12 +120,9 @@ Message headers evaluated by the Volume producer
 If you need more precise container settings you can create new object of the type *org.openstack4j.model.storage.object.options.CreateUpdateContainerOptions* (in case of create or update operation)
 or *org.openstack4j.model.storage.object.options.ContainerListOptions* for listing containers and send in the message body.
 
-objects
-~~~~~~~
+### objects
 
-[[openstack-swift-OperationsYouCanPerformWiththeObjectsProducer]]
-Operations you can perform with the Object producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Operations you can perform with the Object producer
 [width="100%",cols="20%,80%",options="header",]
 |=========================================================================
 |Operation | Description
@@ -159,9 +143,7 @@ Operations you can perform with the Object producer
 
 |=========================================================================
 
-[[openstack-swift-MessageheadersevaluatedbytheObjectProducer]]
-Message headers evaluated by the Object producer
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Object producer
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=========================================================================
@@ -175,14 +157,11 @@ Message headers evaluated by the Object producer
 
 |=========================================================================
 
-[[CamelOpenstack-swift-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:openstack.html[openstack Component]
-
+* link:openstack.html[openstack Component]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc b/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
index e1ffa11..eb72003 100644
--- a/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
+++ b/components/camel-optaplanner/src/main/docs/optaplanner-component.adoc
@@ -1,4 +1,4 @@
-# OptaPlanner Component
+## OptaPlanner Component
 
 *Available as of Camel 2.13*
 
@@ -22,9 +22,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------------------------------
 
-[[OptaPlanner-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------
@@ -37,9 +35,7 @@ example `/org/foo/barSolverConfig.xml`.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[OptaPlanner-URIOptions]]
-OptaPlanner Options
-^^^^^^^^^^^
+### OptaPlanner Options
 
 
 // component options: START
@@ -68,9 +64,7 @@ The OptaPlanner component supports 8 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[OptaPlanner-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,10%,10%,60%",options="header",]
 |=======================================================================
@@ -82,9 +76,7 @@ Message Headers
 rather than blocking the current thread.
 |=======================================================================
 
-[[OptaPlanner-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 Camel takes the planning problem for the IN body, solves it and returns
 it on the OUT body. (since v 2.16) The IN body object supports the following use cases:
@@ -98,9 +90,7 @@ wait till isEveryProblemFactChangeProcessed before returning result.
 * If the body is none of the above types, then the producer will return
 the best result from the solver identified by solverId
 
-[[OptaPlanner-Termination]]
-Termination
-^^^^^^^^^^^
+### Termination
 
 The solving will take as long as specified in the `solverConfig`.
 
@@ -120,9 +110,7 @@ The solving will take as long as specified in the `solverConfig`.
 
 Â 
 
-[[OptaPlanner-Samples]]
-Samples
-+++++++
+#### Samples
 
 Solve an planning problem that's on the ActiveMQ queue with OptaPlanner:
 
@@ -140,12 +128,9 @@ from("cxfrs:bean:rsServer?bindingStyle=SimpleConsumer")
   .to("optaplanner:/org/foo/barSolverConfig.xml");
 -------------------------------------------------------
 
-[[OptaPlanner-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-paho/src/main/docs/paho-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc b/components/camel-paho/src/main/docs/paho-component.adoc
index 1dda450..c1c4a55 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -1,4 +1,4 @@
-# Paho Component
+## Paho Component
 
 INFO: Available as of Camel 2.16 
 
@@ -7,9 +7,7 @@ the https://eclipse.org/paho/[Eclipse Paho] library. Paho is one of the
 most popular MQTT libraries, so if you would like to integrate it with
 your Java project - Camel Paho connector is a way to go.
 
-[[Paho-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------
@@ -47,9 +45,7 @@ from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883").
 
 Â 
 
-[[Paho-Addingthecomponenttotheproject]]
-Adding the component to the project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding the component to the project
 
 Maven users will need to add the following dependency to their `pom.xml`
 for this component:
@@ -80,9 +76,7 @@ you need to add Eclipse Paho repository to your POM xml file:
 </repositories>
 --------------------------------------------------------------------------
 
-[[Paho-Defaultpayloadtype]]
-Default payload type
-^^^^^^^^^^^^^^^^^^^^
+### Default payload type
 
 Â 
 
@@ -118,9 +112,7 @@ String payload = "message";
 producerTemplate.sendBody("paho:topic", payload);
 --------------------------------------------------------------------------
 
-[[Paho-URIOptions]]
-Paho Options
-^^^^^^^^^^^^
+### Paho Options
 
 
 
@@ -167,9 +159,7 @@ The Paho component supports 12 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Paho-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 The following headers are recognized by the Paho component:
 
@@ -187,12 +177,9 @@ stored as a header but on the
 |=======================================================================
 Â 
 
-[[Paho-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc b/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
index 2a6320f..024d3b2 100644
--- a/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
+++ b/components/camel-paxlogging/src/main/docs/paxlogging-component.adoc
@@ -1,4 +1,4 @@
-# OSGi PAX Logging Component
+## OSGi PAX Logging Component
 
 *Available in Camel 2.6*
 
@@ -6,9 +6,7 @@ The `paxlogging` component can be used in an OSGi environment to receive
 http://wiki.ops4j.org/display/paxlogging/Pax+Logging[PaxLogging] events
 and process them.
 
-[[Pax-Logging-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 Maven users need to add the following dependency to their `pom.xml`
 
@@ -24,9 +22,7 @@ Maven users need to add the following dependency to their `pom.xml`
 where `${camel-version`} must be replaced by the actual version of Camel
 (2.6.0 or higher).
 
-[[Pax-Logging-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,xml]
 -----------------------------
@@ -36,9 +32,7 @@ paxlogging:appender[?options]
 where `appender` is the name of the pax appender that need to be
 configured in the PaxLogging service configuration.
 
-[[Pax-Logging-URIoptions]]
-URI options
-^^^^^^^^^^^
+### URI options
 
 
 
@@ -76,15 +70,11 @@ The OSGi PAX Logging component supports 5 endpoint options which are listed belo
 // endpoint options: END
 
 
-[[Pax-Logging-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
 
 The `in` message body will be set to the received PaxLoggingEvent.
 
-[[Pax-Logging-Exampleusage]]
-Example usage
-^^^^^^^^^^^^^
+### Example usage
 
 [source,xml]
 ----------------------------------
@@ -99,4 +89,4 @@ Configuration:
 [source,java]
 ----------------------------------------------------------
 log4j.rootLogger=INFO, out, osgi:VmLogAppender, osgi:camel
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-pdf/src/main/docs/pdf-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-pdf/src/main/docs/pdf-component.adoc b/components/camel-pdf/src/main/docs/pdf-component.adoc
index 052f899..6723202 100644
--- a/components/camel-pdf/src/main/docs/pdf-component.adoc
+++ b/components/camel-pdf/src/main/docs/pdf-component.adoc
@@ -1,4 +1,4 @@
-# PDF Component
+## PDF Component
 
 **Available as of Camel 2.16.0**
 
@@ -22,9 +22,7 @@ following dependency to their `pom.xml`:
 </dependency>
 ------------------------------------------------------------
 
-[[PDF-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The PDF component only supports producer endpoints.
 
@@ -33,9 +31,7 @@ The PDF component only supports producer endpoints.
 pdf:operation[?options]
 -----------------------
 
-[[PDF-Options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The PDF component has no options.
@@ -65,9 +61,7 @@ The PDF component supports 10 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[PDF-Headers]]
-Headers
-^^^^^^^
+### Headers
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
 |Header |Description
@@ -86,9 +80,7 @@ ishttps://pdfbox.apache.org/docs/1.8.9/javadocs/org/apache/pdfbox/pdmodel/encryp
 *Mandatory* header if PDF document is encrypted.
 |=======================================================================
 
-[[PDF-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -97,4 +89,4 @@ See Also
 
 -
 Â 
--
+-
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-pgevent/src/main/docs/pgevent-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-pgevent/src/main/docs/pgevent-component.adoc b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
index de2ef0b..6faaec4 100644
--- a/components/camel-pgevent/src/main/docs/pgevent-component.adoc
+++ b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
@@ -1,4 +1,4 @@
-# PostgresSQL Event Component
+## PostgresSQL Event Component
 
 This is a component for Apache Camel which allows for
 Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY
@@ -31,9 +31,7 @@ pgevent://host:port/database/channel[?parameters]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[PGEvent-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -65,12 +63,9 @@ The PostgresSQL Event component supports 11 endpoint options which are listed be
 // endpoint options: END
 
 
-[[PGEvent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-printer/src/main/docs/lpr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-printer/src/main/docs/lpr-component.adoc b/components/camel-printer/src/main/docs/lpr-component.adoc
index 8b07696..ecaf9b7 100644
--- a/components/camel-printer/src/main/docs/lpr-component.adoc
+++ b/components/camel-printer/src/main/docs/lpr-component.adoc
@@ -1,4 +1,4 @@
-# Printer Component
+## Printer Component
 
 *Available as of Camel 2.1*
 
@@ -27,9 +27,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Printer-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 Since the URI scheme for a printer has not been standardized (the
 nearest thing to a standard being the IETF print standard) and therefore
@@ -44,9 +42,7 @@ lpr://remotehost:port/path/to/printer[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Printer-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -81,25 +77,17 @@ The Printer component supports 14 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Printer-SendingMessagestoaPrinter]]
-Sending Messages to a Printer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending Messages to a Printer
 
-[[Printer-PrinterProducer]]
-Printer Producer
-++++++++++++++++
+#### Printer Producer
 
 Sending data to the printer is very straightforward and involves
 creating a producer endpoint that can be sent message exchanges on in
 route.
 
-[[Printer-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
 
-[[Printer-Example1:PrintingtextbasedpayloadsonaDefaultprinterusingletterstationaryandone-sidedmode]]
-Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode
 
 [source,java]
 -----------------------------------------------
@@ -114,9 +102,7 @@ RouteBuilder builder = new RouteBuilder() {
     }};
 -----------------------------------------------
 
-[[Printer-Example2:PrintingGIFbasedpayloadsonaRemoteprinterusingA4stationaryandone-sidedmode]]
-Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode
 
 [source,java]
 --------------------------------------------------
@@ -130,9 +116,7 @@ RouteBuilder builder = new RouteBuilder() {
    }};
 --------------------------------------------------
 
-[[Printer-Example3:PrintingJPEGbasedpayloadsonaRemoteprinterusingJapanesePostcardstationaryandone-sidedmode]]
-Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode
 
 [source,java]
 --------------------------------------------------
@@ -145,4 +129,4 @@ RouteBuilder builder = new RouteBuilder() {
            "&mediaSize=JAPANESE_POSTCARD" +
            "&flavor=DocFlavor.INPUT_STREAM")
     }};
---------------------------------------------------
+--------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
index f6610e4..abc66f6 100644
--- a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
+++ b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
@@ -1,4 +1,4 @@
-# Protobuf DataFormat
+## Protobuf DataFormat
 [[Protobuf-Protobuf-ProtocolBuffers]]
 Protobuf - Protocol Buffers
 ---------------------------
@@ -21,9 +21,7 @@ http://code.google.com/apis/protocolbuffers/[API Site] +
 http://code.google.com/apis/protocolbuffers/docs/javatutorial.html[Protobuf
 Java Tutorial]
 
-[[Protobuf-Options]]
-Protobuf Options
-^^^^^^^^^^^^^^^^
+### Protobuf Options
 
 // dataformat options: START
 The Protobuf dataformat supports 2 options which are listed below.
@@ -40,17 +38,13 @@ The Protobuf dataformat supports 2 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[Protobuf-Protobufoverview]]
-Protobuf overview
-~~~~~~~~~~~~~~~~~
+### Protobuf overview
 
 This quick overview of how to use Protobuf. For more detail see the
 http://code.google.com/apis/protocolbuffers/docs/javatutorial.html[complete
 tutorial]
 
-[[Protobuf-Definingtheprotoformat]]
-Defining the proto format
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Defining the proto format
 
 The first step is to define the format for the body of your exchange.
 This is defined in a .proto file as so:
@@ -89,9 +83,7 @@ message AddressBook {
 }
 ------------------------------------------------------------
 
-[[Protobuf-GeneratingJavaclasses]]
-Generating Java classes
-^^^^^^^^^^^^^^^^^^^^^^^
+### Generating Java classes
 
 The Protobuf SDK provides a compiler which will generate the Java
 classes for the format we defined in our .proto file. You can run the
@@ -110,9 +102,7 @@ to use a class that does not implement com.google.protobuf.Message. Use
 the generated builders to translate the data from any of your existing
 domain classes.
 
-[[Protobuf-JavaDSL]]
-Java DSL
-~~~~~~~~
+### Java DSL
 
 You can use create the ProtobufDataFormat instance and pass it to Camel
 DataFormat marshal and unmarsha API like this.
@@ -139,9 +129,7 @@ default instance class name like this.
    from("direct:unmarshalB").unmarshal().protobuf(Person.getDefaultInstance()).to("mock:reverse");
 --------------------------------------------------------------------------------------------------
 
-[[Protobuf-SpringDSL]]
-Spring DSL
-~~~~~~~~~~
+### Spring DSL
 
 The following example shows how to use Castor to unmarshal using Spring
 configuring the protobuf data type
@@ -159,9 +147,7 @@ configuring the protobuf data type
 </camelContext>
 ----------------------------------------------------------------------------------------------------------
 
-[[Protobuf-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Protobuf in your camel routes you need to add the a dependency on
 *camel-protobuf* which implements this data format.
@@ -177,4 +163,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-protobuf</artifactId>
   <version>2.2.0</version>
 </dependency>
------------------------------------------
+-----------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-quartz/src/main/docs/quartz-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-quartz/src/main/docs/quartz-component.adoc b/components/camel-quartz/src/main/docs/quartz-component.adoc
index a2c0df2..55ef207 100644
--- a/components/camel-quartz/src/main/docs/quartz-component.adoc
+++ b/components/camel-quartz/src/main/docs/quartz-component.adoc
@@ -1,4 +1,4 @@
-# Quartz Component
+## Quartz Component
 
 The *quartz:* component provides a scheduled delivery of messages using
 the http://www.quartz-scheduler.org/[Quartz Scheduler 1.x].  +
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Quartz-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------------------
@@ -41,9 +39,7 @@ name.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Quartz-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -115,9 +111,7 @@ required by the `QuartzScheduler` in the OSGi container. If you do not
 set any `id` on <camelContext> then +
  a unique id is auto assigned, and there is no problem.
 
-[[Quartz-Configuringquartz.propertiesfile]]
-Configuring quartz.properties file
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring quartz.properties file
 
 By default Quartz will look for a `quartz.properties` file in the
 `org/quartz` directory of the classpath. If you are using WAR
@@ -145,9 +139,7 @@ To do this you can configure this in Spring XML as follows
 </bean>
 -------------------------------------------------------------------------------
 
-[[Quartz-EnablingQuartzschedulerinJMX]]
-Enabling Quartz scheduler in JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Quartz scheduler in JMX
 
 You need to configure the quartz scheduler properties to enable JMX. +
  That is typically setting the option
@@ -157,9 +149,7 @@ configuration file.
 From Camel 2.13 onwards Camel will automatic set this option to true,
 unless explicit disabled.
 
-[[Quartz-StartingtheQuartzscheduler]]
-Starting the Quartz scheduler
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Starting the Quartz scheduler
 
 This is an example:
 
@@ -170,9 +160,7 @@ This is an example:
 </bean>
 ----------------------------------------------------------------------------
 
-[[Quartz-Clustering]]
-Clustering
-^^^^^^^^^^
+### Clustering
 
 *Available as of Camel 2.4*
 
@@ -184,9 +172,7 @@ allows the trigger to keep running on the other nodes in the cluster.
 *Note*: When running in clustered node no checking is done to ensure
 unique job name/group for endpoints.
 
-[[Quartz-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel adds the getters from the Quartz Execution Context as header
 values. The following headers are added: +
@@ -198,9 +184,7 @@ values. The following headers are added: +
 The `fireTime` header contains the `java.util.Date` of when the exchange
 was fired.
 
-[[Quartz-UsingCronTriggers]]
-Using Cron Triggers
-^^^^^^^^^^^^^^^^^^^
+### Using Cron Triggers
 
 Quartz supports
 http://www.quartz-scheduler.org/documentation/quartz-2.1.x/tutorials/crontrigger[Cron-like
@@ -235,9 +219,7 @@ valid URI syntax:
 |`+` | _Space_
 |=======================================================================
 
-[[Quartz-Specifyingtimezone]]
-Specifying time zone
-^^^^^^^^^^^^^^^^^^^^
+### Specifying time zone
 
 *Available as of Camel 2.8.1* +
  The Quartz Scheduler allows you to configure time zone per trigger. For
@@ -256,9 +238,7 @@ Converter] to be able configure this from the endpoint uri. +
  From Camel 2.8.1 onwards we have included such a
 link:type-converter.html[Type Converter] in the camel-core.
 
-[[Quartz-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -266,5 +246,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:quartz2.html[Quartz2]
-* link:timer.html[Timer]
-
+* link:timer.html[Timer]
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[06/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mail/src/main/docs/mail-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mail/src/main/docs/mail-component.adoc b/components/camel-mail/src/main/docs/mail-component.adoc
index 177051c..c1a3199 100644
--- a/components/camel-mail/src/main/docs/mail-component.adoc
+++ b/components/camel-mail/src/main/docs/mail-component.adoc
@@ -1,4 +1,4 @@
-# Mail Component
+## Mail Component
 
 The mail component provides access to Email via Spring's Mail support
 and the underlying JavaMail system.
@@ -44,9 +44,7 @@ environments where you need to send mails to a real mail server. Just
 the presence of the mock-javamail.jar on the classpath means that it
 will kick in and avoid sending the mails.
 
-[[Mail-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 Mail endpoints can have one of the following URI formats (for the
 protocols, SMTP, POP3, or IMAP, respectively):
@@ -73,8 +71,7 @@ You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
 
-[[Mail-Component-Options]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[Mail-Component-Options]]
 
 
 // component options: START
@@ -94,8 +91,7 @@ The Mail component supports 2 options which are listed below.
 
 
 
-[[Mail-Endpoint-Options]]
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[Mail-Endpoint-Options]]
 
 
 // endpoint options: START
@@ -175,9 +171,7 @@ The Mail component supports 63 endpoint options which are listed below:
 
 
 
-[[Mail-Sampleendpoints]]
-Sample endpoints
-++++++++++++++++
+#### Sample endpoints
 
 Typically, you specify a URI with login credentials as follows (taking
 SMTP as an example):
@@ -202,9 +196,7 @@ For example:
 smtp://mycompany.mailserver:30?password=tiger&username=scott
 ------------------------------------------------------------
 
-[[Mail-Components]]
-Components
-^^^^^^^^^^
+### Components
 
 - link:imap.html[IMAP]
 - link:imaps.html[IMAPs]
@@ -213,9 +205,7 @@ Components
 - link:smtp.html[STMP]
 - link:smtps.html[SMTPs]
 
-[[Mail-DefaultPortsDefaultports]]
-Default ports
-+++++++++++++
+#### Default ports
 
 Default port numbers are supported. If the port number is omitted, Camel
 determines the port number to use based on the protocol.
@@ -231,9 +221,7 @@ determines the port number to use based on the protocol.
 |`IMAPS` |`993`
 |=======================================================================
 
-[[Mail-SSLsupport]]
-SSL support
-^^^^^^^^^^^
+### SSL support
 
 The underlying mail framework is responsible for providing SSL support.
 Â You may either configure SSL/TLS support by completely specifying the
@@ -241,9 +229,7 @@ necessary Java Mail API configuration options, or you may provide a
 configured SSLContextParameters through the component or endpoint
 configuration.
 
-[[Mail-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
 
 As of *Camel 2.10*, the mail component supports SSL/TLS configuration
 through the link:camel-configuration-utilities.html[Camel JSSE
@@ -286,9 +272,7 @@ Spring DSL based configuration of endpoint
 <to uri="smtps://smtp.google.com?username=[hidden email]&password=password&sslContextParameters=#sslContextParameters"/>...
 ---------------------------------------------------------------------------------------------------------------------------
 
-[[Mail-ConfiguringJavaMailDirectly]]
-Configuring JavaMail Directly
-+++++++++++++++++++++++++++++
+#### Configuring JavaMail Directly
 
 Camel uses SUN JavaMail, which only trusts certificates issued by well
 known Certificate Authorities (the default JVM trust configuration). If
@@ -296,9 +280,7 @@ you issue your own certificates, you have to import the CA certificates
 into the JVM's Java trust/key store files, override the default JVM
 trust/key store files (see `SSLNOTES.txt` in JavaMail for details).
 
-[[Mail-MailMessageContent]]
-Mail Message Content
-^^^^^^^^^^^^^^^^^^^^
+### Mail Message Content
 
 Camel uses the message exchange's IN body as the
 http://java.sun.com/javaee/5/docs/api/javax/mail/internet/MimeMessage.html[MimeMessage]
@@ -321,9 +303,7 @@ server, you should be able to get the message id of the
 http://java.sun.com/javaee/5/docs/api/javax/mail/internet/MimeMessage.html[MimeMessage]
 with the key `CamelMailMessageId` from the Camel message header.
 
-[[Mail-Headerstakeprecedenceoverpre-configuredrecipients]]
-Headers take precedence over pre-configured recipients
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Headers take precedence over pre-configured recipients
 
 The recipients specified in the message headers always take precedence
 over recipients pre-configured in the endpoint URI. The idea is that if
@@ -349,9 +329,7 @@ pre-configured settings.
         template.sendBodyAndHeaders("smtp://admin@localhost?to=[hidden email]", "Hello World", headers);
 ------------------------------------------------------------------------------------------------------------
 
-[[Mail-Multiplerecipientsforeasierconfiguration]]
-Multiple recipients for easier configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Multiple recipients for easier configuration
 
 It is possible to set multiple recipients using a comma-separated or a
 semicolon-separated list. This applies both to header settings and to
@@ -365,9 +343,7 @@ settings in an endpoint URI. For example:
 
 The preceding example uses a semicolon, `;`, as the separator character.
 
-[[Mail-Settingsendernameandemail]]
-Setting sender name and email
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting sender name and email
 
 You can specify recipients in the format, `name <email>`, to include
 both the name and the email address of the recipient.
@@ -383,9 +359,7 @@ map.put("From", "James Strachan <[hidden email]>");
 map.put("Subject", "Camel is cool");
 ---------------------------------------------------------
 
-[[Mail-JavaMailAPI(exSUNJavaMail)]]
-JavaMail API (ex SUN JavaMail)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### JavaMail API (ex SUN JavaMail)
 
 https://java.net/projects/javamail/pages/Home[JavaMail API] is used
 under the hood for consuming and producing mails. +
@@ -401,9 +375,7 @@ IMAP API]
 https://javamail.java.net/nonav/docs/api/javax/mail/Flags.html[MAIL
 Flags]
 
-[[Mail-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 We start with a simple route that sends the messages received from a JMS
 queue as emails. The email account is the `admin` account on
@@ -427,9 +399,7 @@ from("imap://[hidden email]
 
 In this sample we want to send a mail to multiple recipients:
 
-[[Mail-Sendingmailwithattachmentsample]]
-Sending mail with attachment sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending mail with attachment sample
 
 
 WARNING: *Attachments are not support by all Camel components*
@@ -445,9 +415,7 @@ The mail component supports attachments. In the sample below, we send a
 mail message containing a plain text message with a logo file
 attachment.
 
-[[Mail-SSLsample]]
-SSL sample
-^^^^^^^^^^
+### SSL sample
 
 In this sample, we want to poll our Google mail inbox for mails. To
 download mail onto a local mail client, Google mail requires you to
@@ -476,9 +444,7 @@ progress in the logs:
 2008-05-08 06:32:12,187 INFO  newmail - Exchange[MailMessage: messageNumber=[332], from=[James Bond <[hidden email]>], to=[hidden email]], subject=[...
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[Mail-Consumingmailswithattachmentsample]]
-Consuming mails with attachment sample
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming mails with attachment sample
 
 In this sample we poll a mailbox and store all attachments from the
 mails as files. First, we define a route to poll the mailbox. As this
@@ -523,9 +489,7 @@ As you can see the API to handle attachments is a bit clunky but it's
 there so you can get the `javax.activation.DataHandler` so you can
 handle the attachments using standard API.
 
-[[Mail-Howtosplitamailmessagewithattachments]]
-How to split a mail message with attachments
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to split a mail message with attachments
 
 In this example we consume mail messages which may have a number of
 attachments. What we want to do is to use the
@@ -570,9 +534,7 @@ SplitAttachmentsExpression split = SplitAttachmentsExpression(true);
 
 And then use the expression with the splitter eip.
 
-[[Mail-UsingcustomSearchTerm]]
-Using custom SearchTerm
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using custom SearchTerm
 
 *Available as of Camel 2.11*
 
@@ -660,12 +622,9 @@ builder.unseen().body(Op.not, "Spam").subject(Op.not, "Spam")
 SearchTerm term = builder.build();
 --------------------------------------------------------------
 
-[[Mail-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc b/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
index 80c6498..52f3675 100644
--- a/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
+++ b/components/camel-mail/src/main/docs/mime-multipart-dataformat.adoc
@@ -1,4 +1,4 @@
-# MIME Multipart DataFormat
+## MIME Multipart DataFormat
 
 *Available as of Camel 2.17*
 
@@ -40,9 +40,7 @@ empty message. Up to Camel version 2.17.1 this will happen all message
 bodies that do not contain a MIME multipart message regardless of body
 type and stream cache setting.
 
-[[MIME-Multipart-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The MIME Multipart dataformat supports 6 options which are listed below.
@@ -63,9 +61,7 @@ The MIME Multipart dataformat supports 6 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[MIME-Multipart-MessageHeadersmarshal]]
-Message Headers (marshal)
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Headers (marshal)
 
 [width="100%",cols="20%,20%,60%",options="header",]
 |=======================================================================
@@ -89,9 +85,7 @@ body part. Furthermore the given charset is applied for text to binary
 conversions.
 |=======================================================================
 
-[[MIME-Multipart-MessageHeadersunmarshal]]
-Message Headers (unmarshal)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Headers (unmarshal)
 
 [width="100%",cols="20%,20%,60%",options="header",]
 |=======================================================================
@@ -111,9 +105,7 @@ from MIME endoding descriptor to Java encoding descriptor)
 MIME multipart. The header is removed afterwards
 |=======================================================================
 
-[[MIME-Multipart-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 [source,java]
 -----------------------------------
@@ -191,9 +183,7 @@ Content-Disposition: attachment; filename="Attachment File Name"
 ------=_Part_0_1134128170.1447659361365
 ----------------------------------------------------------------
 
-[[MIME-Multipart-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use MIME-Multipart in your Camel routes you need to add a dependency
 on *camel-mail* which implements this data format.
@@ -207,4 +197,4 @@ If you use Maven you can just add the following to your pom.xml:
   <artifactId>camel-mail</artifactId>
   <version>x.x.x</version> <!-- use the same version as your Camel core version -->
 </dependency>
------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-metrics/src/main/docs/metrics-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-metrics/src/main/docs/metrics-component.adoc b/components/camel-metrics/src/main/docs/metrics-component.adoc
index cec5e5f..1e14bbc 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -1,4 +1,4 @@
-# Metrics Component
+## Metrics Component
 ifdef::env-github[]
 :caution-caption: :boom:
 :important-caption: :exclamation:
@@ -7,9 +7,7 @@ ifdef::env-github[]
 :warning-caption: :warning:
 endif::[]
 
-[[MetricsComponent-MetricsComponent]]
-Metrics Component
-~~~~~~~~~~~~~~~~~
+### Metrics Component
 
 *Available as of Camel 2.14*
 
@@ -36,18 +34,14 @@ for this component:
 </dependency>
 ----
 
-[[MetricsComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source]
 ----
 metrics:[ meter | counter | histogram | timer | gauge ]:metricname[?options]
 ----
 
-[[MetricsComponent-options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The Metrics component supports 1 options which are listed below.
@@ -86,9 +80,7 @@ The Metrics component supports 9 endpoint options which are listed below:
 
 
 
-[[MetricsComponent-registryMetricRegistry]]
-[[MetricsComponent-registry]]Metric Registry
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-registry]]Metric Registry
 
 Camel Metrics component uses by default a `MetricRegistry` instance with
 a `Slf4jReporter` that has a 60 second reporting interval.
@@ -150,9 +142,7 @@ public API in version DropWizard `3.0.1` for users to clean up on exit. Thus usi
 Camel Metrics Component leads to Java classloader leak and my cause
 `OutOfMemoryErrors` in some cases.
 
-[[MetricsComponent-Usage]]
-Usage
-^^^^^
+### Usage
 
 Each metric has type and name. Supported types are
 link:#MetricsComponent-counter[counter],
@@ -160,9 +150,7 @@ link:#MetricsComponent-histogram[histogram], link:#MetricsComponent-meter[meter
 link:#MetricsComponent-timer[timer] and link:#MetricsComponent-gauge[gauge].
 Metric name is simple string. If metric type is not provided then type meter is used by default.
 
-[[MetricsComponent-Headers]]
-Headers
-+++++++
+#### Headers
 
 Metric name defined in URI can be overridden by using header with name
 `CamelMetricsName`.
@@ -184,18 +172,14 @@ endpoint finishes processing of exchange. While processing exchange
 Metrics endpoint will catch all exceptions and write log entry using
 level `warn`.
 
-[[MetricsComponent-counterMetricstypecounter]]
-[[MetricsComponent-counter]]Metrics type counter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-counter]]Metrics type counter
 
 [source]
 ----
 metrics:counter:metricname[?options]
 ----
 
-[[MetricsComponent-Options]]
-Options
-+++++++
+#### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=====================================================
@@ -232,9 +216,7 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-Headers.1]]
-Headers
-+++++++
+#### Headers
 
 Message headers can be used to override `increment` and `decrement`
 values specified in Metrics component URI.
@@ -265,18 +247,14 @@ from("direct:in")
 
 ----
 
-[[MetricsComponent-histogramMetrictypehistogram]]
-[[MetricsComponent-histogram]]Metric type histogram
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-histogram]]Metric type histogram
 
 [source]
 ----
 metrics:histogram:metricname[?options]
 ----
 
-[[MetricsComponent-Options.1]]
-Options
-+++++++
+#### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |===================================
@@ -304,9 +282,7 @@ from("direct:in")
 
 ----
 
-[[MetricsComponent-Headers.2]]
-Headers
-+++++++
+#### Headers
 
 Message header can be used to override value specified in Metrics
 component URI.
@@ -327,18 +303,14 @@ from("direct:in")
 
 ----
 
-[[MetricsComponent-meterMetrictypemeter]]
-[[MetricsComponent-meter]]Metric type meter
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-meter]]Metric type meter
 
 [source]
 ----
 metrics:meter:metricname[?options]
 ----
 
-[[MetricsComponent-Options.2]]
-Options
-+++++++
+#### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |===================================
@@ -364,9 +336,7 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-Headers.3]]
-Headers
-+++++++
+#### Headers
 
 Message header can be used to override `mark` value specified in Metrics
 component URI.
@@ -386,18 +356,14 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-timerMetricstypetimer]]
-[[MetricsComponent-timer]]Metrics type timer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-timer]]Metrics type timer
 
 [source]
 ----
 metrics:timer:metricname[?options]
 ----
 
-[[MetricsComponent-Options.3]]
-Options
-+++++++
+#### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |==========================
@@ -422,9 +388,7 @@ from("direct:in")
 `TimerContext` objects are stored as Exchange properties between
 different Metrics component calls.
 
-[[MetricsComponent-Headers.4]]
-Headers
-+++++++
+#### Headers
 
 Message header can be used to override action value specified in Metrics
 component URI.
@@ -445,18 +409,14 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-gaugeMetrictypegauge]]
-[[MetricsComponent-gauge]]Metric type gauge
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### [[MetricsComponent-gauge]]Metric type gauge
 
 [source]
 ----
 metrics:gauge:metricname[?options]
 ----
 
-[[MetricsComponent-Options.4]]
-Options
-+++++++
+#### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=====================================================
@@ -474,9 +434,7 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-Headers.5]]
-Headers
-+++++++
+#### Headers
 
 Message headers can be used to override `subject` values specified in Metrics component URI.
 Note: if `CamelMetricsName` header is specified, then new gauge is registered in addition to
@@ -497,9 +455,7 @@ from("direct:in")
     .to("direct:out");
 ----
 
-[[MetricsComponent-MetricsRoutePolicyFactory]]
-MetricsRoutePolicyFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### MetricsRoutePolicyFactory
 
 This factory allows to add a link:routepolicy.html[RoutePolicy] for each
 route which exposes route utilization statistics using Dropwizard metrics.
@@ -577,9 +533,7 @@ if (registryService != null) {
 }
 ----
 
-[[MetricsComponent-MetricsMessageHistoryFactory]]
-MetricsMessageHistoryFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### MetricsMessageHistoryFactory
 
 *Available as of Camel 2.17*
 
@@ -655,9 +609,7 @@ String json = service.dumpStatisticsAsJson();
 And the JMX API the MBean is registered in the `type=services` tree
 with `name=MetricsMessageHistoryService`.
 
-[[MetricsComponent-InstrumentedThreadPoolFactory]]
-InstrumentedThreadPoolFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### InstrumentedThreadPoolFactory
 
 *Available as of Camel 2.18*
 
@@ -666,9 +618,7 @@ which collects information from inside of Camel.
 See more details at link:advanced-configuration-of-camelcontext-using-spring.html[Advanced configuration of CamelContext using Spring]
 
 
-[[MetricsComponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * The `camel-example-cdi-metrics` example that illustrates the integration
-  between Camel, Metrics and CDI.
+  between Camel, Metrics and CDI.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mina/src/main/docs/mina-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mina/src/main/docs/mina-component.adoc b/components/camel-mina/src/main/docs/mina-component.adoc
index 47e641b..05c3854 100644
--- a/components/camel-mina/src/main/docs/mina-component.adoc
+++ b/components/camel-mina/src/main/docs/mina-component.adoc
@@ -1,4 +1,4 @@
-# Mina Component
+## Mina Component
 
 *Deprecated*
 
@@ -21,9 +21,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MINA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------
@@ -57,9 +55,7 @@ exchange itself over the wire. See options below.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[MINA-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -124,9 +120,7 @@ The Mina component supports 24 endpoint options which are listed below:
 
 
 
-[[MINA-Usingacustomcodec]]
-Using a custom codec
-^^^^^^^^^^^^^^^^^^^^
+### Using a custom codec
 
 See the http://mina.apache.org/tutorial-on-protocolcodecfilter.html[Mina
 documentation] how to write your own codec. To use your custom codec
@@ -135,9 +129,7 @@ link:registry.html[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 link:hl7.html[HL7] that has a custom codec.
 
-[[MINA-Samplewithsync=false]]
-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
@@ -146,9 +138,7 @@ Mina consumer endpoint that listens on port 6200:
 As the sample is part of a unit test, we test it by sending some data to
 it on port 6200.
 
-[[MINA-Samplewithsync=true]]
-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
@@ -160,9 +150,7 @@ using the `template.requestBody()` method. As we know the response is a
 `String`, we cast it to `String` and can assert that the response is, in
 fact, something we have dynamically set in our processor code logic.
 
-[[MINA-SamplewithSpringDSL]]
-Sample with Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with Spring DSL
 
 Spring DSL can, of course, also be used for link:mina.html[MINA]. In the
 sample below we expose a TCP server on port 5555:
@@ -188,9 +176,7 @@ could be implemented as follows:
    }
 -----------------------------------------------
 
-[[MINA-ConfiguringMinaendpointsusingSpringbeanstyle]]
-Configuring Mina endpoints using Spring bean style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina endpoints using Spring bean style
 
 Configuration of Mina endpoints is possible using regular Spring bean
 style configuration in the Spring DSL.
@@ -206,9 +192,7 @@ The sample below shows the factory approach:
 
 And then we can refer to our endpoint directly in the route, as follows:
 
-[[MINA-ClosingSessionWhenComplete]]
-Closing Session When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Session When Complete
 
 When acting as a server you sometimes want to close the session when,
 for example, a client conversion is finished. To instruct Camel to close
@@ -229,9 +213,7 @@ written the `bye` message back to the client:
         });
 --------------------------------------------------------------------------------------------------
 
-[[MINA-GettheIoSessionformessage]]
-Get the IoSession for message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Get the IoSession for message
 
 *Available since Camel 2.1*
 You can get the IoSession from the message header with this key
@@ -239,9 +221,7 @@ MinaEndpoint.HEADER_MINA_IOSESSION, and also get the local host address
 with the key MinaEndpoint.HEADER_LOCAL_ADDRESS and remote host address
 with the key MinaEndpoint.HEADER_REMOTE_ADDRESS.
 
-[[MINA-ConfiguringMinafilters]]
-Configuring Mina filters
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina filters
 
 Filters permit you to use some Mina Filters, such as `SslFilter`. You
 can also implement some customized filters. Please note that `codec` and
@@ -334,9 +314,7 @@ Then, you can configure your endpoint using Spring DSL:
 </bean>
 ----------------------------------------------------------------------------------
 
-[[MINA-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -344,5 +322,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:mina2.html[MINA2]
-* link:netty.html[Netty]
-
+* link:netty.html[Netty]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mina2/src/main/docs/mina2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mina2/src/main/docs/mina2-component.adoc b/components/camel-mina2/src/main/docs/mina2-component.adoc
index 1975038..ab73083 100644
--- a/components/camel-mina2/src/main/docs/mina2-component.adoc
+++ b/components/camel-mina2/src/main/docs/mina2-component.adoc
@@ -1,4 +1,4 @@
-# Mina2 Component
+## Mina2 Component
 
 *Available as of Camel 2.10*
 
@@ -24,9 +24,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MINA2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------
@@ -58,9 +56,7 @@ exchange itself over the wire. See options below.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[MINA2-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -130,9 +126,7 @@ The Mina2 component supports 29 endpoint options which are listed below:
 
 
 
-[[MINA2-Usingacustomcodec]]
-Using a custom codec
-^^^^^^^^^^^^^^^^^^^^
+### Using a custom codec
 
 See the Mina how to write your own codec. To use your custom codec with
 `camel-mina`, you should register your codec in the
@@ -140,9 +134,7 @@ link:registry.html[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 link:hl7.html[HL7] that has a custom codec.
 
-[[MINA2-Samplewithsyncfalse]]
-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
@@ -166,9 +158,7 @@ template.sendBody("mina2:tcp://localhost:" + port1 + "?textline=true&sync=false"
 assertMockEndpointsSatisfied();
 -------------------------------------------------------------------------------------------------
 
-[[MINA2-Samplewithsynctrue]]
-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
@@ -196,9 +186,7 @@ String response = (String)template.requestBody("mina2:tcp://localhost:" + port2
 assertEquals("Bye World", response);
 -----------------------------------------------------------------------------------------------------------------------
 
-[[MINA2-SamplewithSpringDSL]]
-Sample with Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^
+### Sample with Spring DSL
 
 Spring DSL can, of course, also be used for link:mina.html[MINA]. In the
 sample below we expose a TCP server on port 5555:
@@ -224,9 +212,7 @@ could be implemented as follows:
    }
 -----------------------------------------------
 
-[[MINA2-ClosingSessionWhenComplete]]
-Closing Session When Complete
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Closing Session When Complete
 
 When acting as a server you sometimes want to close the session when,
 for example, a client conversion is finished. To instruct Camel to close
@@ -247,18 +233,14 @@ written the `bye` message back to the client:
         });
 ---------------------------------------------------------------------------------------------------
 
-[[MINA2-GettheIoSessionformessage]]
-Get the IoSession for message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Get the IoSession for message
 
 You can get the IoSession from the message header with this key
 `Mina2Constants.MINA_IOSESSION`, and also get the local host address
 with the key `Mina2Constants.MINA_LOCAL_ADDRESS` and remote host address
 with the key `Mina2Constants.MINA_REMOTE_ADDRESS`.
 
-[[MINA2-ConfiguringMinafilters]]
-Configuring Mina filters
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring Mina filters
 
 Filters permit you to use some Mina Filters, such as `SslFilter`. You
 can also implement some customized filters. Please note that `codec` and
@@ -266,9 +248,7 @@ can also implement some customized filters. Please note that `codec` and
 filters you may define are appended to the end of the filter chain; that
 is, after `codec` and `logger`.
 
-[[MINA2-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -276,5 +256,4 @@ See Also
 * link:getting-started.html[Getting Started]
 
 * link:mina.html[MINA]
-* link:netty.html[Netty]
-
+* link:netty.html[Netty]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mllp/src/main/docs/mllp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mllp/src/main/docs/mllp-component.adoc b/components/camel-mllp/src/main/docs/mllp-component.adoc
index f9875bc..fe9d081 100644
--- a/components/camel-mllp/src/main/docs/mllp-component.adoc
+++ b/components/camel-mllp/src/main/docs/mllp-component.adoc
@@ -1,4 +1,4 @@
-# MLLP Component
+## MLLP Component
 
 *available as of Camel 2.17*
 
@@ -35,9 +35,7 @@ for this component:
 </dependency>
 ---------------------------------------------------------
 
-[[MLLP-MLLPOptions]]
-MLLP Options
-~~~~~~~~~~~~
+### MLLP Options
 
 
 
@@ -93,9 +91,7 @@ The MLLP component supports 24 endpoint options which are listed below:
 
 
 
-[[MLLP-MLLPConsumer]]
-MLLP Consumer
-~~~~~~~~~~~~~
+### MLLP Consumer
 
 The MLLP Consumer supports receiving MLLP-framed messages and sending
 HL7 Acknowledgements.  The MLLP Consumer can automatically generate the
@@ -105,9 +101,7 @@ the CamelMllpAcknowledgement exchange property.  Additionally, the type
 of acknowledgement that will be generated can be controlled by setting
 the CamelMllpAcknowledgementType exchange property.
 
-[[MLLP-MessageHeaders]]
-*Message Headers*
-^^^^^^^^^^^^^^^^^
+### *Message Headers*
 
 The MLLP Consumer adds these headers on the Camel message:
 
@@ -134,9 +128,7 @@ The MLLP Consumer adds these headers on the Camel message:
 All headers are String types. If a header value is missing, its value
 is null.
 
-[[MLLP-ExchangeProperties]]
-*Exchange Properties*
-^^^^^^^^^^^^^^^^^^^^^
+### *Exchange Properties*
 
 The type of acknowledgment the MLLP Consumer generates can be controlled
 by these properties on the Camel exchange:
@@ -151,13 +143,9 @@ by these properties on the Camel exchange:
 All headers are String types. If a header value is missing, its value
 is null.
 
-[[MLLP-ConsumerConfiguration]]
-Consumer Configuration
-^^^^^^^^^^^^^^^^^^^^^^
+### Consumer Configuration
 
-[[MLLP-MLLPProducer]]
-MLLP Producer
-~~~~~~~~~~~~~
+### MLLP Producer
 
 The MLLP Producer supports sending MLLP-framed messages and receiving
 HL7 Acknowledgements.  The MLLP Producer interrogates the HL7
@@ -165,9 +153,7 @@ Acknowledgments and raises exceptions if a negative acknowledgement is
 received.  The received acknowledgement is interrogated and an exception
 is raised in the event of a negative acknowledgement.
 
-[[MLLP-MessageHeaders.1]]
-*Message Headers*
-^^^^^^^^^^^^^^^^^
+### *Message Headers*
 
 The MLLP Producer adds these headers on the Camel message:
 
@@ -181,7 +167,4 @@ The MLLP Producer adds these headers on the Camel message:
 |===================================
 
 All headers are String types. If a header value is missing, its value
-is null.
-
-
-
+is null.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc b/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
index f66c8af..67525ea 100644
--- a/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
+++ b/components/camel-mongodb-gridfs/src/main/docs/gridfs-component.adoc
@@ -1,4 +1,4 @@
-# MongoDBGridFS Component
+## MongoDBGridFS Component
 
 *Available as of Camel 2.17*
 
@@ -15,18 +15,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MongoDBGridFS-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
 
 [source,java]
 ------------------------------------------------------------------------------
 gridfs:connectionBean?database=databaseName&bucket=bucketName[&moreOptions...]
 ------------------------------------------------------------------------------
 
-[[MongoDBGridFS-options]]
-MongoDB GridFS options
-~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB GridFS options
 
 
 // component options: START
@@ -67,9 +63,7 @@ The MongoDBGridFS component supports 18 endpoint options which are listed below:
 
 
 
-[[MongoDBGridFS-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
 
 The following Spring XML creates a bean defining the connection to a
 MongoDB instance.
@@ -86,9 +80,7 @@ MongoDB instance.
 </beans>
 ----------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDBGridFS-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
 
 The following route defined in Spring XML executes the operation
 link:mongodb-gridfs.html[*findOne*] on a collection.
@@ -107,13 +99,9 @@ link:mongodb-gridfs.html[*findOne*] on a collection.
 
 Â 
 
-[[MongoDBGridFS-GridFSoperations-producerendpoint]]
-GridFS operations - producer endpoint
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### GridFS operations - producer endpoint
 
-[[MongoDBGridFS-count]]
-count
-+++++
+#### count
 
 Returns the total number of file in the collection, returning an Integer
 as the OUT message body. +
@@ -136,9 +124,7 @@ headers.put(Exchange.FILE_NAME, "filename.txt");
 Integer count = template.requestBodyAndHeaders("direct:count", query, headers);
 -------------------------------------------------------------------------------
 
-[[MongoDBGridFS-listAll]]
-listAll
-+++++++
+#### listAll
 
 Returns an Reader that lists all the filenames and their IDs in a tab
 separated stream.
@@ -154,9 +140,7 @@ filename2.txt   2897651254
 
 Â 
 
-[[MongoDBGridFS-findOne]]
-*findOne*
-+++++++++
+#### *findOne*
 
 Finds a file in the GridFS system and sets the body to an InputStream of
 the content.   Also provides the metadata has headers.  It uses
@@ -173,9 +157,7 @@ InputStream result = template.requestBodyAndHeaders("direct:findOne", "irrelevan
 
 Â 
 
-[[MongoDBGridFS-create]]
-create
-++++++
+#### create
 
 Creates a new file in the GridFs database. It uses the
 Exchange.FILE_NAME from the incoming headers for the name and the body
@@ -190,9 +172,7 @@ InputStream stream = ... the data for the file ...
 template.requestBodyAndHeaders("direct:create", stream, headers);
 ------------------------------------------------------------------------
 
-[[MongoDBGridFS-remove]]
-remove
-++++++
+#### remove
 
 Removes a file from the GridFS database.
 
@@ -204,9 +184,7 @@ headers.put(Exchange.FILE_NAME, "filename.txt");
 template.requestBodyAndHeaders("direct:remove", "", headers);
 ------------------------------------------------------------------------
 
-[[MongoDBGridFS-GridFSConsumer]]
-GridFS Consumer
-^^^^^^^^^^^^^^^
+### GridFS Consumer
 
 See also
 
@@ -216,5 +194,4 @@ See also
 current version]
 *
 http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb/src/main/docs/mongodb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb/src/main/docs/mongodb-component.adoc b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
index ff04df5..e3c5222 100644
--- a/components/camel-mongodb/src/main/docs/mongodb-component.adoc
+++ b/components/camel-mongodb/src/main/docs/mongodb-component.adoc
@@ -1,4 +1,4 @@
-# MongoDB Component
+## MongoDB Component
 
 *Available as of Camel 2.10*
 
@@ -40,18 +40,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MongoDB-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
 
 [source,java]
 ---------------------------------------------------------------------------------------------------------------
 mongodb:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
 ---------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-options]]
-MongoDB options
-~~~~~~~~~~~~~~~
+### MongoDB options
 
 
 // component options: START
@@ -103,9 +99,7 @@ The MongoDB component supports 24 endpoint options which are listed below:
 
 
 
-[[MongoDB-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
 
 The following Spring XML creates a bean defining the connection to a
 MongoDB instance.
@@ -123,9 +117,7 @@ MongoDB instance.
 </beans>
 ----------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
 
 The following route defined in Spring XML executes the operation
 link:mongodb.html[*dbStats*] on a collection.
@@ -142,17 +134,11 @@ link:mongodb.html[*dbStats*] on a collection.
 </route>
 ---------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-MongoDBoperations-producerendpoints]]
-MongoDB operations - producer endpoints
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB operations - producer endpoints
 
-[[MongoDB-Queryoperations]]
-Query operations
-^^^^^^^^^^^^^^^^
+### Query operations
 
-[[MongoDB-findById]]
-findById
-++++++++
+#### findById
 
 This operation retrieves only one element from the collection whose _id
 field matches the content of the IN message body. The incoming object
@@ -172,9 +158,7 @@ from("direct:findById")
 TIP: *Supports optional parameters*. This operation supports specifying a fields filter. See
 link:mongodb.html[Specifying optional parameters].
 
-[[MongoDB-findOneByQuery]]
-findOneByQuery
-++++++++++++++
+#### findOneByQuery
 
 Use this operation to retrieve just one element from the collection that
 matches a MongoDB query. *The query object is extracted from the IN
@@ -204,9 +188,7 @@ from("direct:findOneByQuery")
 TIP: *Supports optional parameters*. This operation supports specifying a fields filter and/or a sort clause. See
 link:mongodb.html[Specifying optional parameters].
 
-[[MongoDB-findAll]]
-findAll
-+++++++
+#### findAll
 
 The `findAll` operation returns all documents matching a query, or none
 at all, in which case all documents contained in the collection are
@@ -276,9 +258,7 @@ consideration. |int/Integer
 TIP: *Supports optional parameters*. This operation supports specifying a fields filter and/or a sort clause. See
 link:mongodb.html[Specifying optional parameters].
 
-[[MongoDB-count]]
-count
-+++++
+#### count
 
 Returns the total number of objects in a collection, returning a Long as
 the OUT message body. +
@@ -307,9 +287,7 @@ DBObject query = ...
 Long count = template.requestBodyAndHeader("direct:count", query, MongoDbConstants.COLLECTION, "dynamicCollectionName");
 ------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Specifyingoptionalparameters]]
-Specifying a fields filter (projection)
-+++++++++++++++++++++++++++++++++++++++
+#### Specifying a fields filter (projection)
 
 Query operations will, by default, return the matching objects in their
 entirety (with all their fields). If your documents are large and you
@@ -330,8 +308,7 @@ DBObject fieldFilter = BasicDBObjectBuilder.start().add("_id", 0).add("boringFie
 Object result = template.requestBodyAndHeader("direct:findAll", (Object) null, MongoDbConstants.FIELDS_FILTER, fieldFilter);
 ----------------------------------------------------------------------------------------------------------------------------
 
-Specifying a sort clause
-++++++++++++++++++++++++
+#### Specifying a sort clause
 
 There is a often a requirement to fetch the min/max record from a
 collection based on sorting by a particular field. In Mongo the
@@ -364,13 +341,9 @@ to a single field, based on the `documentTimestamp` field:
 ----------------------------------------------------------------------------------------------------------------------------
 
 
-[[MongoDB-Create/updateoperations]]
-Create/update operations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Create/update operations
 
-[[MongoDB-insert]]
-insert
-++++++
+#### insert
 
 Inserts an new object into the MongoDB collection, taken from the IN
 message body. Type conversion is attempted to turn it into `DBObject` or
@@ -417,9 +390,7 @@ constant). The value stored is `org.bson.types.ObjectId` for single
 insert or `java.util.List<org.bson.types.ObjectId>` if multiple records
 have been inserted.
 
-[[MongoDB-save]]
-save
-++++
+#### save
 
 The save operation is equivalent to an _upsert_ (UPdate, inSERT)
 operation, where the record will be updated, and if it doesn't exist, it
@@ -449,9 +420,7 @@ from("direct:insert")
     .to("mongodb:myDb?database=flights&collection=tickets&operation=save");
 ---------------------------------------------------------------------------
 
-[[MongoDB-update]]
-update
-++++++
+#### update
 
 Update one or multiple records on the collection. Requires a
 List<DBObject> as the IN message body containing exactly 2 elements:
@@ -495,13 +464,9 @@ DBObject updateObj = new BasicDBObject("$set", new BasicDBObject("scientist", "D
 Object result = template.requestBodyAndHeader("direct:update", new Object[] {filterField, updateObj}, MongoDbConstants.MULTIUPDATE, true);
 ------------------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Deleteoperations]]
-Delete operations
-^^^^^^^^^^^^^^^^^
+### Delete operations
 
-[[MongoDB-remove]]
-remove
-++++++
+#### remove
 
 Remove matching records from the collection. The IN message body will
 act as the removal filter query, and is expected to be of type
@@ -522,13 +487,9 @@ A header with key `CamelMongoDbRecordsAffected` is returned
 containing the number of records deleted (copied from
 `WriteResult.getN()`).
 
-[[MongoDB-Otheroperations]]
-Other operations
-^^^^^^^^^^^^^^^^
+### Other operations
 
-[[MongoDB-aggregate]]
-aggregate
-+++++++++
+#### aggregate
 
 *Available as of Camel 2.14*
 
@@ -546,9 +507,7 @@ from("direct:aggregate")
     .to("mock:resultAggregate");
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-getDbStats]]
-getDbStats
-++++++++++
+#### getDbStats
 
 Equivalent of running the `db.stats()` command in the MongoDB shell,
 which displays useful statistic figures about the database. +
@@ -585,9 +544,7 @@ assertTrue("Result is not of type DBObject", result instanceof DBObject);
 The operation will return a data structure similar to the one displayed
 in the shell, in the form of a `DBObject` in the OUT message body.
 
-[[MongoDB-getColStats]]
-getColStats
-+++++++++++
+#### getColStats
 
 Equivalent of running the `db.collection.stats()` command in the MongoDB
 shell, which displays useful statistic figures about the collection. +
@@ -627,9 +584,7 @@ assertTrue("Result is not of type DBObject", result instanceof DBObject);
 The operation will return a data structure similar to the one displayed
 in the shell, in the form of a `DBObject` in the OUT message body.
 
-[[MongoDB-command]]
-command
-+++++++
+#### command
 
 *Available as of Camel 2.15*
 
@@ -645,9 +600,7 @@ DBObject commandBody = new BasicDBObject("hostInfo", "1");
 Object result = template.requestBody("direct:command", commandBody);
 --------------------------------------------------------------------------------
 
-[[MongoDB-Dynamicoperations]]
-Dynamic operations
-^^^^^^^^^^^^^^^^^^
+### Dynamic operations
 
 An Exchange can override the endpoint's fixed operation by setting the
 `CamelMongoDbOperation` header, defined by the
@@ -665,9 +618,7 @@ Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody",
 assertTrue("Result is not of type Long", result instanceof Long);
 -----------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-TailableCursorConsumer]]
-Tailable Cursor Consumer
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Tailable Cursor Consumer
 
 MongoDB offers a mechanism to instantaneously consume ongoing data from
 a collection, by keeping the cursor open just like the `tail -f` command
@@ -689,9 +640,7 @@ new objects are inserted, MongoDB will push them as DBObjects in natural
 order to your tailable cursor consumer, who will transform them to an
 Exchange and will trigger your route logic.
 
-[[MongoDB-Howthetailablecursorconsumerworks]]
-How the tailable cursor consumer works
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How the tailable cursor consumer works
 
 To turn a cursor into a tailable cursor, a few special flags are to be
 signalled to MongoDB when first generating the cursor. Once created, the
@@ -742,9 +691,7 @@ The above route will consume from the "flights.cancellations" capped
 collection, using "departureTime" as the increasing field, with a
 default regeneration cursor delay of 1000ms.
 
-[[MongoDB-Persistenttailtracking]]
-Persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Persistent tail tracking
 
 Standard tail tracking is volatile and the last value is only kept in
 memory. However, in practice you will need to restart your Camel
@@ -764,9 +711,7 @@ persisting at regular intervals too in the future (flush every 5
 seconds) for added robustness if the demand is there. To request this
 feature, please open a ticket in the Camel JIRA.
 
-[[MongoDB-Enablingpersistenttailtracking]]
-Enabling persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling persistent tail tracking
 
 To enable this function, set at least the following options on the
 endpoint URI:
@@ -812,9 +757,7 @@ from("mongodb:myDb?database=flights&collection=cancellations&tailTrackIncreasing
     .to("mock:test");
 -----------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-TailtrackingOnOplog]]
-Oplog Tail Tracking
-^^^^^^^^^^^^^^^^^^^
+### Oplog Tail Tracking
 
 The *oplog* collection tracking feature allows to implement trigger like functionality in MongoDB.
 In order to activate this collection you will have first to activate a replica set. For more
@@ -928,9 +871,7 @@ public class MongoDbTracker {
 -----------------------------------------------------------------------------------------------------------------------------------
 
 
-[[MongoDB-Typeconversions]]
-Type conversions
-~~~~~~~~~~~~~~~~
+### Type conversions
 
 The `MongoDbBasicConverters` type converter included with the
 camel-mongodb component provides the following conversions:
@@ -954,9 +895,7 @@ object to a `Map`, which is in turn used to initialise a new
 This type converter is auto-discovered, so you don't need to configure
 anything manually.
 
-[[MongoDB-Seealso]]
-See also
-~~~~~~~~
+### See also
 
 * http://www.mongodb.org/[MongoDB website]
 * http://en.wikipedia.org/wiki/NoSQL[NoSQL Wikipedia article]
@@ -964,5 +903,4 @@ See also
 current version]
 *
 http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc b/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
index 7d9f61a..5d069ff 100644
--- a/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
+++ b/components/camel-mongodb3/src/main/docs/mongodb3-component.adoc
@@ -1,4 +1,4 @@
-# MongoDB Component
+## MongoDB Component
 
 *Available as of Camel 2.19*
 
@@ -42,18 +42,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MongoDB-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
 
 [source,java]
 ---------------------------------------------------------------------------------------------------------------
 mongodb3:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
 ---------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-options]]
-MongoDB options
-~~~~~~~~~~~~~~~
+### MongoDB options
 
 
 // component options: START
@@ -106,9 +102,7 @@ readPreference *Remove in camel 2.19.* See Mongo client options <<MongoDB-Config
 
 
 
-[[MongoDB-ConfigurationofdatabaseinSpringXML]]
-Configuration of database in Spring XML
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Configuration of database in Spring XML
 
 The following Spring XML creates a bean defining the connection to a
 MongoDB instance.
@@ -134,9 +128,7 @@ xsi:schemaLocation="http://www.springframework.org/schema/context
 </beans>
 ----------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Sampleroute]]
-Sample route
-^^^^^^^^^^^^
+### Sample route
 
 The following route defined in Spring XML executes the operation
 link:mongodb3.html[*dbStats*] on a collection.
@@ -153,17 +145,11 @@ link:mongodb3.html[*dbStats*] on a collection.
 </route>
 ---------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-MongoDBoperations-producerendpoints]]
-MongoDB operations - producer endpoints
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### MongoDB operations - producer endpoints
 
-[[MongoDB-Queryoperations]]
-Query operations
-^^^^^^^^^^^^^^^^
+### Query operations
 
-[[MongoDB-findById]]
-findById
-++++++++
+#### findById
 
 This operation retrieves only one element from the collection whose _id
 field matches the content of the IN message body. The incoming object
@@ -183,9 +169,7 @@ from("direct:findById")
 TIP: *Supports optional parameters*. This operation supports specifying a fields filter. See
 link:mongodb3.html[Specifying optional parameters].
 
-[[MongoDB-findOneByQuery]]
-findOneByQuery
-++++++++++++++
+#### findOneByQuery
 
 Use this operation to retrieve just one element (the first) from the collection that
 matches a MongoDB query. *The query object is extracted `CamelMongoDbCriteria` header*.
@@ -216,9 +200,7 @@ from("direct:findOneByQuery")
 TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See
 link:mongodb3.html[Specifying optional parameters].
 
-[[MongoDB-findAll]]
-findAll
-+++++++
+#### findAll
 
 The `findAll` operation returns all documents matching a query, or none
 at all, in which case all documents contained in the collection are
@@ -290,9 +272,7 @@ consideration. |int/Integer
 TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See
 link:mongodb3.html[Specifying optional parameters].
 
-[[MongoDB-count]]
-count
-+++++
+#### count
 
 Returns the total number of objects in a collection, returning a Long as
 the OUT message body. +
@@ -322,9 +302,7 @@ Document query = ...
 Long count = template.requestBodyAndHeader("direct:count", query, MongoDbConstants.COLLECTION, "dynamicCollectionName");
 ------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Specifyingoptionalparameters]]
-Specifying a fields filter (projection)
-+++++++++++++++++++++++++++++++++++++++
+#### Specifying a fields filter (projection)
 
 Query operations will, by default, return the matching objects in their
 entirety (with all their fields). If your documents are large and you
@@ -356,8 +334,7 @@ Bson fieldProjection = Projection.exclude("_id", "boringField");
 Object result = template.requestBodyAndHeader("direct:findAll", ObjectUtils.NULL, MongoDbConstants.FIELDS_PROJECTION, fieldProjection);
 ----------------------------------------------------------------------------------------------------------------------------
 
-Specifying a sort clause
-++++++++++++++++++++++++
+#### Specifying a sort clause
 
 There is a often a requirement to fetch the min/max record from a
 collection based on sorting by a particular field
@@ -391,13 +368,9 @@ to a single field, based on the `documentTimestamp` field:
 ;
 ----------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Create/updateoperations]]
-Create/update operations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Create/update operations
 
-[[MongoDB-insert]]
-insert
-++++++
+#### insert
 
 Inserts an new object into the MongoDB collection, taken from the IN
 message body. Type conversion is attempted to turn it into `Document` or
@@ -444,9 +417,7 @@ have been inserted.
 In MongoDB Java Driver 3.x the insertOne and insertMany operation return void.
 The Camel insert operation return the Document or List of Documents inserted. Note that each Documents are Updated by a new OID if need.
 
-[[MongoDB-save]]
-save
-++++
+#### save
 
 The save operation is equivalent to an _upsert_ (UPdate, inSERT)
 operation, where the record will be updated, and if it doesn't exist, it
@@ -478,9 +449,7 @@ from("direct:insert")
     .to("mongodb3:myDb?database=flights&collection=tickets&operation=save");
 ---------------------------------------------------------------------------
 
-[[MongoDB-update]]
-update
-++++++
+#### update
 
 Update one or multiple records on the collection. Requires a filter query and
 a update rules.
@@ -549,13 +518,9 @@ Object result = template.requestBodyAndHeader("direct:update", updateObj, MongoD
 
 ------------------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Deleteoperations]]
-Delete operations
-^^^^^^^^^^^^^^^^^
+### Delete operations
 
-[[MongoDB-remove]]
-remove
-++++++
+#### remove
 
 Remove matching records from the collection. The IN message body will
 act as the removal filter query, and is expected to be of type
@@ -576,13 +541,9 @@ A header with key `CamelMongoDbRecordsAffected` is returned
 containing the number of records deleted (copied from
 `WriteResult.getN()`).
 
-[[MongoDB-Otheroperations]]
-Other operations
-^^^^^^^^^^^^^^^^
+### Other operations
 
-[[MongoDB-aggregate]]
-aggregate
-+++++++++
+#### aggregate
 
 Perform a aggregation with the given pipeline contained in the
 body. *Aggregations could be long and heavy operations. Use with care.*
@@ -600,9 +561,7 @@ from("direct:aggregate")
     .to("mock:resultAggregate");
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-getDbStats]]
-getDbStats
-++++++++++
+#### getDbStats
 
 Equivalent of running the `db.stats()` command in the MongoDB shell,
 which displays useful statistic figures about the database. +
@@ -639,9 +598,7 @@ assertTrue("Result is not of type Document", result instanceof Document);
 The operation will return a data structure similar to the one displayed
 in the shell, in the form of a `Document` in the OUT message body.
 
-[[MongoDB-getColStats]]
-getColStats
-+++++++++++
+#### getColStats
 
 Equivalent of running the `db.collection.stats()` command in the MongoDB
 shell, which displays useful statistic figures about the collection. +
@@ -681,9 +638,7 @@ assertTrue("Result is not of type Document", result instanceof Document);
 The operation will return a data structure similar to the one displayed
 in the shell, in the form of a `Document` in the OUT message body.
 
-[[MongoDB-command]]
-command
-+++++++
+#### command
 
 Run the body as a command on database. Usefull for admin operation as
 getting host informations, replication or sharding status.
@@ -697,9 +652,7 @@ DBObject commandBody = new BasicDBObject("hostInfo", "1");
 Object result = template.requestBody("direct:command", commandBody);
 --------------------------------------------------------------------------------
 
-[[MongoDB-Dynamicoperations]]
-Dynamic operations
-^^^^^^^^^^^^^^^^^^
+### Dynamic operations
 
 An Exchange can override the endpoint's fixed operation by setting the
 `CamelMongoDbOperation` header, defined by the
@@ -717,9 +670,7 @@ Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody",
 assertTrue("Result is not of type Long", result instanceof Long);
 -----------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-TailableCursorConsumer]]
-Tailable Cursor Consumer
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Tailable Cursor Consumer
 
 MongoDB offers a mechanism to instantaneously consume ongoing data from
 a collection, by keeping the cursor open just like the `tail -f` command
@@ -741,9 +692,7 @@ new objects are inserted, MongoDB will push them as `Document` in natural
 order to your tailable cursor consumer, who will transform them to an
 Exchange and will trigger your route logic.
 
-[[MongoDB-Howthetailablecursorconsumerworks]]
-How the tailable cursor consumer works
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How the tailable cursor consumer works
 
 To turn a cursor into a tailable cursor, a few special flags are to be
 signalled to MongoDB when first generating the cursor. Once created, the
@@ -794,9 +743,7 @@ The above route will consume from the "flights.cancellations" capped
 collection, using "departureTime" as the increasing field, with a
 default regeneration cursor delay of 1000ms.
 
-[[MongoDB-Persistenttailtracking]]
-Persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Persistent tail tracking
 
 Standard tail tracking is volatile and the last value is only kept in
 memory. However, in practice you will need to restart your Camel
@@ -816,9 +763,7 @@ persisting at regular intervals too in the future (flush every 5
 seconds) for added robustness if the demand is there. To request this
 feature, please open a ticket in the Camel JIRA.
 
-[[MongoDB-Enablingpersistenttailtracking]]
-Enabling persistent tail tracking
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling persistent tail tracking
 
 To enable this function, set at least the following options on the
 endpoint URI:
@@ -864,9 +809,7 @@ from("mongodb3:myDb?database=flights&collection=cancellations&tailTrackIncreasin
     .to("mock:test");
 -----------------------------------------------------------------------------------------------------------------------------------
 
-[[MongoDB-Typeconversions]]
-Type conversions
-~~~~~~~~~~~~~~~~
+### Type conversions
 
 The `MongoDbBasicConverters` type converter included with the
 camel-mongodb component provides the following conversions:
@@ -887,9 +830,7 @@ object to a `Map`, which is in turn used to initialise a new
 This type converter is auto-discovered, so you don't need to configure
 anything manually.
 
-[[MongoDB-Seealso]]
-See also
-~~~~~~~~
+### See also
 
 * http://www.mongodb.org/[MongoDB website]
 * http://en.wikipedia.org/wiki/NoSQL[NoSQL Wikipedia article]
@@ -897,5 +838,4 @@ See also
 current version]
 *
 http://svn.apache.org/viewvc/camel/trunk/components/camel-mongodb/src/test/[Unit
-tests] for more examples of usage
-
+tests] for more examples of usage
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mqtt/src/main/docs/mqtt-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mqtt/src/main/docs/mqtt-component.adoc b/components/camel-mqtt/src/main/docs/mqtt-component.adoc
index c950628..f813c9d 100644
--- a/components/camel-mqtt/src/main/docs/mqtt-component.adoc
+++ b/components/camel-mqtt/src/main/docs/mqtt-component.adoc
@@ -1,4 +1,4 @@
-# MQTT Component
+## MQTT Component
 
 *Available as of Camel 2.10*
 
@@ -20,9 +20,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MQTT-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------
@@ -31,9 +29,7 @@ mqtt://name[?options]
 
 Where *name* is the name you want to assign the component.
 
-[[MQTT-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -112,9 +108,7 @@ The MQTT component supports 40 endpoint options which are listed below:
 
 
 
-[[MQTT-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 Sending messages:
 
@@ -130,9 +124,7 @@ Consuming messages:
 from("mqtt:bar?subscribeTopicName=test.mqtt.topic").transform(body().convertToString()).to("mock:result")
 ---------------------------------------------------------------------------------------------------------
 
-[[MQTT-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
 
 Camel supports the link:message-endpoint.html[Message Endpoint] pattern
 using the
@@ -158,12 +150,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
 consuming message exchanges from the endpoint via a
 http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
 
-[[MQTT-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:message-endpoint.html[Message Endpoint] pattern
 * link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-msv/src/main/docs/msv-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-msv/src/main/docs/msv-component.adoc b/components/camel-msv/src/main/docs/msv-component.adoc
index 07e354b..6c843c2 100644
--- a/components/camel-msv/src/main/docs/msv-component.adoc
+++ b/components/camel-msv/src/main/docs/msv-component.adoc
@@ -1,4 +1,4 @@
-# MSV Component
+## MSV Component
 
 The MSV component performs XML validation of the message body using the
 https://msv.dev.java.net/[MSV Library] and any of the supported XML
@@ -22,9 +22,7 @@ Note that the link:jing.html[Jing] component also supports
 http://relaxng.org/compact-tutorial-20030326.html[RelaxNG Compact
 Syntax]
 
-[[MSV-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------
@@ -45,9 +43,7 @@ msv:http://acme.com/cheese.rng
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[MSV-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -97,9 +93,7 @@ The MSV component supports 12 endpoint options which are listed below:
 
 
 
-[[MSV-Example]]
-Example
-^^^^^^^
+### Example
 
 The following
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-msv/src/test/resources/org/apache/camel/component/validator/msv/camelContext.xml[example]
@@ -109,12 +103,9 @@ based on whether or not the XML matches the given
 http://relaxng.org/[RelaxNG XML Schema] (which is supplied on the
 classpath).
 
-[[MSV-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mustache/src/main/docs/mustache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mustache/src/main/docs/mustache-component.adoc b/components/camel-mustache/src/main/docs/mustache-component.adoc
index 5b5e778..a6ad9ce 100644
--- a/components/camel-mustache/src/main/docs/mustache-component.adoc
+++ b/components/camel-mustache/src/main/docs/mustache-component.adoc
@@ -1,4 +1,4 @@
-# Mustache Component
+## Mustache Component
 
 *Available as of Camel 2.12*
 
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ---------------------------------------------------------------------------------
 
-[[Mustache-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
@@ -35,9 +33,7 @@ file://folder/myfile.mustache[file://folder/myfile.mustache]).
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Mustache-Options]]
-Options
-^^^^^^^
+### Options
 
 
 {% raw %}
@@ -84,9 +80,7 @@ The Mustache component supports 6 endpoint options which are listed below:
 {% endraw %}
 
 
-[[Mustache-MustacheContext]]
-Mustache Context
-^^^^^^^^^^^^^^^^
+### Mustache Context
 
 Camel will provide exchange information in the Mustache context (just a
 `Map`). The `Exchange` is transferred as:
@@ -110,9 +104,7 @@ Camel will provide exchange information in the Mustache context (just a
 |`response` |The Out message (only for InOut message exchange pattern).
 |=======================================================================
 
-[[Mustache-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
 
 Camel provides two headers by which you can define a different resource
 location for a template or the template content itself. If any of these
@@ -129,9 +121,7 @@ configured. |
 |MustacheConstants.MUSTACHE_TEMPLATE |String |The template to use instead of the endpoint configured. |
 |=======================================================================
 
-[[Mustache-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use something like:
 
@@ -164,9 +154,7 @@ setHeader(MustacheConstants.MUSTACHE_RESOURCE_URI).constant("path/to/my/template
 to("mustache:dummy");
 --------------------------------------------------------------------------------------------
 
-[[Mustache-TheEmailSample]]
-The Email Sample
-^^^^^^^^^^^^^^^^
+### The Email Sample
 
 In this sample we want to use Mustache templating for an order
 confirmation email. The email template is laid out in Mustache as:
@@ -181,12 +169,9 @@ Regards Camel Riders Bookstore
 {{body}}
 -------------------------------------------------
 
-[[Mustache-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mvel/src/main/docs/mvel-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mvel/src/main/docs/mvel-component.adoc b/components/camel-mvel/src/main/docs/mvel-component.adoc
index bdd5e38..2207c65 100644
--- a/components/camel-mvel/src/main/docs/mvel-component.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-component.adoc
@@ -1,4 +1,4 @@
-# MVEL Component
+## MVEL Component
 
 *Available as of Camel 2.12*
 
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MVELComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------
@@ -35,9 +33,7 @@ file://folder/myfile.mvel[file://folder/myfile.mvel]).
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[MVELComponent-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -64,9 +60,7 @@ The MVEL component supports 4 endpoint options which are listed below:
 
 
 
-[[MVELComponent-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The mvel component sets a couple headers on the message.
 
@@ -77,9 +71,7 @@ The mvel component sets a couple headers on the message.
 |`CamelMvelResourceUri` |The *templateName* as a `String` object.
 |=======================================================================
 
-[[MVELComponent-MVELContext]]
-MVEL Context
-^^^^^^^^^^^^
+### MVEL Context
 
 Camel will provide exchange information in the MVEL context (just a
 `Map`). The `Exchange` is transfered as:
@@ -107,9 +99,7 @@ Camel will provide exchange information in the MVEL context (just a
 |`response` |The Out message (only for InOut message exchange pattern).
 |=======================================================================
 
-[[MVELComponent-Hotreloading]]
-Hot reloading
-^^^^^^^^^^^^^
+### Hot reloading
 
 The mvel template resource is, by default, hot reloadable for both file
 and classpath resources (expanded jar). If you set `contentCache=true`,
@@ -117,9 +107,7 @@ Camel will only load the resource once, and thus hot reloading is not
 possible. This scenario can be used in production, when the resource
 never changes.
 
-[[MVELComponent-Dynamictemplates]]
-Dynamic templates
-^^^^^^^^^^^^^^^^^
+### Dynamic templates
 
 Camel provides two headers by which you can define a different resource
 location for a template or the template content itself. If any of these
@@ -136,9 +124,7 @@ configured.
 |CamelMvelTemplate |String |The template to use instead of the endpoint configured.
 |=======================================================================
 
-[[MVELComponent-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use something like
 
@@ -171,12 +157,9 @@ from("direct:in").
   to("velocity:dummy");
 ------------------------------------------------------------------------------------------
 
-[[MVELComponent-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mvel/src/main/docs/mvel-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc b/components/camel-mvel/src/main/docs/mvel-language.adoc
index 15d4549..a38222e 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -1,4 +1,4 @@
-# MVEL Language
+## MVEL Language
 
 Camel allows Mvel to be used as an link:expression.html[Expression] or
 link:predicate.html[Predicate] the link:dsl.html[DSL] or
@@ -20,9 +20,7 @@ you can construct the syntax as follows:
 "getRequest().getBody().getFamilyName()"
 ----------------------------------------
 
-[[Mvel-Options]]
-Mvel Options
-^^^^^^^^^^^^
+### Mvel Options
 
 // language options: START
 The MVEL language supports 1 options which are listed below.
@@ -38,9 +36,7 @@ The MVEL language supports 1 options which are listed below.
 {% endraw %}
 // language options: END
 
-[[Mvel-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -67,9 +63,7 @@ Variables
 |property(name, type) |Type |the property by the given name as the given type
 |=======================================================================
 
-[[Mvel-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use Mvel inside a link:message-filter.html[Message
 Filter] in XML
@@ -92,9 +86,7 @@ And the sample using Java DSL:
    from("seda:foo").filter().mvel("request.headers.foo == 'bar'").to("seda:bar");
 ---------------------------------------------------------------------------------
 
-[[Mvel-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -108,9 +100,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").mvel("resource:classpath:script.mvel")
 -------------------------------------------------------------
 
-[[Mvel-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Mvel in your camel routes you need to add the a dependency on
 *camel-mvel* which implements the Mvel language.
@@ -126,4 +116,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-mvel</artifactId>
   <version>x.x.x</version>
 </dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-mybatis/src/main/docs/mybatis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-mybatis/src/main/docs/mybatis-component.adoc b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
index a22f25a..92e3567 100644
--- a/components/camel-mybatis/src/main/docs/mybatis-component.adoc
+++ b/components/camel-mybatis/src/main/docs/mybatis-component.adoc
@@ -1,4 +1,4 @@
-# MyBatis Component
+## MyBatis Component
 
 *Available as of Camel 2.7*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[MyBatis-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
@@ -40,9 +38,7 @@ the root of the classpath with the expected name of
  If the file is located in another location, you will need to configure
 the `configurationUri` option on the `MyBatisComponent` component.
 
-[[MyBatis-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -110,9 +106,7 @@ The MyBatis component supports 30 endpoint options which are listed below:
 
 
 
-[[MyBatis-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel will populate the result message, either IN or OUT with a header
 with the statement used:
@@ -128,9 +122,7 @@ instance an `INSERT` could return the auto-generated key, or number of
 rows etc.
 |=======================================================================
 
-[[MyBatis-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 The response from MyBatis will only be set as the body if it's a
 `SELECT` statement. That means, for example, for `INSERT` statements
@@ -138,9 +130,7 @@ Camel will not replace the body. This allows you to continue routing and
 keep the original body. The response from MyBatis is always stored in
 the header with the key `CamelMyBatisResult`.
 
-[[MyBatis-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example if you wish to consume beans from a JMS queue and insert
 them into a database you could do the following:
@@ -172,9 +162,7 @@ Where *insertAccount* is the MyBatis ID in the SQL mapping file:
   </insert>
 ------------------------------------------------------------
 
-[[MyBatis-UsingStatementTypeforbettercontrolofMyBatis]]
-Using StatementType for better control of MyBatis
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using StatementType for better control of MyBatis
 
 When routing to an MyBatis endpoint you will want more fine grained
 control so you can control whether the SQL statement to be executed is a
@@ -192,9 +180,7 @@ We can do the same for some of the other operations, such as
 And the same for `UPDATE`, where we can send an `Account` object as the
 IN body to MyBatis:
 
-[[MyBatis-UsingInsertListStatementType]]
-Using InsertList StatementType
-++++++++++++++++++++++++++++++
+#### Using InsertList StatementType
 
 *Available as of Camel 2.10*
 
@@ -206,9 +192,7 @@ Then you can insert multiple rows, by sending a Camel message to the
 `mybatis` endpoint which uses the `InsertList` statement type, as shown
 below:
 
-[[MyBatis-UsingUpdateListStatementType]]
-Using UpdateList StatementType
-++++++++++++++++++++++++++++++
+#### Using UpdateList StatementType
 
 *Available as of Camel 2.11*
 
@@ -240,9 +224,7 @@ from("direct:start")
     .to("mock:result");
 --------------------------------------------------------------
 
-[[MyBatis-UsingDeleteListStatementType]]
-Using DeleteList StatementType
-++++++++++++++++++++++++++++++
+#### Using DeleteList StatementType
 
 *Available as of Camel 2.11*
 
@@ -273,18 +255,14 @@ from("direct:start")
     .to("mock:result");
 --------------------------------------------------------------
 
-[[MyBatis-NoticeonInsertList,UpdateListandDeleteListStatementTypes]]
-Notice on InsertList, UpdateList and DeleteList StatementTypes
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Notice on InsertList, UpdateList and DeleteList StatementTypes
 
 Parameter of any type (List, Map, etc.) can be passed to mybatis and an
 end user is responsible for handling it as required +
  with the help of http://www.mybatis.org/core/dynamic-sql.html[mybatis
 dynamic queries] capabilities.
 
-[[MyBatis-Scheduledpollingexample]]
-Scheduled polling example
-+++++++++++++++++++++++++
+#### Scheduled polling example
 
 This component supports scheduled polling and can therefore be used as
 a link:polling-consumer.html[Polling Consumer]. For example to poll the
@@ -319,9 +297,7 @@ And the MyBatis SQL mapping file used:
   </select>
 ----------------------------------------------------------------------------
 
-[[MyBatis-UsingonConsume]]
-Using onConsume
-+++++++++++++++
+#### Using onConsume
 
 This component supports executing statements *after* data have been
 consumed and processed by Camel. This allows you to do post updates in
@@ -335,9 +311,7 @@ database to processed, so we avoid consuming it twice or more.
 
 And the statements in the sqlmap file:
 
-[[MyBatis-Participatingintransactions]]
-Participating in transactions
-+++++++++++++++++++++++++++++
+#### Participating in transactions
 
 Setting up a transaction manager under camel-mybatis can be a little bit
 fiddly, as it involves externalising the database configuration outside
@@ -420,12 +394,9 @@ usual:
     </camelContext>
 ------------------------------------------------------------------------------------------------
 
-[[MyBatis-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-nagios/src/main/docs/nagios-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-nagios/src/main/docs/nagios-component.adoc b/components/camel-nagios/src/main/docs/nagios-component.adoc
index 36677bb..e608975 100644
--- a/components/camel-nagios/src/main/docs/nagios-component.adoc
+++ b/components/camel-nagios/src/main/docs/nagios-component.adoc
@@ -1,4 +1,4 @@
-# Nagios Component
+## Nagios Component
 
 *Available as of Camel 2.3*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Nagios-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------
@@ -33,9 +31,7 @@ its endpoint. +
  Camel also provides a link:camel-jmx.html[EventNotifer] which allows
 you to send notifications to Nagios.
 
-[[Nagios-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -82,9 +78,7 @@ The Nagios component supports 8 endpoint options which are listed below:
 
 
 
-[[Nagios-Sendingmessageexamples]]
-Sending message examples
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending message examples
 
 You can send a message to Nagios where the message payload contains the
 message. By default it will be `OK` level and use the
@@ -111,9 +105,7 @@ To send a `CRITICAL` message you can send the headers such as:
         template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
 -----------------------------------------------------------------------------
 
-[[Nagios-UsingNagiosEventNotifer]]
-Using `NagiosEventNotifer`
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using `NagiosEventNotifer`
 
 The link:nagios.html[Nagios] component also provides an
 link:camel-jmx.html[EventNotifer] which you can use to send events to
@@ -136,12 +128,9 @@ In Spring XML its just a matter of defining a Spring bean with the type
 link:advanced-configuration-of-camelcontext-using-spring.html[Advanced
 configuration of CamelContext using Spring].
 
-[[Nagios-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-nats/src/main/docs/nats-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-nats/src/main/docs/nats-component.adoc b/components/camel-nats/src/main/docs/nats-component.adoc
index a1b45b8..d92076e 100644
--- a/components/camel-nats/src/main/docs/nats-component.adoc
+++ b/components/camel-nats/src/main/docs/nats-component.adoc
@@ -1,4 +1,4 @@
-# Nats Component
+## Nats Component
 
 *Available since Camel 2.17.0*
 
@@ -17,9 +17,7 @@ their `pom.xml` for this component.
 </dependency>
 ------------------------------------------------------------
 
-[[NATS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------
@@ -28,9 +26,7 @@ nats:servers[?options]
 
 Where *servers* represents the list of NATS servers.
 
-[[NATS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -78,9 +74,7 @@ The Nats component supports 23 endpoint options which are listed below:
 
 
 
-[[NATS-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -105,4 +99,4 @@ from("direct:send").to("nats://localhost:4222?topic=test");
 [source,java]
 ----------------------------------------------------------------------------------------
 from("nats://localhost:4222?topic=test&maxMessages=5&queueName=test").to("mock:result");
-----------------------------------------------------------------------------------------
+----------------------------------------------------------------------------------------
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[07/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jms/src/main/docs/jms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index c0bd57c..1596260 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -1,4 +1,4 @@
-# JMS Component
+## JMS Component
 ifdef::env-github[]
 :icon-smile: :smiley:
 :caution-caption: :boom:
@@ -14,9 +14,7 @@ ifndef::env-github[]
 endif::[]
 
 
-[[JMS-JMSComponent]]
-JMS Component
-~~~~~~~~~~~~~
+### JMS Component
 
 [TIP]
 ====
@@ -66,9 +64,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[JMS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 --------------------------------------------
 jms:[queue:|topic:]destinationName[?options]
@@ -99,13 +95,9 @@ jms:topic:Stocks.Prices
 You append query options to the URI using the following format,
 `?option=value&option=value&...`
 
-[[JMS-Notes]]
-Notes
-^^^^^
+### Notes
 
-[[JMS-UsingActiveMQ]]
-Using ActiveMQ
-++++++++++++++
+#### Using ActiveMQ
 
 The JMS component reuses Spring 2's `JmsTemplate` for sending messages.
 This is not ideal for use in a non-J2EE container and typically requires
@@ -120,9 +112,7 @@ then we recommend that you either:
 optimized to use ActiveMQ efficiently
 * Use the `PoolingConnectionFactory` in ActiveMQ.
 
-[[JMS-TransactionsandCacheLevels]]
-Transactions and Cache Levels
-+++++++++++++++++++++++++++++
+#### Transactions and Cache Levels
 
 If you are consuming messages and using transactions
 (`transacted=true`) then the default settings for cache level can impact
@@ -148,9 +138,7 @@ level accordingly to:
 So you can say the default setting is conservative. Consider using
 `cacheLevelName=CACHE_CONSUMER` if you are using non-XA transactions.
 
-[[JMS-DurableSubscriptions]]
-Durable Subscriptions
-+++++++++++++++++++++
+#### Durable Subscriptions
 
 If you wish to use durable topic subscriptions, you need to specify both
 `clientId` and `durableSubscriptionName`. The value of the `clientId`
@@ -160,9 +148,7 @@ http://activemq.apache.org/virtual-destinations.html[Virtual Topics]
 instead to avoid this limitation. More background on durable messaging
 http://activemq.apache.org/how-do-durable-queues-and-topics-work.html[here].
 
-[[JMS-MessageHeaderMapping]]
-Message Header Mapping
-++++++++++++++++++++++
+#### Message Header Mapping
 
 When using message headers, the JMS specification states that header
 names must be valid Java identifiers. So try to name your headers to be
@@ -185,9 +171,7 @@ Camel consume the message
 * Hyphen is replaced by `_HYPHEN_` and the replacement is reversed when
 Camel consumes the message
 
-[[JMS-Options]]
-Options
-^^^^^^^
+### Options
 
 You can configure many different properties on the JMS endpoint which
 map to properties on the
@@ -203,9 +187,7 @@ uses for sending and receiving messages. So you can get more information
 about these properties by consulting the relevant Spring documentation.
 ====
 
-[[JMS-Componentoptions]]
-Component options
-+++++++++++++++++
+#### Component options
 
 
 
@@ -308,9 +290,7 @@ The JMS component supports 74 options which are listed below.
 
 
 
-[[JMS-Endpointoptions]]
-Endpoint options
-++++++++++++++++
+#### Endpoint options
 
 
 
@@ -425,9 +405,7 @@ The JMS component supports 86 endpoint options which are listed below:
 
 
 
-[[JMS-MessageMappingbetweenJMSandCamel]]
-Message Mapping between JMS and Camel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message Mapping between JMS and Camel
 
 Camel automatically maps messages between `javax.jms.Message` and
 `org.apache.camel.Message`.
@@ -470,9 +448,7 @@ following body type:
 |`javax.jms.ObjectMessage` |`Object`
 |=============================================
 
-[[JMS-Disablingauto-mappingofJMSmessages]]
-Disabling auto-mapping of JMS messages
-++++++++++++++++++++++++++++++++++++++
+#### Disabling auto-mapping of JMS messages
 
 You can use the `mapJmsMessage` option to disable the auto-mapping
 above. If disabled, Camel will not try to map the received JMS message,
@@ -481,9 +457,7 @@ the overhead of mapping and let Camel just pass through the JMS message.
 For instance, it even allows you to route `javax.jms.ObjectMessage` JMS
 messages with classes you do *not* have on the classpath.
 
-[[JMS-UsingacustomMessageConverter]]
-Using a custom MessageConverter
-+++++++++++++++++++++++++++++++
+#### Using a custom MessageConverter
 
 You can use the `messageConverter` option to do the mapping yourself in
 a Spring `org.springframework.jms.support.converter.MessageConverter`
@@ -500,9 +474,7 @@ from("file://inbox/order").to("jms:queue:order?messageConverter=#myMessageConver
 You can also use a custom message converter when consuming from a JMS
 destination.
 
-[[JMS-Controllingthemappingstrategyselected]]
-Controlling the mapping strategy selected
-+++++++++++++++++++++++++++++++++++++++++
+#### Controlling the mapping strategy selected
 
 You can use the `jmsMessageType` option on the endpoint URL to force a
 specific message type for all messages.
@@ -527,9 +499,7 @@ from("file://inbox/order").setHeader("CamelJmsMessageType", JmsMessageType.Text)
 The possible values are defined in the `enum` class,
 `org.apache.camel.jms.JmsMessageType`.
 
-[[JMS-Messageformatwhensending]]
-Message format when sending
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message format when sending
 
 The exchange that is sent over the JMS wire must conform to the
 http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html[JMS Message
@@ -566,9 +536,7 @@ at *DEBUG* level if it drops a given header value. For example:
   - Ignoring non primitive header: order of class: org.apache.camel.component.jms.issues.DummyOrder with value: DummyOrder{orderId=333, itemId=4444, quantity=2}
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[JMS-Messageformatwhenreceiving]]
-Message format when receiving
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Message format when receiving
 
 Camel adds the following properties to the `Exchange` when it receives a
 message:
@@ -614,9 +582,7 @@ As all the above information is standard JMS you can check the
 http://java.sun.com/javaee/5/docs/api/javax/jms/Message.html[JMS
 documentation] for further details.
 
-[[JMS-AboutusingCameltosendandreceivemessagesandJMSReplyTo]]
-About using Camel to send and receive messages and JMSReplyTo
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### About using Camel to send and receive messages and JMSReplyTo
 
 The JMS component is complex and you have to pay close attention to how
 it works in some cases. So this is a short summary of some of the
@@ -634,9 +600,7 @@ endpoint: `disableReplyTo`, `preserveMessageQos`, `explicitQosEnabled`.
 All this can be a tad complex to understand and configure to support
 your use case.
 
-[[JMS-JmsProducer]]
-JmsProducer
-+++++++++++
+#### JmsProducer
 
 The `JmsProducer` behaves as follows, depending on configuration:
 
@@ -663,9 +627,7 @@ instruct Camel to keep the `JMSReplyTo`. In all situations the
 sending the message.
 |=======================================================================
 
-[[JMS-JmsConsumer]]
-JmsConsumer
-+++++++++++
+#### JmsConsumer
 
 The `JmsConsumer` behaves as follows, depending on configuration:
 
@@ -695,9 +657,7 @@ from("activemq:queue:in")
    .to("bean:handleOrder");
 ------------------------------------------------------
 
-[[JMS-Reuseendpointandsendtodifferentdestinationscomputedatruntime]]
-Reuse endpoint and send to different destinations computed at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Reuse endpoint and send to different destinations computed at runtime
 
 If you need to send messages to a lot of different JMS destinations, it
 makes sense to reuse a JMS endpoint and specify the real destination in
@@ -751,9 +711,7 @@ them to the created JMS message in order to avoid the accidental loops
 in the routes (in scenarios when the message will be forwarded to the
 another JMS endpoint).
 
-[[JMS-ConfiguringdifferentJMSproviders]]
-Configuring different JMS providers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring different JMS providers
 
 You can configure your JMS provider in link:spring.html[Spring] XML as
 follows:
@@ -774,9 +732,7 @@ spring context for the scheme name you use for
 link:endpoint.html[Endpoint] link:uris.html[URIs] and having the
 link:component.html[Component] resolve the endpoint URIs.
 
-[[JMS-UsingJNDItofindtheConnectionFactory]]
-Using JNDI to find the ConnectionFactory
-++++++++++++++++++++++++++++++++++++++++
+#### Using JNDI to find the ConnectionFactory
 
 If you are using a J2EE container, you might need to look up JNDI to
 find the JMS `ConnectionFactory` rather than use the usual `<bean>`
@@ -797,9 +753,7 @@ http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html
 jee schema] in the Spring reference documentation for more details about
 JNDI lookup.
 
-[[JMS-ConcurrentConsuming]]
-Concurrent Consuming
-^^^^^^^^^^^^^^^^^^^^
+### Concurrent Consuming
 
 A common requirement with JMS is to consume messages concurrently in
 multiple threads in order to make an application more responsive. You
@@ -818,9 +772,7 @@ You can configure this option in one of the following ways:
 * On the endpoint URI or,
 * By invoking `setConcurrentConsumers()` directly on the `JmsEndpoint`.
 
-[[JMS-ConcurrentConsumingwithasyncconsumer]]
-Concurrent Consuming with async consumer
-++++++++++++++++++++++++++++++++++++++++
+#### Concurrent Consuming with async consumer
 
 Notice that each concurrent consumer will only pickup the next available
 message from the JMS broker, when the current message has been fully
@@ -837,9 +789,7 @@ from("jms:SomeQueue?concurrentConsumers=20&asyncConsumer=true").
   bean(MyClass.class);
 ----------------------------------------------------------------
 
-[[JMS-Request-replyoverJMS]]
-Request-reply over JMS
-^^^^^^^^^^^^^^^^^^^^^^
+### Request-reply over JMS
 
 Camel supports link:request-reply.html[Request Reply] over JMS. In
 essence the MEP of the Exchange should be `InOut` when you send a
@@ -945,9 +895,7 @@ from(xxx)
 .to(zzz);
 -------------------------------------------------------
 
-[[JMS-Request-replyoverJMSandusingasharedfixedreplyqueue]]
-Request-reply over JMS and using a shared fixed reply queue
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Request-reply over JMS and using a shared fixed reply queue
 
 If you use a fixed reply queue when doing
 link:request-reply.html[Request Reply] over JMS as shown in the example
@@ -981,9 +929,7 @@ Notice this will cause the Camel to send pull requests to the message
 broker more frequent, and thus require more network traffic. +
  It is generally recommended to use temporary queues if possible.
 
-[[JMS-Request-replyoverJMSandusinganexclusivefixedreplyqueue]]
-Request-reply over JMS and using an exclusive fixed reply queue
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Request-reply over JMS and using an exclusive fixed reply queue
 
 *Available as of Camel 2.9*
 
@@ -1030,9 +976,7 @@ node in the cluster may pickup messages which was intended as a reply on
 another node. For clustered environments its recommended to use shared
 reply queues instead.
 
-[[JMS-Synchronizingclocksbetweensendersandreceivers]]
-Synchronizing clocks between senders and receivers
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Synchronizing clocks between senders and receivers
 
 When doing messaging between systems, its desirable that the systems
 have synchronized clocks. For example when sending a link:jms.html[JMS]
@@ -1044,9 +988,7 @@ clocks. If you are using http://activemq.apache.org/[ActiveMQ] then you
 can use the http://activemq.apache.org/timestampplugin.html[timestamp
 plugin] to synchronize clocks.
 
-[[JMS-Abouttimetolive]]
-About time to live
-^^^^^^^^^^^^^^^^^^
+### About time to live
 
 Read first above about synchronized clocks.
 
@@ -1112,9 +1054,7 @@ example to indicate a 5 sec., you set `timeToLive=5000`. The option
 also for InOnly messaging. The `requestTimeout` option is not being used
 for InOnly messaging.
 
-[[JMS-EnablingTransactedConsumption]]
-Enabling Transacted Consumption
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling Transacted Consumption
 
 A common requirement is to consume from a queue in a transaction and
 then process the message using the Camel route. To do this, just ensure
@@ -1169,9 +1109,7 @@ http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html[her
 and
 http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching%20connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530[here].
 
-[[JMS-UsingJMSReplyToforlatereplies]]
-Using JMSReplyTo for late replies
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using JMSReplyTo for late replies
 
 When using Camel as a JMS listener, it sets an Exchange property with
 the value of the ReplyTo `javax.jms.Destination` object, having the key
@@ -1210,25 +1148,19 @@ For example:
     }
 ----------------------------------------------------------------------------------------------------------------------------------------
 
-[[JMS-Usingarequesttimeout]]
-Using a request timeout
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using a request timeout
 
 In the sample below we send a link:request-reply.html[Request Reply]
 style message link:exchange.html[Exchange] (we use the `requestBody`
 method = `InOut`) to the slow queue for further processing in Camel and
 we wait for a return reply:
 
-[[JMS-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 JMS is used in many examples for other components as well. But we
 provide a few samples below to get started.
 
-[[JMS-ReceivingfromJMS]]
-Receiving from JMS
-++++++++++++++++++
+#### Receiving from JMS
 
 In the following sample we configure a route that receives JMS messages
 and routes the message to a POJO:
@@ -1250,9 +1182,7 @@ from("jms:topic:OrdersTopic").
     to("jms:queue:BigSpendersQueue");
 ----------------------------------------------
 
-[[JMS-SendingtoJMS]]
-Sending to JMS
-++++++++++++++
+#### Sending to JMS
 
 In the sample below we poll a file folder and send the file content to a
 JMS topic. As we want the content of the file as a `TextMessage` instead
@@ -1265,16 +1195,12 @@ from("file://orders").
   to("jms:topic:OrdersTopic");
 ------------------------------
 
-[[JMS-UsingAnnotations]]
-Using link:bean-integration.html[Annotations]
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Using link:bean-integration.html[Annotations]
 
 Camel also has annotations so you can use link:pojo-consuming.html[POJO
 Consuming] and link:pojo-producing.html[POJO Producing].
 
-[[JMS-SpringDSLsample]]
-Spring DSL sample
-+++++++++++++++++
+#### Spring DSL sample
 
 The preceding examples use the Java DSL. Camel also supports Spring XML
 DSL. Here is the big spender sample using Spring DSL:
@@ -1290,9 +1216,7 @@ DSL. Here is the big spender sample using Spring DSL:
 </route>
 ---------------------------------------------------
 
-[[JMS-Othersamples]]
-Other samples
-+++++++++++++
+#### Other samples
 
 JMS appears in many of the examples for other components and EIP
 patterns, as well in this Camel documentation. So feel free to browse
@@ -1300,9 +1224,7 @@ the documentation. If you have time, check out the this tutorial that
 uses JMS but focuses on how well Spring Remoting and Camel works
 together link:tutorial-jmsremoting.html[Tutorial-JmsRemoting].
 
-[[JMS-UsingJMSasaDeadLetterQueuestoringExchange]]
-Using JMS as a Dead Letter Queue storing Exchange
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JMS as a Dead Letter Queue storing Exchange
 
 Normally, when using link:jms.html[JMS] as the transport, it only
 transfers the body and headers as the payload. If you want to use
@@ -1336,9 +1258,7 @@ Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Exception.clas
 String problem = cause.getMessage();
 -----------------------------------------------------------------------------------
 
-[[JMS-UsingJMSasaDeadLetterChannelstoringerroronly]]
-Using JMS as a Dead Letter Channel storing error only
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JMS as a Dead Letter Channel storing error only
 
 You can use JMS to store the cause error message or to store a custom
 body, which you can initialize yourself. The following example uses the
@@ -1360,9 +1280,7 @@ You can, however, use any link:expression.html[Expression] to send
 whatever you like. For example, you can invoke a method on a Bean or use
 a custom processor.
 
-[[JMS-SendinganInOnlymessageandkeepingtheJMSReplyToheader]]
-Sending an InOnly message and keeping the JMSReplyTo header
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending an InOnly message and keeping the JMSReplyTo header
 
 When sending to a link:jms.html[JMS] destination using *camel-jms* the
 producer will use the MEP to detect if its _InOnly_ or _InOut_ messaging.
@@ -1386,9 +1304,7 @@ For example to send an _InOnly_ message to the foo queue, but with a
 Notice we use `preserveMessageQos=true` to instruct Camel to keep the
 `JMSReplyTo` header.
 
-[[JMS-SettingJMSprovideroptionsonthedestination]]
-Setting JMS provider options on the destination
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting JMS provider options on the destination
 
 Some JMS providers, like IBM's WebSphere MQ need options to be set on
 the JMS destination. For example, you may need to specify the
@@ -1427,9 +1343,7 @@ wmq.setDestinationResolver(new DestinationResolver() {
 });
 ----------------------------------------------------------------------------------------------------------------------------------
 
-[[JMS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
@@ -1440,4 +1354,4 @@ See Also
 * link:bean-integration.html[Bean Integration]
 * link:tutorial-jmsremoting.html[Tutorial-JmsRemoting]
 * http://activemq.apache.org/jmstemplate-gotchas.html[JMSTemplate
-gotchas]
+gotchas]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jmx/src/main/docs/jmx-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jmx/src/main/docs/jmx-component.adoc b/components/camel-jmx/src/main/docs/jmx-component.adoc
index 6d1aa8c..df88101 100644
--- a/components/camel-jmx/src/main/docs/jmx-component.adoc
+++ b/components/camel-jmx/src/main/docs/jmx-component.adoc
@@ -1,4 +1,4 @@
-# JMX Component
+## JMX Component
 ifdef::env-github[]
 :caution-caption: :boom:
 :important-caption: :exclamation:
@@ -7,9 +7,7 @@ ifdef::env-github[]
 :warning-caption: :warning:
 endif::[]
 
-[[CamelJMX-CamelJMX]]
-Camel JMX
-~~~~~~~~~
+### Camel JMX
 
 Apache Camel has extensive support for JMX to allow you to monitor and
 control the Camel managed objects with a JMX client.
@@ -19,9 +17,7 @@ subscribe to MBean notifications. This page is about how to manage and
 monitor Camel using JMX.
 
 
-[[CamelJMX-Options]]
-Options
-^^^^^^^
+### Options
 
 // component options: START
 The JMX component has no options.
@@ -68,9 +64,7 @@ The JMX component supports 30 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[CamelJMX-ActivatingJMXinCamel]]
-Activating JMX in Camel
-^^^^^^^^^^^^^^^^^^^^^^^
+### Activating JMX in Camel
 
 [NOTE]
 ====
@@ -86,9 +80,7 @@ From *Camel 2.9* onwards, the Spring JARs are *no* longer required to
 run Camel in JMX mode.
 ====
 
-[[CamelJMX-UsingJMXtomanageApacheCamel]]
-Using JMX to manage Apache Camel
-++++++++++++++++++++++++++++++++
+#### Using JMX to manage Apache Camel
 
 By default, JMX instrumentation agent is enabled in Camel, which means
 that Camel runtime creates and registers MBean management objects with a
@@ -131,9 +123,7 @@ Spring configuration:
 Spring configuration always takes precedence over system properties when
 they both present. It is true for all JMX related configurations.
 
-[[CamelJMX-DisablingJMXinstrumentationagentinCamel]]
-Disabling JMX instrumentation agent in Camel
-++++++++++++++++++++++++++++++++++++++++++++
+#### Disabling JMX instrumentation agent in Camel
 
 You can disable JMX instrumentation agent by setting the Java VM system
 property as follow:
@@ -165,9 +155,7 @@ CamelContext camel = new DefaultCamelContext();
 camel.disableJMX();
 ----
 
-[[CamelJMX-LocatingaMBeanServerintheJavaVM]]
-Locating a MBeanServer in the Java VM
-+++++++++++++++++++++++++++++++++++++
+#### Locating a MBeanServer in the Java VM
 
 Each CamelContext can have an instance of
 http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InstrumentationAgent.html[`InstrumentationAgent`]
@@ -235,9 +223,7 @@ Spring configuration:
 </camelContext>
 ----
 
-[[CamelJMX-CreatingJMXRMIConnectorServer]]
-Creating JMX RMI Connector Server
-+++++++++++++++++++++++++++++++++
+#### Creating JMX RMI Connector Server
 
 JMX connector server enables MBeans to be remotely managed by a JMX
 client such as JConsole; Camel JMX RMI connector server can be
@@ -260,9 +246,7 @@ Spring configuration:
 </camelContext>
 ----
 
-[[CamelJMX-JMXServiceURL]]
-JMX Service URL
-+++++++++++++++
+#### JMX Service URL
 
 The default JMX Service URL has the format:
 
@@ -357,9 +341,7 @@ When the connector port option is set, the JMX service URL will become:
 service:jmx:rmi://localhost:<connectorPort>/jndi/rmi://localhost:<registryPort>/<serviceUrlPath>
 ----
 
-[[CamelJMX-TheSystemPropertiesforCamelJMXsupport]]
-The System Properties for Camel JMX support
-+++++++++++++++++++++++++++++++++++++++++++
+#### The System Properties for Camel JMX support
 
 [width="100%",cols="1m,1,3",options="header",]
 |=======================================================================
@@ -371,9 +353,7 @@ feature in Camel
 See more system properties in this section below: _jmxAgent Properties
 Reference_.
 
-[[CamelJMX-HowtouseauthenticationwithJMX]]
-How to use authentication with JMX
-++++++++++++++++++++++++++++++++++
+#### How to use authentication with JMX
 
 JMX in the JDK have features for authentication and also for using
 secure connections over SSL. You have to refer to the SUN documentation
@@ -382,13 +362,9 @@ how to use this:
 * http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html
 * http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
 
-[[CamelJMX-JMXinsideanApplicationServer]]
-JMX inside an Application Server
-++++++++++++++++++++++++++++++++
+#### JMX inside an Application Server
 
-[[CamelJMX-Tomcat6]]
-Tomcat 6
-++++++++
+#### Tomcat 6
 
 See http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html[this page]
 for details about enabling JMX in Tomcat.
@@ -404,9 +380,7 @@ set the following options...
     -Dcom.sun.management.jmxremote.authenticate=false
 ----
 
-[[CamelJMX-JBossAS4]]
-JBoss AS 4
-++++++++++
+#### JBoss AS 4
 
 By default JBoss creates its own `MBeanServer`. To allow Camel to expose
 to the same server follow these steps:
@@ -426,9 +400,7 @@ Add the following property to your `JAVA_OPTS` by editing `run.sh` or
 `run.conf` `-Djboss.platform.mbeanserver`. See
 http://wiki.jboss.org/wiki/JBossMBeansInJConsole
 
-[[CamelJMX-WebSphere]]
-WebSphere
-+++++++++
+#### WebSphere
 
 Alter the `mbeanServerDefaultDomain` to be `WebSphere`:
 
@@ -437,9 +409,7 @@ Alter the `mbeanServerDefaultDomain` to be `WebSphere`:
 <camel:jmxAgent id="agent" createConnector="true" mbeanObjectDomainName="org.yourname" usePlatformMBeanServer="false" mbeanServerDefaultDomain="WebSphere"/>
 ----
 
-[[CamelJMX-OracleOC4j]]
-Oracle OC4j
-+++++++++++
+#### Oracle OC4j
 
 The Oracle OC4J J2EE application server will not allow Camel to access
 the platform `MBeanServer`. You can identify this in the log as Camel
@@ -456,17 +426,13 @@ java.lang.SecurityException: Unauthorized access from application: xx to MBean:
 To resolve this you should disable the JMX agent in Camel, see section
 _Disabling JMX instrumentation agent in Camel_.
 
-[[CamelJMX-AdvancedJMXConfiguration]]
-Advanced JMX Configuration
-++++++++++++++++++++++++++
+#### Advanced JMX Configuration
 
 The Spring configuration file allows you to configure how Camel is
 exposed to JMX for management. In some cases, you could specify more
 information here, like the connector's port or the path name.
 
-[[CamelJMX-Example:]]
-Example:
-++++++++
+#### Example:
 
 [source,xml]
 ----
@@ -499,9 +465,7 @@ SUNJMX=-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1
 for Camel, as additional startup parameters for the JVM. If you start
 Camel directly, you'll have to pass these parameters yourself.)
 
-[[CamelJMX-jmxAgentPropertiesReference]]
-`jmxAgent` Properties Reference
-+++++++++++++++++++++++++++++++
+#### `jmxAgent` Properties Reference
 
 [width="100%",cols="25%,25%,25%,25%",options="header",]
 |=======================================================================
@@ -567,9 +531,7 @@ usage of each incoming and outgoing endpoints).
 |=======================================================================
 
 
-[[CamelJMX-ConfiguringwhethertoregisterMBeansalways,fornewroutesorjustbydefault]]
-Configuring whether to register MBeans always, for new routes or just by default
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Configuring whether to register MBeans always, for new routes or just by default
 
 
 *Available as of Camel 2.7*
@@ -600,13 +562,9 @@ also be registered. This could potential lead to system degration due
 the rising number of mbeans in the registry. A MBean is not a
 light-weight object and thus consumes memory.
 
-[[CamelJMX-MonitoringCamelusingJMX]]
-Monitoring Camel using JMX
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Monitoring Camel using JMX
 
-[[CamelJMX-UsingJConsoletomonitorCamel]]
-Using JConsole to monitor Camel
-+++++++++++++++++++++++++++++++
+#### Using JConsole to monitor Camel
 
 The `CamelContext` should appear in the list of local connections, if
 you are running JConsole on the same host as Camel.
@@ -619,9 +577,7 @@ Using the Apache Camel with JConsole:
 
 image:camel-jmx.png[image]
 
-[[CamelJMX-Whichendpointsareregistered]]
-Which endpoints are registered
-++++++++++++++++++++++++++++++
+#### Which endpoints are registered
 
 In *Camel 2.1* onwards *only* `singleton` endpoints are registered as
 the overhead for non singleton will be substantial in cases where
@@ -629,15 +585,11 @@ thousands or millions of endpoints are used. This can happens when using
 a link:recipient-list.html[Recipient List] EIP or from a
 `ProducerTemplate` that sends a lot of messages.
 
-[[CamelJMX-Whichprocessorsareregistered]]
-Which processors are registered
-+++++++++++++++++++++++++++++++
+#### Which processors are registered
 
 See link:why-is-my-processor-not-showing-up-in-jconsole.html[this FAQ].
 
-[[CamelJMX-HowtousetheJMXNotificationListenertolistenthecamelevents]]
-How to use the JMX NotificationListener to listen the camel events?
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### How to use the JMX NotificationListener to listen the camel events?
 
 The Camel notification events give a coarse grained overview what is
 happening. You can see lifecycle event from context and endpoints and
@@ -680,9 +632,7 @@ context.getManagementStrategy().getManagementAgent().getMBeanServer().addNotific
     }, null);
 ----
 
-[[CamelJMX-UsingtheTracerMBeantogetfinegrainedtracing]]
-Using the Tracer MBean to get fine grained tracing
-++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using the Tracer MBean to get fine grained tracing
 
 Additionally to the coarse grained notifications above *Camel 2.9.0*
 support JMX Notification for fine grained trace events.
@@ -703,13 +653,9 @@ route with all exchange and message details:
 
 image:jconsole_trace_notifications.png[image]
 
-[[CamelJMX-UsingJMXforyourownCamelCode]]
-Using JMX for your own Camel Code
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using JMX for your own Camel Code
 
-[[CamelJMX-RegisteringyourownManagedEndpoints]]
-Registering your own Managed Endpoints
-++++++++++++++++++++++++++++++++++++++
+#### Registering your own Managed Endpoints
 
 *Available as of Camel 2.0* +
 You can decorate your own endpoints with Spring managed annotations
@@ -764,9 +710,7 @@ Notice from *Camel 2.9* onwards its encouraged to use the
 the `org.apache.camel.api.management` package. This allows your custom
 code to not depend on Spring JARs.
 
-[[CamelJMX-ProgrammingyourownManagedServices]]
-Programming your own Managed Services
-+++++++++++++++++++++++++++++++++++++
+#### Programming your own Managed Services
 
 *Available as of Camel 2.1*
 
@@ -820,9 +764,7 @@ types such as:
 
 And in the future we will add additional wrappers for more EIP patterns.
 
-[[CamelJMX-ManagementNamingStrategy]]
-ManagementNamingStrategy
-++++++++++++++++++++++++
+#### ManagementNamingStrategy
 
 *Available as of Camel 2.1*
 
@@ -831,9 +773,7 @@ Camel provides a pluggable API for naming strategy by
 implementation is used to compute the MBean names that all MBeans are
 registered with.
 
-[[CamelJMX-Managementnamingpattern]]
-Management naming pattern
-+++++++++++++++++++++++++
+#### Management naming pattern
 
 *Available as of Camel 2.10*
 
@@ -975,9 +915,7 @@ install a 2nd Camel application that has the same `CamelContext` id and
 `managementNamePattern` then Camel will fail upon starting, and report a
 MBean already exists exception.
 
-[[CamelJMX-ManagementStrategy]]
-ManagementStrategy
-++++++++++++++++++
+#### ManagementStrategy
 
 *Available as of Camel 2.1*
 
@@ -990,9 +928,7 @@ does, for example, is make it easier to provide an adapter for other
 management products. In addition, it also allows you to provide more
 details and features that are provided out of the box at Apache.
 
-[[CamelJMX-Configuringlevelofgranularityforperformancestatistics]]
-Configuring level of granularity for performance statistics
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Configuring level of granularity for performance statistics
 
 *Available as of Camel 2.1*
 
@@ -1053,9 +989,7 @@ And from Spring DSL you do:
 </camelContext>
 ----
 
-[[CamelJMX-Hidingsensitiveinformation]]
-Hiding sensitive information
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Hiding sensitive information
 
 *Available as of Camel 2.12*
 
@@ -1087,9 +1021,7 @@ And from Spring DSL you do:
 This will mask link:uris.html[URIs] having options such as password and
 passphrase, and use `xxxxxx` as the replacement value.
 
-[[CamelJMX-DeclaringwhichJMXattributesandoperationstomask]]
-Declaring which JMX attributes and operations to mask
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Declaring which JMX attributes and operations to mask
 
 On the `org.apache.camel.api.management.ManagedAttribute` and
 `org.apache.camel.api.management.ManagedOperation`, the attribute `mask`
@@ -1107,10 +1039,8 @@ declared that the `EndpointUri` JMX attribute is masked:
 String getEndpointUri();
 ----
 
-[[CamelJMX-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:management-example.html[Management Example]
 * link:why-is-my-processor-not-showing-up-in-jconsole.html[Why is my
-processor not showing up in JConsole]
+processor not showing up in JConsole]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc b/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
index 965e573..b10ebef 100644
--- a/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
+++ b/components/camel-johnzon/src/main/docs/json-johnzon-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon Johnzon DataFormat
+## JSon Johnzon DataFormat
 
 *Available as of Camel 2.18*
 
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[Johnzon-Options]]
-Johnzon Options
-^^^^^^^^^^^^^^^
+### Johnzon Options
 
 
 
@@ -50,9 +48,7 @@ The JSon Johnzon dataformat supports 17 options which are listed below.
 
 
 
-[[Johnzon-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Johnzon in your camel routes you need to add the dependency
 on *camel-johnzon* which implements this data format.
@@ -69,4 +65,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jolt/src/main/docs/jolt-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jolt/src/main/docs/jolt-component.adoc b/components/camel-jolt/src/main/docs/jolt-component.adoc
index ed25e5a..6011851 100644
--- a/components/camel-jolt/src/main/docs/jolt-component.adoc
+++ b/components/camel-jolt/src/main/docs/jolt-component.adoc
@@ -1,4 +1,4 @@
-# JOLT Component
+## JOLT Component
 
 *Available as of Camel 2.16*
 
@@ -21,9 +21,7 @@ their `pom.xml` for this component:
 
 Â 
 
-[[JOLT-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------
@@ -37,9 +35,7 @@ invoke; or the complete URL of the remote specification
 You can append query options to the URI in the following
 format, `?option=value&option=value&...`
 
-[[JOLT-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -82,9 +78,7 @@ The JOLT component supports 6 endpoint options which are listed below:
 
 
 
-[[JOLT-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example you could use something like
 
@@ -115,12 +109,9 @@ from("direct:in").
 
 Â 
 
-[[JOLT-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-josql/src/main/docs/sql-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-josql/src/main/docs/sql-language.adoc b/components/camel-josql/src/main/docs/sql-language.adoc
index 7038d5f..502897f 100644
--- a/components/camel-josql/src/main/docs/sql-language.adoc
+++ b/components/camel-josql/src/main/docs/sql-language.adoc
@@ -1,4 +1,4 @@
-# SQL Language
+## SQL Language
 
 The SQL support is added by http://josql.sourceforge.net/[JoSQL] and is
 primarily used for performing SQL queries on in-memory objects. If you
@@ -53,9 +53,7 @@ And the spring DSL:
    <to uri="queue:bar"/>
 --------------------------------------
 
-[[SQL-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // language options: START
@@ -73,9 +71,7 @@ The SQL language supports 1 options which are listed below.
 // language options: END
 
 
-[[SQL-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -87,4 +83,4 @@ eg to refer to a file on the classpath you can do:
 [source,java]
 ----------------------------------------------------------
 .setHeader("myHeader").sql("resource:classpath:mysql.sql")
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jpa/src/main/docs/jpa-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jpa/src/main/docs/jpa-component.adoc b/components/camel-jpa/src/main/docs/jpa-component.adoc
index e79d410..c8af852 100644
--- a/components/camel-jpa/src/main/docs/jpa-component.adoc
+++ b/components/camel-jpa/src/main/docs/jpa-component.adoc
@@ -1,4 +1,4 @@
-# JPA Component
+## JPA Component
 
 The *jpa* component enables you to store and retrieve Java objects from
 persistent storage using EJB 3's Java Persistence Architecture (JPA),
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[JPA-Sendingtotheendpoint]]
-Sending to the endpoint
-^^^^^^^^^^^^^^^^^^^^^^^
+### Sending to the endpoint
 
 You can store a Java entity bean in a database by sending it to a JPA
 producer endpoint. The body of the _In_ message is assumed to be an
@@ -36,9 +34,7 @@ If the body does not contain one of the previous listed types, put a
 link:message-translator.html[Message Translator] in front of the
 endpoint to perform the necessary conversion first.
 
-[[JPA-Consumingfromtheendpoint]]
-Consuming from the endpoint
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming from the endpoint
 
 Consuming messages from a JPA consumer endpoint removes (or updates)
 entity beans in the database. This allows you to use a database table as
@@ -64,9 +60,7 @@ which will be invoked on your entity bean before it has been processed
 If you are consuming a lot (100K+) of rows and experience OutOfMemory
 problems you should set the maximumResults to sensible value.
 
-[[JPA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -82,9 +76,7 @@ For consuming, the _entityClassName_ is mandatory.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[JPA-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -170,9 +162,7 @@ The JPA component supports 42 endpoint options which are listed below:
 
 
 
-[[JPA-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel adds the following message headers to the exchange:
 
@@ -192,9 +182,7 @@ reason why the support for this header has been dropped.
 
 |=======================================================================
 
-[[JPA-ConfiguringEntityManagerFactory]]
-Configuring EntityManagerFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring EntityManagerFactory
 
 Its strongly advised to configure the JPA component to use a specific
 `EntityManagerFactory` instance. If failed to do so each `JpaEndpoint`
@@ -217,9 +205,7 @@ you do not need to configure this on the `JpaComponent` as shown above.
 You only need to do so if there is ambiguity, in which case Camel will
 log a WARN.
 
-[[JPA-ConfiguringTransactionManager]]
-Configuring TransactionManager
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring TransactionManager
 
 Since *Camel 2.3* the `JpaComponent` will auto lookup the
 `TransactionManager` from the link:registry.html[Registry.] If Camel
@@ -244,9 +230,7 @@ explicitly configure a JPA component that references the
 </bean>
 -------------------------------------------------------------------
 
-[[JPA-Usingaconsumerwithanamedquery]]
-Using a consumer with a named query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a named query
 
 For consuming only selected entities, you can use the
 `consumer.namedQuery` URI query option. First, you have to define the
@@ -269,9 +253,7 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.namedQuery=step1")
 .to("bean:myBusinessLogic");
 ----------------------------------------------------------------------------
 
-[[JPA-Usingaconsumerwithaquery]]
-Using a consumer with a query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a query
 
 For consuming only selected entities, you can use the `consumer.query`
 URI query option. You only have to define the query option:
@@ -282,9 +264,7 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.query=select o from or
 .to("bean:myBusinessLogic");
 ---------------------------------------------------------------------------------------------------------------------------------------
 
-[[JPA-Usingaconsumerwithanativequery]]
-Using a consumer with a native query
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using a consumer with a native query
 
 For consuming only selected entities, you can use the
 `consumer.nativeQuery` URI query option. You only have to define the
@@ -299,16 +279,12 @@ from("jpa://org.apache.camel.examples.MultiSteps?consumer.nativeQuery=select * f
 If you use the native query option, you will receive an object array in
 the message body.
 
-[[JPA-Example]]
-Example
-^^^^^^^
+### Example
 
 See link:tracer-example.html[Tracer Example] for an example using
 link:jpa.html[JPA] to store traced messages into a database.
 
-[[JPA-UsingtheJPAbasedidempotentrepository]]
-Using the JPA based idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the JPA based idempotent repository
 
 In this section we will use the JPA based idempotent repository.
 
@@ -380,14 +356,11 @@ argument to the JVM:
 Then it will all become green again
 image:https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png[(smile)]
 
-[[JPA-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:tracer-example.html[Tracer Example]
-
+* link:tracer-example.html[Tracer Example]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jsch/src/main/docs/scp-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jsch/src/main/docs/scp-component.adoc b/components/camel-jsch/src/main/docs/scp-component.adoc
index c92cbf5..3d4b6c0 100644
--- a/components/camel-jsch/src/main/docs/scp-component.adoc
+++ b/components/camel-jsch/src/main/docs/scp-component.adoc
@@ -1,4 +1,4 @@
-# SCP Component
+## SCP Component
 
 The *camel-jsch* component supports the
 http://en.wikipedia.org/wiki/Secure_copy[SCP protocol] using the Client
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Jsch-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------
@@ -35,9 +33,7 @@ The file name can be specified either in the <path> part of the URI or
 as a "CamelFileName" header on the message (`Exchange.FILE_NAME` if used
 in code).
 
-[[Jsch-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -102,20 +98,15 @@ The SCP component supports 22 endpoint options which are listed below:
 
 
 
-[[Jsch-Limitations]]
-Limitations
-^^^^^^^^^^^
+### Limitations
 
 Currently camel-jsch only supports a
 http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Producer.html[Producer]
 (i.e. copy files to another host). 
 
-[[Jsch-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
index 766cec4..57f6fec 100644
--- a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
+++ b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
@@ -1,4 +1,4 @@
-# JSonPath Language
+## JSonPath Language
 
 *Available as of Camel 2.13*
 
@@ -18,9 +18,7 @@ from("queue:books.new")
       .to("jms:queue:book.expensive")
 -----------------------------------------------------
 
-[[JSonPath-Options]]
-JSonPath Options
-^^^^^^^^^^^^^^^^
+### JSonPath Options
 
 
 // language options: START
@@ -42,9 +40,7 @@ The JSonPath language supports 4 options which are listed below.
 
 
 
-[[JSonPath-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
 
 If you prefer to configure your routes in your link:spring.html[Spring]
 XML file then you can use link:jsonpath.html[JSonPath] expressions as
@@ -72,16 +68,12 @@ follows
   </camelContext>
 -------------------------------------------------------------------------
 
-[[JSonPath-Syntax]]
-Syntax
-^^^^^^
+### Syntax
 
 See the https://code.google.com/p/json-path/[JSonPath] project page for
 further examples.
 
-[[JSonPath-SupportedType]]
-Supported message body types
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+### Supported message body types
 
 Camel JSonPath supports message body using the following types:
 
@@ -104,9 +96,7 @@ If a message body is of unsupported type then an exception is thrown by default,
 can configure JSonPath to suppress exceptions (see below)
 
 
-[[JSonPath-Suppressexceptions]]
-Suppress exceptions
-~~~~~~~~~~~~~~~~~~~
+### Suppress exceptions
 
 *Available as of Camel 2.16*
 
@@ -149,9 +139,7 @@ And in XML DSL:
 
 This option is also available on the `@JsonPath` annotation.
 
-[[JSonPath-InlineSimple]]
-Inline Simple exceptions
-~~~~~~~~~~~~~~~~~~~~~~~~
+### Inline Simple exceptions
 
 *Available as of Camel 2.18*
 
@@ -207,9 +195,7 @@ And in XML DSL:
 --------------------------------------------------------------------------
 
 
-[[JSonPath-JSonPathinjection]]
-JSonPath injection
-~~~~~~~~~~~~~~~~~~
+### JSonPath injection
 
 You can use link:bean-integration.html[Bean Integration] to invoke a
 method on a bean and use various languages such as JSonPath to extract a
@@ -228,9 +214,7 @@ public class Foo {
 }
 ---------------------------------------------------------------------------------------------------
 
-[[JSonPath-EncodingDetection]]
-Encoding Detection
-~~~~~~~~~~~~~~~~~~
+### Encoding Detection
 
 *Since Camel version 2.16*, the encoding of the JSON document is
 detected automatically, if the document is encoded in unicode  (UTF-8,
@@ -240,9 +224,7 @@ you enter the document in String format to the JSONPath component or you
 can specify the encoding in the header "*CamelJsonPathJsonEncoding*"
 (JsonpathConstants.HEADER_JSON_ENCODING).
 
-[[JSonPath-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use JSonPath in your camel routes you need to add the a dependency on
 *camel-jsonpath* which implements the JSonPath language.
@@ -258,4 +240,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-jsonpath</artifactId>
   <version>x.x.x</version>
 </dependency>
------------------------------------------
+-----------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jt400/src/main/docs/jt400-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jt400/src/main/docs/jt400-component.adoc b/components/camel-jt400/src/main/docs/jt400-component.adoc
index 1f0720c..84150ef 100644
--- a/components/camel-jt400/src/main/docs/jt400-component.adoc
+++ b/components/camel-jt400/src/main/docs/jt400-component.adoc
@@ -1,4 +1,4 @@
-# JT400 Component
+## JT400 Component
 
 The *`jt400`* component allows you to exchanges messages with an AS/400
 system using data queues.
@@ -16,9 +16,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[JT400-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------------------------------------------
@@ -35,9 +33,7 @@ jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/program.PGM[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[JT400-options]]
-JT400 options
-^^^^^^^^^^^^^
+### JT400 options
 
 // component options: START
 The JT400 component supports 1 options which are listed below.
@@ -100,9 +96,7 @@ The JT400 component supports 34 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[JT400-Usage]]
-Usage
-^^^^^
+### Usage
 
 When configured as a consumer endpoint, the endpoint will poll a data
 queue on a remote system. For every entry on the data queue, a new
@@ -111,9 +105,7 @@ formatted either as a `String` or a `byte[]`, depending on the format.
 For a provider endpoint, the _In_ message body contents will be put on
 the data queue as either raw bytes or text.
 
-[[JT400-Connectionpool]]
-Connection pool
-^^^^^^^^^^^^^^^
+### Connection pool
 
 *Available as of Camel 2.10*
 
@@ -121,9 +113,7 @@ Connection pooling is in use from Camel 2.10 onwards. You can explicit
 configure a connection pool on the Jt400Component, or as an uri option
 on the endpoint.
 
-[[JT400-Remoteprogramcall]]
-Remote program call (*Camel 2.7*)
-+++++++++++++++++++++++++++++++++
+#### Remote program call (*Camel 2.7*)
 
 This endpoint expects the input to be either a String array or byte[]
 array (depending on format) and handles all the CCSID handling through
@@ -134,9 +124,7 @@ String array or byte[] array with the values as they were returned by
 the program (the input only parameters will contain the same data as the
 beginning of the invocation). This endpoint does not implement a provider endpoint!
 
-[[JT400-Example]]
-Example
-^^^^^^^
+### Example
 
 In the snippet below, the data for an exchange sent to the
 `direct:george` endpoint will be put in the data queue `PENNYLANE` in
@@ -155,9 +143,7 @@ public class Jt400RouteBuilder extends RouteBuilder {
 }
 -------------------------------------------------------------------------------------------------------
 
-[[JT400-Remoteprogramcallexample]]
-Remote program call example (*Camel 2.7*)
-+++++++++++++++++++++++++++++++++++++++++
+#### Remote program call example (*Camel 2.7*)
 
 In the snippet below, the data Exchange sent to the direct:work endpoint
 will contain three string that will be used as the arguments for the
@@ -175,9 +161,7 @@ public class Jt400RouteBuilder extends RouteBuilder {
 }
 ---------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[JT400-Writingtokeyeddataqueues]]
-Writing to keyed data queues
-++++++++++++++++++++++++++++
+#### Writing to keyed data queues
 
 [source,java]
 ------------------------------------------------------------------------
@@ -185,9 +169,7 @@ from("jms:queue:input")
 .to("jt400://username:password@system/lib.lib/MSGINDQ.DTAQ?keyed=true");
 ------------------------------------------------------------------------
 
-[[JT400-Readingfromkeyeddataqueues]]
-Reading from keyed data queues
-++++++++++++++++++++++++++++++
+#### Reading from keyed data queues
 
 [source,java]
 -------------------------------------------------------------------------------------------------------
@@ -195,12 +177,9 @@ from("jt400://username:password@system/lib.lib/MSGOUTDQ.DTAQ?keyed=true&searchKe
 .to("jms:queue:output");
 -------------------------------------------------------------------------------------------------------
 
-[[JT400-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-juel/src/main/docs/el-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-juel/src/main/docs/el-language.adoc b/components/camel-juel/src/main/docs/el-language.adoc
index 440d2a3..10a0679 100644
--- a/components/camel-juel/src/main/docs/el-language.adoc
+++ b/components/camel-juel/src/main/docs/el-language.adoc
@@ -1,4 +1,4 @@
-# EL Language
+## EL Language
 [[EL-EL]]
 EL
 ~~
@@ -42,9 +42,7 @@ link:message-filter.html[Message Filter] or as an
 link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[EL-Options]]
-EL Options
-^^^^^^^^^^
+### EL Options
 
 
 
@@ -64,9 +62,7 @@ The EL language supports 1 options which are listed below.
 
 
 
-[[EL-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -79,9 +75,7 @@ Variables
 |out |Message |the exchange.out message
 |=======================================================================
 
-[[EL-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 You can use EL dot notation to invoke operations. If you for instance
 have a body that contains a POJO that has a `getFamiliyName` method then
@@ -92,9 +86,7 @@ you can construct the syntax as follows:
 "${in.body.familyName}"
 -----------------------
 
-[[EL-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use EL in your camel routes you need to add the a dependency on
 *camel-juel* which implements the EL language.
@@ -113,4 +105,4 @@ link:download.html[the download page for the latest versions]).
 -------------------------------------
 
 Otherwise you'll also need to include
-http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar[JUEL].
+http://repo2.maven.org/maven2/de/odysseus/juel/juel/2.1.3/juel-2.1.3.jar[JUEL].
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jxpath/src/main/docs/jxpath-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jxpath/src/main/docs/jxpath-language.adoc b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
index 3d6f0d8..de69ead 100644
--- a/components/camel-jxpath/src/main/docs/jxpath-language.adoc
+++ b/components/camel-jxpath/src/main/docs/jxpath-language.adoc
@@ -1,4 +1,4 @@
-# JXPath Language
+## JXPath Language
 
 Camel supports http://commons.apache.org/jxpath/[JXPath] to allow
 link:xpath.html[XPath] expressions to be used on beans in an
@@ -19,9 +19,7 @@ from("queue:foo").filter().
   to("queue:bar")
 ---------------------------
 
-[[JXPath-Options]]
-JXPath Options
-^^^^^^^^^^^^^^
+### JXPath Options
 
 
 // language options: START
@@ -41,9 +39,7 @@ The JXPath language supports 2 options which are listed below.
 
 
 
-[[JXPath-Variables]]
-Variables
-^^^^^^^^^
+### Variables
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -56,9 +52,7 @@ Variables
 |out |Message |the exchange.out message
 |=======================================================================
 
-[[JXPath-Options]]
-Options
-^^^^^^^
+### Options
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -72,9 +66,7 @@ http://commons.apache.org/proper/commons-jxpath//users-guide.html#Lenient_Mode[J
 Documentation] This option is by default false.
 |=======================================================================
 
-[[JXPath-UsingXMLconfiguration]]
-Using XML configuration
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using XML configuration
 
 If you prefer to configure your routes in your link:spring.html[Spring]
 XML file then you can use JXPath expressions as follows
@@ -99,18 +91,14 @@ XML file then you can use JXPath expressions as follows
 </beans>
 ---------------------------------------------------------------------------------------------------------------
 
-[[JXPath-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 Here is a simple
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-jxpath/src/test/java/org/apache/camel/language/jxpath/JXPathFilterTest.java[example]
 using a JXPath expression as a predicate in a
 link:message-filter.html[Message Filter]
 
-[[JXPath-JXPathinjection]]
-JXPath injection
-~~~~~~~~~~~~~~~~
+### JXPath injection
 
 You can use link:bean-integration.html[Bean Integration] to invoke a
 method on a bean and use various languages such as JXPath to extract a
@@ -129,9 +117,7 @@ public class Foo {
 }
 ---------------------------------------------------------------------------------------------
 
-[[JXPath-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -145,9 +131,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").jxpath("resource:classpath:myjxpath.txt")
 ----------------------------------------------------------------
 
-[[JXPath-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use JXpath in your camel routes you need to add the a dependency on
 *camel-jxpath* which implements the JXpath language.
@@ -167,4 +151,4 @@ link:download.html[the download page for the latest versions]).
 
 Otherwise, you'll also need
 http://repo2.maven.org/maven2/commons-jxpath/commons-jxpath/1.3/commons-jxpath-1.3.jar[Commons
-JXPath].
+JXPath].
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kafka/src/main/docs/kafka-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc b/components/camel-kafka/src/main/docs/kafka-component.adoc
index 1700c0e..79b7c50 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -1,4 +1,4 @@
-# Kafka Component
+## Kafka Component
 
 *Available as of Camel 2.13*
 
@@ -18,15 +18,11 @@ for this component.
 </dependency>
 ------------------------------------------------------------
 
-[[Kafka-Camel2.17ornewer]]
-Camel 2.17 or newer
-+++++++++++++++++++
+#### Camel 2.17 or newer
 
 Scala is no longer used, as we use the kafka java client.
 
-[[Kafka-Camel2.16orolder]]
-Camel 2.16 or older
-+++++++++++++++++++
+#### Camel 2.16 or older
 
 And then the Scala libraries of choice. camel-kafka does not include
 that dependency, but assumes it is provided. For example to use Scala
@@ -41,9 +37,7 @@ that dependency, but assumes it is provided. For example to use Scala
     </dependency>
 --------------------------------------------
 
-[[Kafka-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------
@@ -52,9 +46,7 @@ kafka:server:port[?options]
 
 Â 
 
-[[Kafka-Options]]
-Options (Camel 2.16 or older)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Options (Camel 2.16 or older)
 
 
 
@@ -203,13 +195,9 @@ For more information about Producer/Consumer configuration:
 http://kafka.apache.org/documentation.html#newconsumerconfigs[http://kafka.apache.org/documentation.html#newconsumerconfigs]
 http://kafka.apache.org/documentation.html#producerconfigs[http://kafka.apache.org/documentation.html#producerconfigs]
 
-[[Kafka-Samples]]
-Samples
-^^^^^^^
+### Samples
 
-[[Kafka-Camel2.16orolder.1]]
-Camel 2.16 or older
-+++++++++++++++++++
+#### Camel 2.16 or older
 
 Consuming messages:
 
@@ -222,9 +210,7 @@ Producing messages:
 
 See unit tests of camel-kafka for more examples
 
-[[Kafka-Camel2.17ornewer]]
-Camel 2.17 or newer
-+++++++++++++++++++
+#### Camel 2.17 or newer
 
 Consuming messages:
 
@@ -276,9 +262,7 @@ from("direct:start").process(new Processor() {
 
 Â 
 
-[[Kafka-Endpoints]]
-Endpoints
-~~~~~~~~~
+### Endpoints
 
 Camel supports the link:message-endpoint.html[Message Endpoint] pattern
 using the
@@ -306,12 +290,9 @@ implements the link:polling-consumer.html[Polling Consumer] pattern for
 consuming message exchanges from the endpoint via a
 http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
 
-[[Kafka-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:message-endpoint.html[Message Endpoint] pattern
 * link:uris.html[URIs]
-* link:writing-components.html[Writing Components]
-
+* link:writing-components.html[Writing Components]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kestrel/src/main/docs/kestrel-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kestrel/src/main/docs/kestrel-component.adoc b/components/camel-kestrel/src/main/docs/kestrel-component.adoc
index ba8d963..025a475 100644
--- a/components/camel-kestrel/src/main/docs/kestrel-component.adoc
+++ b/components/camel-kestrel/src/main/docs/kestrel-component.adoc
@@ -1,4 +1,4 @@
-# Kestrel Component
+## Kestrel Component
 
 The Kestrel component allows messages to be sent to a
 https://github.com/robey/kestrel[Kestrel] queue, or messages to be
@@ -10,9 +10,7 @@ WARNING: The kestrel project is inactive and the Camel team regard this
 components as deprecated.
 
 
-[[Kestrel-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------
@@ -59,9 +57,7 @@ concurrently from a queue:
 kestrel://kserver03:22133/massive?concurrentConsumers=25&waitTimeMs=500
 -----------------------------------------------------------------------
 
-[[Kestrel-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -108,9 +104,7 @@ The Kestrel component supports 8 endpoint options which are listed below:
 
 
 
-[[Kestrel-ConfiguringtheKestrelcomponentusingSpringXML]]
-Configuring the Kestrel component using Spring XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the Kestrel component using Spring XML
 
 The simplest form of explicit configuration is as follows:
 
@@ -162,13 +156,9 @@ can set up a KestrelConfiguration POJO as follows:
 </beans>
 ---------------------------------------------------------------------------------------------------------------
 
-[[Kestrel-UsageExamples]]
-Usage Examples
-^^^^^^^^^^^^^^
+### Usage Examples
 
-[[Kestrel-Example1:Consuming]]
-Example 1: Consuming
-++++++++++++++++++++
+#### Example 1: Consuming
 
 [source,java]
 -------------------------------------------------------------------------------
@@ -185,9 +175,7 @@ public class MyConsumer {
 }
 -------------------------------------------
 
-[[Kestrel-Example2:Producing]]
-Example 2: Producing
-++++++++++++++++++++
+#### Example 2: Producing
 
 [source,java]
 ------------------------------------------------------------------------------
@@ -201,9 +189,7 @@ public class MyProducer {
 }
 ------------------------------------------------------------------------------
 
-[[Kestrel-Example3:SpringXMLConfiguration]]
-Example 3: Spring XML Configuration
-+++++++++++++++++++++++++++++++++++
+#### Example 3: Spring XML Configuration
 
 [source,xml]
 ----------------------------------------------------------------------------------------
@@ -228,17 +214,13 @@ public class MyBean {
 }
 -------------------------------------------
 
-[[Kestrel-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 The Kestrel component has the following dependencies:
 
 * `spymemcached` 2.5 (or greater)
 
-[[Kestrel-spymemcached]]
-spymemcached
-++++++++++++
+#### spymemcached
 
 You *must* have the `spymemcached` jar on your classpath. Here is a
 snippet you can use in your pom.xml:
@@ -273,12 +255,9 @@ you may need to set `enableAssertions` to `false`. Please refer to the
 http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html[surefire:test
 reference] for details.
 
-[[Kestrel-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-krati/src/main/docs/krati-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-krati/src/main/docs/krati-component.adoc b/components/camel-krati/src/main/docs/krati-component.adoc
index 996356e..0268736 100644
--- a/components/camel-krati/src/main/docs/krati-component.adoc
+++ b/components/camel-krati/src/main/docs/krati-component.adoc
@@ -1,4 +1,4 @@
-# Krati Component
+## Krati Component
 
 *Available as of Camel 2.9*
 
@@ -25,9 +25,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Krati-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------
@@ -40,9 +38,7 @@ krati will use for its datastore.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Krati-KratiOptions]]
-Krati Options
-^^^^^^^^^^^^^
+### Krati Options
 
 
 // component options: START
@@ -107,9 +103,7 @@ krati:/tmp/krati?operation=CamelKratiGet&initialCapacity=10000&keySerializer=#my
 For producer endpoint you can override all of the above URI options by
 passing the appropriate headers to the message.
 
-[[Krati-MessageHeadersfordatastore]]
-Message Headers for datastore
-+++++++++++++++++++++++++++++
+#### Message Headers for datastore
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -123,13 +117,9 @@ CamelKratiDelete, CamelKratiDeleteAll
 |`CamelKratiValue` |The value.
 |=======================================================================
 
-[[Krati-UsageSamples]]
-Usage Samples
-^^^^^^^^^^^^^
+### Usage Samples
 
-[[Krati-Example1:Puttingtothedatastore.]]
-Example 1: Putting to the datastore.
-++++++++++++++++++++++++++++++++++++
+#### Example 1: Putting to the datastore.
 
 This example will show you how you can store any message inside a
 datastore.
@@ -152,9 +142,7 @@ route.
         </route>
 ------------------------------------------------------------
 
-[[Krati-Example2:GettingReadingfromadatastore]]
-Example 2: Getting/Reading from a datastore
-+++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Getting/Reading from a datastore
 
 This example will show you how you can read the contnet of a datastore.
 
@@ -178,9 +166,7 @@ route.
 </route>
 -----------------------------------------------------------------------------
 
-[[Krati-Example3:Consumingfromadatastore]]
-Example 3: Consuming from a datastore
-+++++++++++++++++++++++++++++++++++++
+#### Example 3: Consuming from a datastore
 
 This example will consume all items that are under the specified
 datastore.
@@ -201,9 +187,7 @@ You can achieve the same goal by using xml, as you can see below.
 </route>
 ------------------------------------------------------
 
-[[Krati-IdempotentRepository]]
-Idempotent Repository
-^^^^^^^^^^^^^^^^^^^^^
+### Idempotent Repository
 
 As already mentioned this component also offers and idemptonet
 repository which can be used for filtering out duplicate messages.
@@ -213,8 +197,6 @@ repository which can be used for filtering out duplicate messages.
 from("direct://in").idempotentConsumer(header("messageId"), new KratiIdempotentRepositroy("/tmp/idempotent").to("log://out");
 -----------------------------------------------------------------------------------------------------------------------------
 
-[[Krati-Seealso]]
-See also
-++++++++
+#### See also
 
-http://sna-projects.com/krati/[Krati Website]
+http://sna-projects.com/krati/[Krati Website]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc b/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
index 4978059..f7d30b7 100644
--- a/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
+++ b/components/camel-kubernetes/src/main/docs/kubernetes-component.adoc
@@ -1,4 +1,4 @@
-# Kubernetes Component
+## Kubernetes Component
 
 *Available as of Camel 2.17*
 
@@ -18,9 +18,7 @@ their `pom.xml` for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Kubernetes-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------
@@ -30,9 +28,7 @@ kubernetes:masterUrl[?options]
 You can append query options to the URI in the following
 format, `?option=value&option=value&...`
 
-[[Kubernetes-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -91,9 +87,7 @@ The Kubernetes component supports 28 endpoint options which are listed below:
 
 
 
-[[Kubernetes-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -174,4 +168,4 @@ Headers
 |CamelKubernetesConfigMapsLabels |Map |ConfigMap labels
 
 |CamelKubernetesConfigData |Map |ConfigMap Data
-|=======================================================================
+|=======================================================================
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ldap/src/main/docs/ldap-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ldap/src/main/docs/ldap-component.adoc b/components/camel-ldap/src/main/docs/ldap-component.adoc
index 2489e78..b711cea 100644
--- a/components/camel-ldap/src/main/docs/ldap-component.adoc
+++ b/components/camel-ldap/src/main/docs/ldap-component.adoc
@@ -1,4 +1,4 @@
-# LDAP Component
+## LDAP Component
 
 The *ldap* component allows you to perform searches in LDAP servers
 using filters as the message payload. +
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[LDAP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -36,9 +34,7 @@ the start of a route.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[LDAP-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -67,16 +63,12 @@ The LDAP component supports 6 endpoint options which are listed below:
 
 
 
-[[LDAP-Result]]
-Result
-^^^^^^
+### Result
 
 The result is returned in the Out body as a
 `ArrayList<javax.naming.directory.SearchResult>` object.
 
-[[LDAP-DirContext]]
-DirContext
-^^^^^^^^^^
+### DirContext
 
 The URI, `ldap:ldapserver`, references a Spring bean with the ID,
 `ldapserver`. The `ldapserver` bean may be defined as follows:
@@ -104,9 +96,7 @@ or that the context supports concurrency. In the Spring framework,
 `prototype` scoped objects are instantiated each time they are looked
 up.
 
-[[LDAP-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 Following on from the Spring configuration above, the code sample below
 sends an LDAP request to filter search a group for a member. The Common
@@ -145,9 +135,7 @@ if the LDAP entry has a Common Name, use a filter expression like:
 (cn=*)
 ------
 
-[[LDAP-Bindingusingcredentials]]
-Binding using credentials
-+++++++++++++++++++++++++
+#### Binding using credentials
 
 A Camel end user donated this sample code he used to bind to the ldap
 server using credentials.
@@ -192,9 +180,7 @@ System.out.println(out.getOut().getBody());
 context.stop();
 ---------------------------------------------------------------------------------------
 
-[[LDAP-ConfiguringSSL]]
-Configuring SSL
-^^^^^^^^^^^^^^^
+### Configuring SSL
 
 All required is to create a custom socket factory and reference it in
 the InitialDirContext bean - see below sample.
@@ -335,12 +321,9 @@ public class CustomSocketFactory extends SSLSocketFactory {
 
 Â 
 
-[[LDAP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc b/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
index fa81b62..ca5c9dc 100644
--- a/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
+++ b/components/camel-linkedin/camel-linkedin-component/src/main/docs/linkedin-component.adoc
@@ -1,4 +1,4 @@
-# Linkedin Component
+## Linkedin Component
 
 *Available as of Camel 2.14*
 
@@ -29,9 +29,7 @@ for this component:
     </dependency>
 -----------------------------------------------
 
-[[LinkedIn-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------------
@@ -48,9 +46,7 @@ Endpoint prefix can be one of:
 * posts
 * search
 
-[[LinkedIn-LinkedInComponent.1]]
-LinkedInComponent
-^^^^^^^^^^^^^^^^^
+### LinkedInComponent
 
 
 
@@ -101,9 +97,7 @@ The Linkedin component supports 16 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[LinkedIn-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
+### Producer Endpoints:
 
 Producer endpoints can use endpoint prefixes followed by endpoint names
 and associated options described next. A shorthand alias can be used for
@@ -125,9 +119,7 @@ For more information on the endpoints and options see LinkedIn REST API
 documentation
 at https://developer.linkedin.com/rest[https://developer.linkedin.com/rest]. 
 
-[[LinkedIn-Endpointprefixcomments]]
-Endpoint prefix _comments_
-++++++++++++++++++++++++++
+#### Endpoint prefix _comments_
 
 The following endpoints can be invoked with the prefix *comments* as
 follows:
@@ -158,9 +150,7 @@ URI Options for _comments_
 |fields |String
 |=======================================================================
 
-[[LinkedIn-Endpointprefixcompanies]]
-Endpoint prefix _companies_
-+++++++++++++++++++++++++++
+#### Endpoint prefix _companies_
 
 The following endpoints can be invoked with the prefix *companies* as
 follows:
@@ -265,9 +255,7 @@ matching endpoints.
 |updatecomment |org.apache.camel.component.linkedin.api.model.UpdateComment
 |=======================================================================
 
-[[LinkedIn-Endpointprefixgroups]]
-Endpoint prefix _groups_
-++++++++++++++++++++++++
+#### Endpoint prefix _groups_
 
 The following endpoints can be invoked with the prefix *groups* as
 follows:
@@ -298,9 +286,7 @@ URI Options for _groups_
 |post |org.apache.camel.component.linkedin.api.model.Post
 |=======================================================================
 
-[[LinkedIn-Endpointprefixjobs]]
-Endpoint prefix _jobs_
-++++++++++++++++++++++
+#### Endpoint prefix _jobs_
 
 The following endpoints can be invoked with the prefix *jobs* as
 follows:
@@ -339,9 +325,7 @@ URI Options for _jobs_
 |partner_job_id |Long
 |=======================================================================
 
-[[LinkedIn-Endpointprefixpeople]]
-Endpoint prefix _people_
-++++++++++++++++++++++++
+#### Endpoint prefix _people_
 
 The following endpoints can be invoked with the prefix *people* as
 follows:
@@ -495,9 +479,7 @@ if other options do not satisfy matching endpoints.
 |updatecomment |org.apache.camel.component.linkedin.api.model.UpdateComment
 |=======================================================================
 
-[[LinkedIn-Endpointprefixposts]]
-Endpoint prefix _posts_
-+++++++++++++++++++++++
+#### Endpoint prefix _posts_
 
 The following endpoints can be invoked with the prefix *posts* as
 follows:
@@ -555,9 +537,7 @@ options do not satisfy matching endpoints.
 |start |Long
 |=======================================================================
 
-[[LinkedIn-Endpointprefixsearch]]
-Endpoint prefix _search_
-++++++++++++++++++++++++
+#### Endpoint prefix _search_
 
 The following endpoints can be invoked with the prefix *search* as
 follows:
@@ -637,9 +617,7 @@ satisfy matching endpoints.
 |title |String
 |=======================================================================
 
-[[LinkedIn-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 
 Any of the producer endpoints can be used as a consumer endpoint.
 Consumer endpoints can
@@ -651,25 +629,19 @@ be executed once for each exchange. To change this behavior use the
 property *consumer.splitResults=true* to return a single exchange for
 the entire list or array. 
 
-[[LinkedIn-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Any URI option can be provided in a message header for producer
 endpoints with a *CamelLinkedIn.* prefix.
 
-[[LinkedIn-Messagebody]]
-Message body
-^^^^^^^^^^^^
+### Message body
 
 All result message bodies utilize objects provided by the Camel LinkedIn
 API SDK, which is built using Apache CXF JAX-RS. Producer endpoints can
 specify the option name for incoming message body in the *inBody*
 endpoint parameter.
 
-[[LinkedIn-Usecases]]
-Use cases
-^^^^^^^^^
+### Use cases
 
 The following route gets user's profile:
 
@@ -697,4 +669,4 @@ The following route uses a producer with dynamic header options. The
         .setHeader("CamelLinkedIn.person_id", header("personId"))
         .to("linkedin://people/connectionsById")
         .to("bean://bar");
------------------------------------------------------------------
+-----------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lucene/src/main/docs/lucene-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lucene/src/main/docs/lucene-component.adoc b/components/camel-lucene/src/main/docs/lucene-component.adoc
index 289186d..4cccec4 100644
--- a/components/camel-lucene/src/main/docs/lucene-component.adoc
+++ b/components/camel-lucene/src/main/docs/lucene-component.adoc
@@ -1,4 +1,4 @@
-# Lucene Component
+## Lucene Component
 
 *Available as of Camel 2.2*
 
@@ -33,9 +33,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Lucene-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------
@@ -46,9 +44,7 @@ lucene:searcherName:query[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Lucene-InsertOptions]]
-Insert Options
-^^^^^^^^^^^^^^
+### Insert Options
 
 
 
@@ -94,13 +90,9 @@ The Lucene component supports 7 endpoint options which are listed below:
 
 
 
-[[Lucene-Sending/ReceivingMessagestoFromthecache]]
-Sending/Receiving Messages to/from the cache
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sending/Receiving Messages to/from the cache
 
-[[Lucene-MessageHeaders]]
-Message Headers
-+++++++++++++++
+#### Message Headers
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -113,9 +105,7 @@ wildcards and phrases
 documentation when returning hit information.
 |=======================================================================
 
-[[Lucene-LuceneProducers]]
-Lucene Producers
-++++++++++++++++
+#### Lucene Producers
 
 This component supports 2 producer endpoints.
 
@@ -129,20 +119,14 @@ property name called 'QUERY'. The value of the header property 'QUERY'
 is a Lucene Query. For more details on how to create Lucene Queries
 check out http://lucene.apache.org/java/3_0_0/queryparsersyntax.html[http://lucene.apache.org/java/3_0_0/queryparsersyntax.html]
 
-[[Lucene-LuceneProcessor]]
-Lucene Processor
-++++++++++++++++
+#### Lucene Processor
 
 There is a processor called LuceneQueryProcessor available to perform
 queries against lucene without the need to create a producer.
 
-[[Lucene-LuceneUsageSamples]]
-Lucene Usage Samples
-^^^^^^^^^^^^^^^^^^^^
+### Lucene Usage Samples
 
-[[Lucene-Example1:CreatingaLuceneindex]]
-Example 1: Creating a Lucene index
-++++++++++++++++++++++++++++++++++
+#### Example 1: Creating a Lucene index
 
 [source,java]
 ------------------------------------------------------------------------------------
@@ -156,9 +140,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 ------------------------------------------------------------------------------------
 
-[[Lucene-Example2:LoadingpropertiesintotheJNDIregistryintheCamelContext]]
-Example 2: Loading properties into the JNDI registry in the Camel Context
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Loading properties into the JNDI registry in the Camel Context
 
 [source,java]
 -----------------------------------------------------------------
@@ -177,9 +159,7 @@ protected JndiRegistry createRegistry() throws Exception {
 CamelContext context = new DefaultCamelContext(createRegistry());
 -----------------------------------------------------------------
 
-[[Lucene-Example2:PerformingsearchesusingaQueryProducer]]
-Example 2: Performing searches using a Query Producer
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 2: Performing searches using a Query Producer
 
 [source,java]
 ----------------------------------------------------------------------------------------------------
@@ -210,9 +190,7 @@ RouteBuilder builder = new RouteBuilder() {
 };
 ----------------------------------------------------------------------------------------------------
 
-[[Lucene-Example3:PerformingsearchesusingaQueryProcessor]]
-Example 3: Performing searches using a Query Processor
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Performing searches using a Query Processor
 
 [source,java]
 -------------------------------------------------------------------------------------------------------
@@ -244,4 +222,4 @@ RouteBuilder builder = new RouteBuilder() {
        }).to("mock:searchResult");
    }
 };
--------------------------------------------------------------------------------------------------------
+-------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
index 3f0ee80..b94c81c 100644
--- a/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
+++ b/components/camel-lumberjack/src/main/docs/lumberjack-component.adoc
@@ -1,4 +1,4 @@
-# Lumberjack Component
+## Lumberjack Component
 
 *Available as of Camel 2.18*
 
@@ -20,9 +20,7 @@ Maven users will need to add the following dependency to their `pom.xml` for thi
 </dependency>
 ------------------------------------------------------------
 
-[[Lumberjack-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------
@@ -33,9 +31,7 @@ lumberjack:host:port
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Lumberjack-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -82,19 +78,13 @@ The Lumberjack component supports 7 endpoint options which are listed below:
 
 
 
-[[Lumberjack-Result]]
-Result
-^^^^^^
+### Result
 
 The result body is a `Map<String, Object>` object.
 
-[[Lumberjack-LumberjackUsageSamples]]
-Lumberjack Usage Samples
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Lumberjack Usage Samples
 
-[[Lumberjack-Example1:]]
-Example 1: Streaming the log messages
-+++++++++++++++++++++++++++++++++++++
+#### Example 1: Streaming the log messages
 
 [source,java]
 ------------------------------------------------------------------------------------
@@ -105,5 +95,4 @@ RouteBuilder builder = new RouteBuilder() {
            to("stream:out");                        // Write it into the output stream
     }
 };
-------------------------------------------------------------------------------------
-
+------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
index b873ceb..00e2fc7 100644
--- a/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
+++ b/components/camel-lzf/src/main/docs/lzf-dataformat.adoc
@@ -1,4 +1,4 @@
-# LZF Deflate Compression DataFormat
+## LZF Deflate Compression DataFormat
 
 The
 LZF https://cwiki.apache.org/confluence/display/CAMEL/Data+Format[Data
@@ -9,9 +9,7 @@ endpoint. The compression capability is quite useful when you deal with
 large XML and Text based payloads or when you read messages previously
 comressed using LZF algotithm.
 
-[[LZFDataFormat-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The LZF Deflate Compression dataformat supports 2 options which are listed below.
@@ -28,9 +26,7 @@ The LZF Deflate Compression dataformat supports 2 options which are listed below
 {% endraw %}
 // dataformat options: END
 
-[[LZFDataFormat-Marshal]]
-Marshal
-^^^^^^^
+### Marshal
 
 In this example we marshal a regular text/XML payload to a compressed
 payload employing LZF compression format and send it an ActiveMQ queue
@@ -41,9 +37,7 @@ called MY_QUEUE.
 from("direct:start").marshal().lzf().to("activemq:queue:MY_QUEUE");
 -------------------------------------------------------------------
 
-[[LZFDataFormat-Unmarshal]]
-Unmarshal
-^^^^^^^^^
+### Unmarshal
 
 In this example we unmarshal a LZF payload from an ActiveMQ queue called
 MY_QUEUE to its original format, and forward it for processing to
@@ -54,9 +48,7 @@ the `UnGZippedMessageProcessor`.
 from("activemq:queue:MY_QUEUE").unmarshal().lzf().process(new UnCompressedMessageProcessor());
 ----------------------------------------------------------------------------------------------
 
-[[LZFDataFormat-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To useLZF compression in your camel routes you need to add a dependency
 on *camel-lzf* which implements this data format.
@@ -74,4 +66,4 @@ download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[08/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-http4/src/main/docs/http4-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-http4/src/main/docs/http4-component.adoc b/components/camel-http4/src/main/docs/http4-component.adoc
index 8e3076b..318b596 100644
--- a/components/camel-http4/src/main/docs/http4-component.adoc
+++ b/components/camel-http4/src/main/docs/http4-component.adoc
@@ -1,4 +1,4 @@
-# HTTP4 Component
+## HTTP4 Component
 
 *Available as of Camel 2.3*
 
@@ -26,9 +26,7 @@ Camel-http4 uses http://hc.apache.org/httpcomponents-client-ga/[Apache
 HttpClient 4.x] while camel-http uses
 http://hc.apache.org/httpclient-3.x/[Apache HttpClient 3.x].
 
-[[HTTP4-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------------
@@ -47,9 +45,7 @@ Therefore it should never be used as input into your Camel Routes. To
 bind/expose an HTTP endpoint via a HTTP server as input to a Camel
 route, use the link:jetty.html[Jetty Component] instead.
 
-[[HTTP4-HttpOptions]]
-Http4 Component Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Http4 Component Options
 
 
 
@@ -138,9 +134,7 @@ The HTTP4 component supports 32 endpoint options which are listed below:
 
 
 
-[[HTTP4-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,20%,70%",options="header",]
 |=======================================================================
@@ -171,9 +165,7 @@ a content type, such as `text/html`.
 provide a content encoding, such as `gzip`.
 |=======================================================================
 
-[[HTTP4-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 Camel will store the HTTP response from the external server on the OUT
 body. All headers from the IN message will be copied to the OUT message,
@@ -183,9 +175,7 @@ HTTP response headers as well to the OUT message headers.
 Â 
 
 
-[[HTTP4-UsingSystemProperties]]
-Using System Properties
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using System Properties
 
 When setting useSystemProperties to true, the HTTP Client will look for
 the following System Properties and it will use it:
@@ -207,9 +197,7 @@ the following System Properties and it will use it:
 * http.keepAlive
 * http.maxConnections
 
-[[HTTP4-Responsecode]]
-Response code
-^^^^^^^^^^^^^
+### Response code
 
 Camel will handle according to the HTTP response code:
 
@@ -227,9 +215,7 @@ the `HttpOperationFailedException` from being thrown for failed response
 codes. This allows you to get any response from the remote server. +
 There is a sample below demonstrating this.
 
-[[HTTP4-HttpOperationFailedException]]
-HttpOperationFailedException
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HttpOperationFailedException
 
 This exception contains the following information:
 
@@ -239,9 +225,7 @@ This exception contains the following information:
 * Response body as a `java.lang.String`, if server provided a body as
 response
 
-[[HTTP4-CallingusingGETorPOST]]
-Calling using GET or POST
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Calling using GET or POST
 
 The following algorithm is used to determine whether the `GET` or `POST`
 HTTP method should be used: +
@@ -251,9 +235,7 @@ HTTP method should be used: +
  4. `POST` if there is data to send (body is not null). +
  5. `GET` otherwise.
 
-[[HTTP4-HowtogetaccesstoHttpServletRequestandHttpServletResponse]]
-How to get access to HttpServletRequest and HttpServletResponse
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get access to HttpServletRequest and HttpServletResponse
 
 You can get access to these two using the Camel type converter system
 using +
@@ -266,9 +248,7 @@ HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
 HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
 ----------------------------------------------------------------------------------
 
-[[HTTP4-ConfiguringURItocall]]
-Configuring URI to call
-^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI to call
 
 You can set the HTTP producer's URI directly form the endpoint URI. In
 the route below, Camel will call out to the external server, `oldhost`,
@@ -307,9 +287,7 @@ endpoint is configured with http4://oldhost. +
 If the http4 endpoint is working in bridge mode, it will ignore the
 message header of `Exchange.HTTP_URI`.
 
-[[HTTP4-ConfiguringURIParameters]]
-Configuring URI Parameters
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring URI Parameters
 
 The *http* producer supports URI parameters to be sent to the HTTP
 server. The URI parameters can either be set directly on the endpoint
@@ -330,9 +308,7 @@ from("direct:start")
   .to("http4://oldhost");
 ---------------------------------------------------------------------
 
-[[HTTP4-HowtosetthehttpmethodtotheHTTPproducer]]
-How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to set the http method (GET/PATCH/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer
 
 *Using the http PATCH method*
 
@@ -372,9 +348,7 @@ And the equivalent Spring sample:
 </camelContext>
 ---------------------------------------------------------------------
 
-[[HTTP4-Usingclienttimeout-SO_TIMEOUT]]
-Using client timeout - SO_TIMEOUT
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using client timeout - SO_TIMEOUT
 
 See the
 https://svn.apache.org/repos/asf/camel/trunk/components/camel-http4/src/test/java/org/apache/camel/component/http4/HttpSOTimeoutTest.java[HttpSOTimeoutTest]
@@ -384,9 +358,7 @@ unit test.
 https://github.com/apache/camel/blob/master/components/camel-http4/src/test/java/org/apache/camel/component/http4/HttpSOTimeoutTest.java[HttpSOTimeoutTest]
 unit test.
 
-[[HTTP4-ConfiguringaProxy]]
-Configuring a Proxy
-^^^^^^^^^^^^^^^^^^^
+### Configuring a Proxy
 
 The HTTP4 component provides a way to configure a proxy.
 
@@ -399,9 +371,7 @@ from("direct:start")
 There is also support for proxy authentication via the
 `proxyAuthUsername` and `proxyAuthPassword` options.
 
-[[HTTP4-UsingproxysettingsoutsideofURI]]
-Using proxy settings outside of URI
-+++++++++++++++++++++++++++++++++++
+#### Using proxy settings outside of URI
 
 To avoid System properties conflicts, you can set proxy configuration
 only from the CamelContext or URI. +
@@ -432,9 +402,7 @@ Properties and then the endpoint proxy options if provided. +
 Notice in *Camel 2.8* there is also a `http.proxyScheme` property you
 can set to explicit configure the scheme to use.
 
-[[HTTP4-Configuringcharset]]
-Configuring charset
-^^^^^^^^^^^^^^^^^^^
+### Configuring charset
 
 If you are using `POST` to send data you can configure the `charset`
 using the `Exchange` property:
@@ -444,9 +412,7 @@ using the `Exchange` property:
 exchange.setProperty(Exchange.CHARSET_NAME, "ISO-8859-1");
 ----------------------------------------------------------
 
-[[HTTP4-Samplewithscheduledpoll]]
-Sample with scheduled poll
-++++++++++++++++++++++++++
+#### Sample with scheduled poll
 
 This sample polls the Google homepage every 10 seconds and write the
 page to the file `message.html`:
@@ -459,9 +425,7 @@ from("timer://foo?fixedRate=true&delay=0&period=10000")
   .to("file:target/google");
 ------------------------------------------------------------
 
-[[HTTP4-URIParametersfromtheendpointURI]]
-URI Parameters from the endpoint URI
-++++++++++++++++++++++++++++++++++++
+#### URI Parameters from the endpoint URI
 
 In this sample we have the complete URI endpoint that is just what you
 would have typed in a web browser. Multiple URI parameters can of course
@@ -474,9 +438,7 @@ web browser. Camel does no tricks here.
 template.sendBody("http4://www.google.com/search?q=Camel", null);
 -----------------------------------------------------------------
 
-[[HTTP4-URIParametersfromtheMessage]]
-URI Parameters from the Message
-+++++++++++++++++++++++++++++++
+#### URI Parameters from the Message
 
 [source,java]
 ------------------------------------------------------------------
@@ -489,9 +451,7 @@ template.sendBody("http4://www.google.com/search", null, headers);
 In the header value above notice that it should *not* be prefixed with
 `?` and you can separate parameters as usual with the `&` char.
 
-[[HTTP4-GettingtheResponseCode]]
-Getting the Response Code
-+++++++++++++++++++++++++
+#### Getting the Response Code
 
 You can get the HTTP response code from the HTTP4 component by getting
 the value from the Out message header with
@@ -508,25 +468,19 @@ Message out = exchange.getOut();
 int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
 ------------------------------------------------------------------------------------
 
-[[HTTP4-DisablingCookies]]
-Disabling Cookies
-^^^^^^^^^^^^^^^^^
+### Disabling Cookies
 
 To disable cookies you can set the HTTP Client to ignore cookies by
 adding this URI option: +
  `httpClient.cookiePolicy=ignoreCookies`
 
-[[HTTP4-AdvancedUsage]]
-Advanced Usage
-^^^^^^^^^^^^^^
+### Advanced Usage
 
 If you need more control over the HTTP producer you should use the
 `HttpComponent` where you can set various classes to give you custom
 behavior.
 
-[[HTTP4-SettingupSSLforHTTPClient]]
-Setting up SSL for HTTP Client
-++++++++++++++++++++++++++++++
+#### Setting up SSL for HTTP Client
 
 [[HTTP4-UsingtheJSSEConfigurationUtility]]
 Using the JSSE Configuration Utility
@@ -696,4 +650,4 @@ property.
    <property name="sslContextParameters" ref="sslContextParams2"/>
    <property name="x509HostnameVerifier" ref="hostnameVerifier"/>
 </bean>
-----------------------------------------------------------------------------
+----------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ibatis/src/main/docs/ibatis-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ibatis/src/main/docs/ibatis-component.adoc b/components/camel-ibatis/src/main/docs/ibatis-component.adoc
index 0203cc2..ddedce8 100644
--- a/components/camel-ibatis/src/main/docs/ibatis-component.adoc
+++ b/components/camel-ibatis/src/main/docs/ibatis-component.adoc
@@ -1,4 +1,4 @@
-# iBatis Component
+## iBatis Component
 
 The *ibatis:* component allows you to query, poll, insert, update and
 delete data in a relational database using
@@ -27,9 +27,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[iBATIS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------
@@ -50,9 +48,7 @@ the root of the classpath and expected named as `SqlMapConfig.xml`. +
  In Camel 2.2 you can configure this on the iBatisComponent with the
 `setSqlMapConfig(String)` method.
 
-[[iBATIS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -123,9 +119,7 @@ The iBatis component supports 28 endpoint options which are listed below:
 
 
 
-[[iBATIS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel will populate the result message, either IN or OUT with a header
 with the operationName used:
@@ -141,9 +135,7 @@ instance an `INSERT` could return the auto-generated key, or number of
 rows etc.
 |=======================================================================
 
-[[iBATIS-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 The response from iBatis will only be set as body if it's a `SELECT`
 statement. That means, for example, for `INSERT` statements Camel will
@@ -151,9 +143,7 @@ not replace the body. This allows you to continue routing and keep the
 original body. The response from iBatis is always stored in the header
 with the key `CamelIBatisResult`.
 
-[[iBATIS-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 For example if you wish to consume beans from a JMS queue and insert
 them into a database you could do the following:
@@ -185,9 +175,7 @@ Where *insertAccount* is the iBatis ID in the SQL map file:
   </insert>
 ------------------------------------------------------------
 
-[[iBATIS-UsingStatementTypeforbettercontrolofIBatis]]
-Using StatementType for better control of IBatis
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using StatementType for better control of IBatis
 
 When routing to an iBatis endpoint you want more fine grained control so
 you can control whether the SQL statement to be executed is a `SELEECT`,
@@ -205,9 +193,7 @@ We can do the same for some of the other operations, such as
 And the same for `UPDATE`, where we can send an `Account` object as IN
 body to iBatis:
 
-[[iBATIS-Scheduledpollingexample]]
-Scheduled polling example
-+++++++++++++++++++++++++
+#### Scheduled polling example
 
 Since this component does not support scheduled polling, you need to use
 another mechanism for triggering the scheduled polls, such as the
@@ -231,9 +217,7 @@ And the iBatis SQL map file used:
   </select>
 ----------------------------------------------------------------------------
 
-[[iBATIS-UsingonConsume]]
-Using onConsume
-+++++++++++++++
+#### Using onConsume
 
 This component supports executing statements *after* data have been
 consumed and processed by Camel. This allows you to do post updates in
@@ -247,14 +231,11 @@ database to processed, so we avoid consuming it twice or more.
 
 And the statements in the sqlmap file:
 
-[[iBATIS-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:mybatis.html[MyBatis]
-
+* link:mybatis.html[MyBatis]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ical/src/main/docs/ical-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ical/src/main/docs/ical-dataformat.adoc b/components/camel-ical/src/main/docs/ical-dataformat.adoc
index 39128d5..ceb68c8 100644
--- a/components/camel-ical/src/main/docs/ical-dataformat.adoc
+++ b/components/camel-ical/src/main/docs/ical-dataformat.adoc
@@ -1,4 +1,4 @@
-# iCal DataFormat
+## iCal DataFormat
 
 *Available as of Camel 2.11.1*
 
@@ -26,9 +26,7 @@ END:VEVENT
 END:VCALENDAR
 ----------------------------------------------------------------------
 
-[[ICal-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The iCal dataformat supports 2 options which are listed below.
@@ -45,9 +43,7 @@ The iCal dataformat supports 2 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[ICal-BasicUsage]]
-Basic Usage
-^^^^^^^^^^^
+### Basic Usage
 
 To unmarshal and marshal the message shown above, your route will look
 like the following:
@@ -74,12 +70,9 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[ICal-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-infinispan/src/main/docs/infinispan-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-infinispan/src/main/docs/infinispan-component.adoc b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
index bb014c1..6031c7d 100644
--- a/components/camel-infinispan/src/main/docs/infinispan-component.adoc
+++ b/components/camel-infinispan/src/main/docs/infinispan-component.adoc
@@ -1,4 +1,4 @@
-# Infinispan Component
+## Infinispan Component
 
 *Available as of Camel 2.13.0*
 
@@ -22,18 +22,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Infinispan-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
 infinispan://hostName?[options]
 -------------------------------
 
-[[Infinispan-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 The producer allows sending messages to a local infinispan cache
 configured in the registry, or to a remote cache using the HotRod
@@ -76,9 +72,7 @@ The Infinispan component supports 15 endpoint options which are listed below:
 
 
 
-[[Infinispan-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,10%,10%,60%",options="header",]
 |=======================================================================
@@ -123,9 +117,7 @@ present the command defaults to InifinispanConfiguration's one
 operation returning something is ignored by the client application
 |=======================================================================
 
-[[Infinispan-Example]]
-Example
-^^^^^^^
+### Example
 
 Below is an example route that retrieves a value from the cache for a
 specific key:
@@ -138,9 +130,7 @@ from("direct:start")
         .to("infinispan://localhost?cacheContainer=#cacheContainer");
 ------------------------------------------------------------------------------------
 
-[[Infinispan-UsingtheInfinispanbasedidempotentrepository]]
-Using the Infinispan based idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Infinispan based idempotent repository
 
 In this section we will use the Infinispan based idempotent repository.
 
@@ -178,12 +168,9 @@ XML file as well:
 
 For more information, see these resources...
 
-[[Infinispan-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-influxdb/src/main/docs/influxdb-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-influxdb/src/main/docs/influxdb-component.adoc b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
index d171c5f..e8a7689 100644
--- a/components/camel-influxdb/src/main/docs/influxdb-component.adoc
+++ b/components/camel-influxdb/src/main/docs/influxdb-component.adoc
@@ -1,4 +1,4 @@
-# InfluxDB Component
+## InfluxDB Component
 
 *Available as of Camel 2.18.0*
 
@@ -26,18 +26,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[InfluxDb-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
 influxdb://beanName?[options]
 -------------------------------
 
-[[InfluxDb-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 The producer allows sending messages to a influxdb
 configured in the registry, using the native java driver.
@@ -72,9 +68,7 @@ The InfluxDB component supports 7 endpoint options which are listed below:
 
 
 
-[[InfluxDb-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,10%,10%,60%",options="header",]
 |=======================================================================
@@ -83,9 +77,7 @@ Message Headers
 
 |=======================================================================
 
-[[InfluxDb-Example]]
-Example
-^^^^^^^
+### Example
 
 
 Below is an example route that stores a point into the db (taking the db name from the URI)
@@ -106,12 +98,9 @@ from("direct:start")
 
 For more information, see these resources...
 
-[[InfluxDb-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-irc/src/main/docs/irc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-irc/src/main/docs/irc-component.adoc b/components/camel-irc/src/main/docs/irc-component.adoc
index 2ae82e3..af4a499 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -1,4 +1,4 @@
-# IRC Component
+## IRC Component
 
 The *irc* component implements an
 http://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] (Internet Relay
@@ -17,9 +17,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[IRC-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------------------------------------
@@ -30,9 +28,7 @@ irc:nick@host[:port]?channels=#channel1,#channel2,#channel3[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[IRC-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -87,13 +83,9 @@ The IRC component supports 26 endpoint options which are listed below:
 
 
 
-[[IRC-SSLSupport]]
-SSL Support
-^^^^^^^^^^^
+### SSL Support
 
-[[IRC-UsingtheJSSEConfigurationUtility]]
-Using the JSSE Configuration Utility
-++++++++++++++++++++++++++++++++++++
+#### Using the JSSE Configuration Utility
 
 As of Camel 2.9, the IRC component supports SSL/TLS configuration
 through the link:camel-configuration-utilities.html[Camel JSSE
@@ -144,9 +136,7 @@ Spring DSL based configuration of endpoint
   <to uri="ircs://camel-prd-user@server:6669/#camel-test?nickname=camel-prd&password=password&sslContextParameters=#sslContextParameters"/>...
 ----------------------------------------------------------------------------------------------------------------------------------------------
 
-[[IRC-Usingthelegacybasicconfigurationoptions]]
-Using the legacy basic configuration options
-++++++++++++++++++++++++++++++++++++++++++++
+#### Using the legacy basic configuration options
 
 You can also connect to an SSL enabled IRC server, as follows:
 
@@ -165,9 +155,7 @@ If you need to provide your own custom trust manager, use the
 ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTrustManagerBean
 ----------------------------------------------------------------------------------------------
 
-[[IRC-Usingkeys]]
-Using keys
-^^^^^^^^^^
+### Using keys
 
 *Available as of Camel 2.2*
 
@@ -181,8 +169,7 @@ For example we join 3 channels where as only channel 1 and 3 uses a key.
 irc:[hidden email]?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
 -----------------------------------------------------------------------------
 
-Getting a list of users of the channel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Getting a list of users of the channel
 
 Using the `namesOnJoin` option one can invoke the IRC-`NAMES` command after the component has joined a channel.
 The server will reply with `irc.num = 353`. So in order to process the result the property `onReply` has to be `true`.
@@ -199,12 +186,9 @@ from("ircs:nick@myserver:1234/#mychannelname?listOnJoin=true&onReply=true")
  .to("mock:result").stop();
 -----------------------------------------------------------------------------
 
-[[IRC-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-ironmq/src/main/docs/ironmq-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-ironmq/src/main/docs/ironmq-component.adoc b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
index 088c78b..18032c0 100644
--- a/components/camel-ironmq/src/main/docs/ironmq-component.adoc
+++ b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
@@ -1,4 +1,4 @@
-# ironmq Component
+## ironmq Component
 
 *Available as of Camel 2.17*
 
@@ -23,9 +23,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[IronMQ-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -33,9 +31,7 @@ URI format
 -----------------------------
 Where **queueName** identifies the IronMQ queue you want to publish or consume messages from.
 
-[[IronMQ-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -90,9 +86,7 @@ The ironmq component supports 31 endpoint options which are listed below:
 
 
 
-[[IronMQ-IronMQComponentOptions]]
-IronMQComponent Options
-^^^^^^^^^^^^^^^^^^^^^^^
+### IronMQComponent Options
 
 
 
@@ -105,14 +99,10 @@ The ironmq component has no options.
 
 
 
-[[IronMQ-Messagebody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 Should be either a String or a array of Strings. In the latter case the batch of strings will be send to IronMQ as one request, creating one message pr. element in the array.
 
-[[IronMQ-MessageHeaders]]
-Producer message headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Producer message headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -121,8 +111,7 @@ Producer message headers
 |CamelIronMQMessageId |String or io.iron.ironmq.Ids|The id of the IronMQ message as a String when sending a single message, or a Ids object when sending a array of strings.
 |=======================================================================
 
-Consumer message headers
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Consumer message headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -133,8 +122,7 @@ Consumer message headers
 |=======================================================================
 
 
-Consumer example
-^^^^^^^^^^^^^^^^
+### Consumer example
 
 Consume 50 messages pr. poll from the queue 'testqueue' on aws eu, and save the messages to files.
 
@@ -144,12 +132,11 @@ from("ironmq:testqueue?ironMQCloud=https://mq-aws-eu-west-1-1.iron.io&projectId=
   .to("file:somefolder");
 --------------------------------------------------
 
-Producer example
-^^^^^^^^^^^^^^^^
+### Producer example
 Dequeue from activemq jms and enqueue the messages on IronMQ.
 
 [source,java]
 --------------------------------------------------
 from("activemq:foo")
   .to("ironmq:testqueue?projectId=myIronMQProjectid&token=myIronMQToken");
---------------------------------------------------
+--------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc b/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
index 5f9980d..5bdfa56 100644
--- a/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
+++ b/components/camel-jackson/src/main/docs/json-jackson-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon Jackson DataFormat
+## JSon Jackson DataFormat
 
 *Available as of Camel 2.18*
 
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[Jackson-Options]]
-Jackson Options
-^^^^^^^^^^^^^^^
+### Jackson Options
 
 
 
@@ -50,9 +48,7 @@ The JSon Jackson dataformat supports 17 options which are listed below.
 
 
 
-[[Jackson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Jackson in your camel routes you need to add the dependency
 on *camel-jackson* which implements this data format.
@@ -69,4 +65,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc b/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
index 45c89d5..874aa46 100644
--- a/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
+++ b/components/camel-jacksonxml/src/main/docs/jacksonxml-dataformat.adoc
@@ -1,4 +1,4 @@
-# JacksonXML DataFormat
+## JacksonXML DataFormat
 
 *Available as of Camel 2.16*
 
@@ -27,9 +27,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[JacksonXML-Options]]
-JacksonXML Options
-^^^^^^^^^^^^^^^^^^
+### JacksonXML Options
 
 
 
@@ -62,9 +60,7 @@ The JacksonXML dataformat supports 15 options which are listed below.
 // dataformat options: END
 
 
-[[JacksonXML-UsingJacksonXMLinSpringDSL]]
-Using Jackson XML in Spring DSL
-+++++++++++++++++++++++++++++++
+#### Using Jackson XML in Spring DSL
 
 When using link:data-format.html[Data Format] in Spring DSL you need to
 declare the data formats first. This is done in the *DataFormats* XML
@@ -90,9 +86,7 @@ And then you can refer to this id in the route:
         </route>
 -------------------------------------
 
-[[JacksonXML-ExcludingPOJOfieldsfrommarshalling]]
-Excluding POJO fields from marshalling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Excluding POJO fields from marshalling
 
 When marshalling a POJO to XML you might want to exclude certain fields
 from the XML output. With Jackson you can
@@ -112,9 +106,7 @@ Note that the weight field is missing in the resulting XML:
 <pojo age="30" weight="70"/>
 ----------------------------
 
-[[JacksonXML-Include/ExcludefieldsusingthejsonViewattributewithJacksonXMLDataFormat]]
-Include/Exclude fields using the `jsonView` attribute with `JacksonXML`DataFormat
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Include/Exclude fields using the `jsonView` attribute with `JacksonXML`DataFormat
 
 As an example of using this attribute you can instead of:
 
@@ -144,9 +136,7 @@ And the same in XML DSL:
   </marshal>
 ---------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[JacksonXML-Settingserializationincludeoption]]
-Setting serialization include option
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Setting serialization include option
 
 If you want to marshal a pojo to XML, and the pojo has some fields with
 null values. And you want to skip these null values, then you need to
@@ -179,9 +169,7 @@ Or from XML DSL you configure this as
     </dataFormats>
 ------------------------------------------------------
 
-[[JacksonXML-UnmarshallingfromXMLtoPOJOwithdynamicclassname]]
-Unmarshalling from XML to POJO with dynamic class name
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling from XML to POJO with dynamic class name
 
 If you use jackson to unmarshal XML to POJO, then you can now specify a
 header in the message that indicate which class name to unmarshal to. +
@@ -208,9 +196,7 @@ Or from XML DSL you configure this as
     </dataFormats>
 -------------------------------------------------------
 
-[[JacksonXML-UnmarshallingfromXMLtoListMaporListPojo]]
-Unmarshalling from XML to List<Map> or List<pojo>
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Unmarshalling from XML to List<Map> or List<pojo>
 
 If you are using Jackson to unmarshal XML to a list of map/pojo, you can
 now specify this by setting `useList="true"` or use
@@ -246,9 +232,7 @@ And you can specify the pojo type also
     </dataFormats>
 -------------------------------------------------------------------------------
 
-[[JacksonXML-UsingcustomJacksonmodules]]
-Using custom Jackson modules
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using custom Jackson modules
 
 You can use custom Jackson modules by specifying the class names of
 those using the moduleClassNames option as shown below.
@@ -280,9 +264,7 @@ to the module as shown below:
 Â Multiple modules can be specified separated by comma, such as
 moduleRefs="myJacksonModule,myOtherModule"
 
-[[JacksonXML-EnablingordisablefeaturesusingJackson]]
-Enabling or disable features using Jackson
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Enabling or disable features using Jackson
 
 Jackson has a number of features you can enable or disable, which its
 ObjectMapper uses. For example to disable failing on unknown properties
@@ -315,9 +297,7 @@ df.disableFeature(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES);
 df.disableFeature(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES);
 ----------------------------------------------------------------------
 
-[[JacksonXML-ConvertingMapstoPOJOusingJackson]]
-Converting Maps to POJO using Jackson
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Converting Maps to POJO using Jackson
 
 Jackson `ObjectMapper` can be used to convert maps to POJO objects.
 Jackson component comes with the data converter that can be used to
@@ -338,9 +318,7 @@ If there is a single `ObjectMapper` instance available in the Camel
 registry, it will used by the converter to perform the conversion.
 Otherwise the default mapper will be used.  
 
-[[JacksonXML-FormattedXMLmarshallingpretty-printing]]
-Formatted XML marshalling (pretty-printing)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Formatted XML marshalling (pretty-printing)
 
 Using the `prettyPrint` option one can output a well formatted XML while
 marshalling:
@@ -363,9 +341,7 @@ Please note that there are 5 different overloaded `jacksonxml()` DSL
 methods which support the `prettyPrint` option in combination with other
 settings for `unmarshalType`, `jsonView` etc. 
 
-[[JacksonXML-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Jackson XML in your camel routes you need to add the dependency
 on *camel-jacksonxml* which implements this data format.
@@ -382,4 +358,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-javaspace/src/main/docs/javaspace-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-javaspace/src/main/docs/javaspace-component.adoc b/components/camel-javaspace/src/main/docs/javaspace-component.adoc
index ffe4cf5..141e93b 100644
--- a/components/camel-javaspace/src/main/docs/javaspace-component.adoc
+++ b/components/camel-javaspace/src/main/docs/javaspace-component.adoc
@@ -1,4 +1,4 @@
-# JavaSpace Component
+## JavaSpace Component
 
 *Available as of Camel 2.1*
 
@@ -34,9 +34,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[JavaSpace-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------
@@ -46,9 +44,7 @@ javaspace:jini://host[?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[JavaSpace-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -82,13 +78,9 @@ The JavaSpace component supports 11 endpoint options which are listed below:
 
 
 
-[[JavaSpace-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[JavaSpace-SendingandReceivingEntries]]
-Sending and Receiving Entries
-+++++++++++++++++++++++++++++
+#### Sending and Receiving Entries
 
 [source,java]
 --------------------------------------------------------------------------------------------------------
@@ -104,9 +96,7 @@ from("javaspace:jini://localhost?spaceName=mySpace&templateId=template&verb=take
 In this case the payload can be any object that inherits from the Jini
 `Entry` type.
 
-[[JavaSpace-Sendingandreceivingserializableobjects]]
-Sending and receiving serializable objects
-++++++++++++++++++++++++++++++++++++++++++
+#### Sending and receiving serializable objects
 
 Using the preceding routes, it is also possible to send and receive any
 serializable object. The JavaSpace component detects that the payload is
@@ -114,9 +104,7 @@ not a Jini `Entry` and then it automatically wraps the payload with a
 Camel Jini `Entry`. In this way, a JavaSpace can be used as a generic
 transport mechanism.
 
-[[JavaSpace-UsingJavaSpaceasaremoteinvocationtransport]]
-Using JavaSpace as a remote invocation transport
-++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using JavaSpace as a remote invocation transport
 
 The JavaSpace component has been tailored to work in combination with
 the Camel bean component. It is therefore possible to call a remote POJO
@@ -138,12 +126,9 @@ realize the master/worker pattern. The idea is to use the POJO to
 provide the business logic and rely on Camel for sending/receiving
 requests/replies with the proper correlation.
 
-[[JavaSpace-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
index ccbd16f..05b260b 100644
--- a/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
+++ b/components/camel-jaxb/src/main/docs/jaxb-dataformat.adoc
@@ -1,13 +1,11 @@
-# JAXB DataFormat
+## JAXB DataFormat
 
 JAXB is a link:data-format.html[Data Format] which uses the JAXB2 XML
 marshalling standard which is included in Java 6 to unmarshal an XML
 payload into Java objects or to marshal Java objects into an XML
 payload.
 
-[[JAXB-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The JAXB dataformat supports 17 options which are listed below.
@@ -39,9 +37,7 @@ The JAXB dataformat supports 17 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[JAXB-UsingtheJavaDSL]]
-Using the Java DSL
-^^^^^^^^^^^^^^^^^^
+### Using the Java DSL
 
 For example the following uses a named DataFormat of _jaxb_ which is
 configured with a number of Java package names to initialize the
@@ -67,9 +63,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[JAXB-UsingSpringXML]]
-Using Spring XML
-^^^^^^^^^^^^^^^^
+### Using Spring XML
 
 The following example shows how to use JAXB to unmarshal using
 link:spring.html[Spring] configuring the jaxb data type
@@ -84,9 +78,7 @@ You can specify context path using `:` as separator, for example
 `com.mycompany:com.mycompany2`. Note that this is handled by JAXB
 implementation and might change if you use different vendor than RI.
 
-[[JAXB-Partialmarshalling/unmarshalling]]
-Partial marshalling/unmarshalling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Partial marshalling/unmarshalling
 
 *This feature is new to Camel 2.2.0.* +
  JAXB 2 supports marshalling and unmarshalling XML tree fragments. By
@@ -101,9 +93,7 @@ to JAXB's unmarshaler.
 For marshalling you have to add `partNamespace` attribute with QName of
 destination namespace. Example of Spring DSL you can find above.
 
-[[JAXB-Fragment]]
-Fragment
-^^^^^^^^
+### Fragment
 
 *This feature is new to Camel 2.8.0.* +
  JaxbDataFormat has new property fragment which can set the the
@@ -112,9 +102,7 @@ you don't want the JAXB Marshaller to generate the XML declaration, you
 can set this option to be true. The default value of this property is
 false.
 
-[[JAXB-IgnoringtheNonXMLCharacter]]
-Ignoring the NonXML Character
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Ignoring the NonXML Character
 
 *This feature is new to Camel 2.2.0.* +
  JaxbDataFromat supports to ignore the
@@ -159,9 +147,7 @@ Camel's NonXML filtering:
 <jaxb filterNonXmlChars="true"  contextPath="org.apache.camel.foo.bar" xmlStreamWriterWrapper="#testXmlStreamWriterWrapper" />
 ------------------------------------------------------------------------------------------------------------------------------
 
-[[JAXB-WorkingwiththeObjectFactory]]
-Working with the ObjectFactory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Working with the ObjectFactory
 
 If you use XJC to create the java class from the schema, you will get an
 ObjectFactory for you JAXB context. Since the ObjectFactory uses
@@ -174,9 +160,7 @@ unmarshaled message body.  +
 body, you need to set the JaxbDataFormat object's ignoreJAXBElement
 property to be false.
 
-[[JAXB-Settingencoding]]
-Setting encoding
-^^^^^^^^^^^^^^^^
+### Setting encoding
 
 You can set the *encoding* option to use when marshalling. Its the
 `Marshaller.JAXB_ENCODING` encoding property on the JAXB Marshaller. +
@@ -187,9 +171,7 @@ property will overrule the encoding set on the JAXB data format.
 
 In this Spring DSL we have defined to use `iso-8859-1` as the encoding:
 
-[[JAXB-Controllingnamespaceprefixmapping]]
-Controlling namespace prefix mapping
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling namespace prefix mapping
 
 *Available as of Camel 2.11*
 
@@ -227,9 +209,7 @@ with the id "myMap", which was what we defined above.
   </marshal>
 ----------------------------------------------------------------------------------------
 
-[[JAXB-Schemavalidation]]
-Schema validation
-^^^^^^^^^^^^^^^^^
+### Schema validation
 
 *Available as of Camel 2.11*
 
@@ -276,9 +256,7 @@ JaxbDataFormat jaxbDataFormat = new JaxbDataFormat();
 jaxbDataFormat.setSchemaFactory(thradSafeSchemaFactory);
 --------------------------------------------------------
 
-[[JAXB-SchemaLocation]]
-Schema Location
-^^^^^^^^^^^^^^^
+### Schema Location
 
 *Available as of Camel 2.14*
 
@@ -303,9 +281,7 @@ You can do the same using the XML DSL:
 </marshal>
 --------------------------------------------------------
 
-[[JAXB-MarshaldatathatisalreadyXML]]
-Marshal data that is already XML
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Marshal data that is already XML
 
 *Available as of Camel 2.14.1*
 
@@ -318,9 +294,7 @@ the JAXB marshaller only attempts to marshal JAXBElements
 (javax.xml.bind.JAXBIntrospector#isElement returns true). And in those
 situations the marshaller fallbacks to marshal the message body as-is.
 
-[[JAXB-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use JAXB in your camel routes you need to add the a dependency on
 *camel-jaxb* which implements this data format.
@@ -336,4 +310,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-jaxb</artifactId>
   <version>x.x.x</version>
 </dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jbpm/src/main/docs/jbpm-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jbpm/src/main/docs/jbpm-component.adoc b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
index e4554ff..3100600 100644
--- a/components/camel-jbpm/src/main/docs/jbpm-component.adoc
+++ b/components/camel-jbpm/src/main/docs/jbpm-component.adoc
@@ -1,4 +1,4 @@
-# JBPM Component
+## JBPM Component
 
 *Available as of Camel 2.16*
 
@@ -19,18 +19,14 @@ for this component:
 </dependency>
 ------------------------------------------------------------------------------------
 
-[[jBPM-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------------
 jbpm::hostName[:port][/resourceUri][?options]
 ---------------------------------------------
 
-[[jBPM-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 // component options: START
@@ -81,9 +77,7 @@ The JBPM component supports 26 endpoint options which are listed below:
 
 
 
-[[jBPM-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -131,9 +125,7 @@ org.infinispan.notifications.cachelistener.event.Event.Type
 |CamelJBPMStatusList |null |List<Status> |The list of status to use when filtering tasks
 |=======================================================================
 
-[[jBPM-Example]]
-Example
-^^^^^^^
+### Example
 
 Below is an example route that starts a business process with id
 project1.integration-test and deploymentId
@@ -147,13 +139,11 @@ from("direct:start")
 Â + "&deploymentId=org.kie.example:project1:1.0.0-SNAPSHOT");
 ----------------------------------------------------------------------------------------------
 
-[[jBPM-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
- 
+ 
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jcache/src/main/docs/jcache-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jcache/src/main/docs/jcache-component.adoc b/components/camel-jcache/src/main/docs/jcache-component.adoc
index e7c737a..bae1e38 100644
--- a/components/camel-jcache/src/main/docs/jcache-component.adoc
+++ b/components/camel-jcache/src/main/docs/jcache-component.adoc
@@ -1,4 +1,4 @@
-# JCache Component
+## JCache Component
 
 
 
@@ -48,6 +48,4 @@ The JCache component supports 23 endpoint options which are listed below:
 
 // component options: START
 The JCache component has no options.
-// component options: END
-
-
+// component options: END
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jclouds/src/main/docs/jclouds-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jclouds/src/main/docs/jclouds-component.adoc b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
index 81e67b7..6515e92 100644
--- a/components/camel-jclouds/src/main/docs/jclouds-component.adoc
+++ b/components/camel-jclouds/src/main/docs/jclouds-component.adoc
@@ -1,4 +1,4 @@
-# JClouds Component
+## JClouds Component
 
 *Available as of Camel 2.9*
 
@@ -33,9 +33,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[jclouds-Configuringthecomponent]]
-Configuring the component
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the component
 
 The camel jclouds component will make use of multiple jclouds blobstores
 and compute services as long as they are passed to the component during
@@ -84,9 +82,7 @@ As you can see the component is capable of handling multiple blobstores
 and compute services. The actual implementation that will be used by
 each endpoint is specified by passing the provider inside the URI.
 
-[[jclouds-Options]]
-Jclouds Options
-^^^^^^^^^^^^^^^
+### Jclouds Options
 
 [source,java]
 -----------------------------------------
@@ -100,9 +96,7 @@ target service (_e.g. aws-s3 or aws_ec2_).
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[jclouds-BlobstoreURIOptions]]
-Blobstore URI Options
-^^^^^^^^^^^^^^^^^^^^^
+### Blobstore URI Options
 
 
 
@@ -167,9 +161,7 @@ jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobNam
 For producer endpoint you can override all of the above URI options by
 passing the appropriate headers to the message.
 
-[[jclouds-MessageHeadersforblobstore]]
-Message Headers for blobstore
-+++++++++++++++++++++++++++++
+#### Message Headers for blobstore
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -184,13 +176,9 @@ Message Headers for blobstore
 |`CamelJcloudsBlobName` |The name of the blob.
 |=======================================================================
 
-[[jclouds-BlobstoreUsageSamples]]
-Blobstore Usage Samples
-^^^^^^^^^^^^^^^^^^^^^^^
+### Blobstore Usage Samples
 
-[[jclouds-Example1:Puttingtotheblob]]
-Example 1: Putting to the blob
-++++++++++++++++++++++++++++++
+#### Example 1: Putting to the blob
 
 This example will show you how you can store any message inside a blob
 using the jclouds component.
@@ -217,9 +205,7 @@ route.
 </route>
 --------------------------------------------------------------------------------------------
 
-[[jclouds-Example2:GettingReadingfromablob]]
-Example 2: Getting/Reading from a blob
-++++++++++++++++++++++++++++++++++++++
+#### Example 2: Getting/Reading from a blob
 
 This example will show you how you can read the contnet of a blob using
 the jclouds component.
@@ -246,9 +232,7 @@ route.
 </route>
 --------------------------------------------------------------------------------------------
 
-[[jclouds-Example3:Consumingablob]]
-Example 3: Consuming a blob
-+++++++++++++++++++++++++++
+#### Example 3: Consuming a blob
 
 This example will consume all blob that are under the specified
 container. The generated exchange will contain the payload of the blob
@@ -278,16 +262,12 @@ You can achieve the same goal by using xml, as you can see below.
 jclouds:compute:aws-ec2?operation=CamelJcloudsCreateNode&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
 -------------------------------------------------------------------------------------------------------------
 
-[[jclouds-ComputeUsageSamples]]
-Compute Usage Samples
-^^^^^^^^^^^^^^^^^^^^^
+### Compute Usage Samples
 
 Below are some examples that demonstrate the use of jclouds compute
 producer in java dsl and spring/blueprint xml.
 
-[[jclouds-Example1:Listingtheavailableimages.]]
-Example 1: Listing the available images.
-++++++++++++++++++++++++++++++++++++++++
+#### Example 1: Listing the available images.
 
 [source,java]
 --------------------------------------------
@@ -307,9 +287,7 @@ its body. You can also do the same using xml.
 </route>
 --------------------------------------------------------------------------
 
-[[jclouds-Example2:Createanewnode.]]
-Example 2: Create a new node.
-+++++++++++++++++++++++++++++
+#### Example 2: Create a new node.
 
 [source,java]
 ---------------------------------------------
@@ -334,9 +312,7 @@ spring xml.
 </route>
 -------------------------------------------------------------------------------------------------------------------------
 
-[[jclouds-Example3:Runashellscriptonrunningnode.]]
-Example 3: Run a shell script on running node.
-++++++++++++++++++++++++++++++++++++++++++++++
+#### Example 3: Run a shell script on running node.
 
 [source,java]
 --------------------------------------------
@@ -369,9 +345,7 @@ Here is the same using spring xml.
 </route>
 ----------------------------------------------------------------------------------------------
 
-[[jclouds-Seealso]]
-See also
-++++++++
+#### See also
 
 If you want to find out more about jclouds here is list of interesting
 resources
@@ -380,4 +354,4 @@ http://jclouds.incubator.apache.org/documentation/userguide/blobstore-guide/[Jcl
 Blobstore wiki]
 
 http://jclouds.incubator.apache.org/documentation/userguide/compute/[Jclouds
-Compute wiki]
+Compute wiki]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jcr/src/main/docs/jcr-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jcr/src/main/docs/jcr-component.adoc b/components/camel-jcr/src/main/docs/jcr-component.adoc
index 7f54eba..150546d 100644
--- a/components/camel-jcr/src/main/docs/jcr-component.adoc
+++ b/components/camel-jcr/src/main/docs/jcr-component.adoc
@@ -1,4 +1,4 @@
-# JCR Component
+## JCR Component
 
 The *`jcr`* component allows you to add/read nodes to/from a JCR
 compliant content repository (for example,
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[JCR-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------
@@ -32,16 +30,12 @@ jcr://user:password@repository/path/to/node
 From *Camel 2.10* onwards you can use consumer as an EventListener in
 JCR or a producer to read a node by identifier.
 
-[[JCR-Usage]]
-Usage
-^^^^^
+### Usage
 
 The `repository` element of the URI is used to look up the JCR
 `Repository` object in the Camel context registry.
 
-[[JCR-Options]]
-JCR Options
-+++++++++++
+#### JCR Options
 
 
 // component options: START
@@ -86,9 +80,7 @@ message headers in Camel versions earlier than 2.12.3. See
 https://issues.apache.org/jira/browse/CAMEL-7067[https://issues.apache.org/jira/browse/CAMEL-7067]
 for more details.
 
-[[JCR-Example]]
-Example
-^^^^^^^
+### Example
 
 The snippet below creates a node named `node` under the `/home/test`
 node in the content repository. One additional property is added to the
@@ -117,12 +109,9 @@ all the children.
 </route>
 ---------------------------------------------------------------------------------------------
 
-[[JCR-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jdbc/src/main/docs/jdbc-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jdbc/src/main/docs/jdbc-component.adoc b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
index 6219831..2a7849f 100644
--- a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
+++ b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
@@ -1,4 +1,4 @@
-# JDBC Component
+## JDBC Component
 
 The *jdbc* component enables you to access databases through JDBC, where
 SQL queries (SELECT) and operations (INSERT, UPDATE, etc) are sent in
@@ -22,9 +22,7 @@ for this component:
 This component can only be used to define producer endpoints, which
 means that you cannot use the JDBC component in a `from()` statement.
 
-[[JDBC-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -36,9 +34,7 @@ This component only supports producer endpoints.
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[JDBC-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -89,9 +85,7 @@ The JDBC component supports 14 endpoint options which are listed below:
 
 
 
-[[JDBC-Result]]
-Result
-^^^^^^
+### Result
 
 By default the result is returned in the OUT body as an
 `ArrayList<HashMap<String, Object>>`. The `List` object contains the
@@ -102,9 +96,7 @@ the result.
 *Note:* This component fetches `ResultSetMetaData` to be able to return
 the column name as the key in the `Map`.
 
-[[JDBC-MessageHeaders]]
-Message Headers
-+++++++++++++++
+#### Message Headers
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -128,9 +120,7 @@ type.
 `useHeadersAsParameters` has been enabled.
 |=======================================================================
 
-[[JDBC-Generatedkeys]]
-Generated keys
-^^^^^^^^^^^^^^
+### Generated keys
 
 *Available as of Camel 2.10*
 
@@ -147,9 +137,7 @@ test].
 
 Using generated keys does not work with together with named parameters.
 
-[[JDBC-Usingnamedparameters]]
-Using named parameters
-^^^^^^^^^^^^^^^^^^^^^^
+### Using named parameters
 
 *Available as of Camel 2.12*
 
@@ -172,9 +160,7 @@ Notice in the example above we set two headers with constant value +
 You can also store the header values in a `java.util.Map` and store the
 map on the headers with the key `CamelJdbcParameters`.
 
-[[JDBC-Samples]]
-Samples
-^^^^^^^
+### Samples
 
 In the following example, we fetch the rows from the customer table.
 
@@ -210,9 +196,7 @@ from("direct:hello")
   .to("mock:result");
 -------------------------------------------------------------------------------------------------
 
-[[JDBC-Sample-Pollingthedatabaseeveryminute]]
-Sample - Polling the database every minute
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample - Polling the database every minute
 
 If we want to poll a database using the JDBC component, we need to
 combine it with a polling scheduler such as the link:timer.html[Timer]
@@ -224,9 +208,7 @@ data from the database every 60 seconds:
 from("timer://foo?period=60000").setBody(constant("select * from customer")).to("jdbc:testdb").to("activemq:queue:customers");
 ------------------------------------------------------------------------------------------------------------------------------
 
-[[JDBC-Sample-MoveDataBetweenDataSources]]
-Sample - Move Data Between Data Sources +
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample - Move Data Between Data Sources +
 
 A common use case is to query for data, process it and move it to
 another data source (ETL operations). In the following example, we
@@ -246,14 +228,11 @@ from("timer://MoveNewCustomersEveryHour?period=3600000")
 
 Â 
 
-[[JDBC-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:sql.html[SQL]
-
+* link:sql.html[SQL]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jetty9/src/main/docs/jetty-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jetty9/src/main/docs/jetty-component.adoc b/components/camel-jetty9/src/main/docs/jetty-component.adoc
index fc6ced7..8bc5d3b 100644
--- a/components/camel-jetty9/src/main/docs/jetty-component.adoc
+++ b/components/camel-jetty9/src/main/docs/jetty-component.adoc
@@ -1,4 +1,4 @@
-# Jetty 9 Component
+## Jetty 9 Component
 
 The *jetty* component provides HTTP-based link:endpoint.html[endpoints]
 for consuming and producing HTTP requests. That is, the Jetty component
@@ -31,9 +31,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Jetty-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------------------------
@@ -43,9 +41,7 @@ jetty:http://hostname[:port][/resourceUri][?options]
 You can append query options to the URI in the following format,
 `?option=value&option=value&...`
 
-[[Jetty-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -172,9 +168,7 @@ The Jetty 9 component supports 54 endpoint options which are listed below:
 
 
 
-[[Jetty-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Camel uses the same message headers as the link:http.html[HTTP]
 component.
@@ -190,17 +184,13 @@ header named `orderid` with the value 123.
 Starting with Camel 2.2.0, you can get the request.parameter from the
 message header not only from Get Method, but also other HTTP method.
 
-[[Jetty-Usage]]
-Usage
-^^^^^
+### Usage
 
 The Jetty component supports both consumer and producer endpoints.
 Another option for producing to other HTTP endpoints, is to use the
 link:http.html[HTTP Component]
 
-[[Jetty-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
+### Producer Example
 
 The following is a basic example of how to send an HTTP request to an
 existing HTTP endpoint.
@@ -222,9 +212,7 @@ or in Spring XML
 <route>
 ---------------------------------------------
 
-[[Jetty-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
+### Consumer Example
 
 In this sample we define a route that exposes a HTTP service at
 `http://localhost:8080/myapp/myservice`:
@@ -267,9 +255,7 @@ link:simple.html[Simple] (such as link:el.html[EL] or
 link:ognl.html[OGNL]) we could also test for the parameter value and do
 routing based on the header value as well.
 
-[[Jetty-SessionSupport]]
-Session Support
-^^^^^^^^^^^^^^^
+### Session Support
 
 The session support option, `sessionSupport`, can be used to enable a
 `HttpSession` object and access the session object while processing the
@@ -302,9 +288,7 @@ public void process(Exchange exchange) throws Exception {
 }
 --------------------------------------------------------------------------------------
 
-[[Jetty-SSLSupport(HTTPS)]]
-SSL Support (HTTPS)
-^^^^^^^^^^^^^^^^^^^
+### SSL Support (HTTPS)
 
 [[Jetty-UsingtheJSSEConfigurationUtility]]
 Using the JSSE Configuration Utility
@@ -475,9 +459,7 @@ difference between the various Camel versions:
 The value you use as keys in the above map is the port you configure
 Jetty to listen on.
 
-[[Jetty-ConfiguringgeneralSSLproperties]]
-Configuring general SSL properties
-++++++++++++++++++++++++++++++++++
+#### Configuring general SSL properties
 
 *Available as of Camel 2.5*
 
@@ -501,9 +483,7 @@ the port number as entry).
 </bean>
 -----------------------------------------------------------------------------
 
-[[Jetty-HowtoobtainreferencetotheX509Certificate]]
-How to obtain reference to the X509Certificate
-++++++++++++++++++++++++++++++++++++++++++++++
+#### How to obtain reference to the X509Certificate
 
 Jetty stores a reference to the certificate in the HttpServletRequest
 which you can access from code as follows:
@@ -514,9 +494,7 @@ HttpServletRequest req = exchange.getIn().getBody(HttpServletRequest.class);
 X509Certificate cert = (X509Certificate) req.getAttribute("javax.servlet.request.X509Certificate")
 --------------------------------------------------------------------------------------------------
 
-[[Jetty-ConfiguringgeneralHTTPproperties]]
-Configuring general HTTP properties
-+++++++++++++++++++++++++++++++++++
+#### Configuring general HTTP properties
 
 *Available as of Camel 2.5*
 
@@ -537,9 +515,7 @@ the port number as entry).
 </bean>
 -----------------------------------------------------------------------------
 
-[[Jetty-ObtainingX-Forwarded-ForheaderwithHttpServletRequest.getRemoteAddr]]
-Obtaining X-Forwarded-For header with HttpServletRequest.getRemoteAddr()
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Obtaining X-Forwarded-For header with HttpServletRequest.getRemoteAddr()
 
 If the HTTP requests are handled by an Apache server and forwarded to
 jetty with mod_proxy, the original client IP address is in the
@@ -571,9 +547,7 @@ This is particularly useful when an existing Apache server handles TLS
 connections for a domain and proxies them to application servers
 internally.
 
-[[Jetty-DefaultbehaviorforreturningHTTPstatuscodes]]
-Default behavior for returning HTTP status codes
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Default behavior for returning HTTP status codes
 
 The default behavior of HTTP status codes is defined by the
 `org.apache.camel.component.http.DefaultHttpBinding` class, which
@@ -586,9 +560,7 @@ returned, and the stacktrace is returned in the body. If you want to
 specify which HTTP status code to return, set the code in the
 `Exchange.HTTP_RESPONSE_CODE` header of the OUT message.
 
-[[Jetty-CustomizingHttpBinding]]
-Customizing HttpBinding
-^^^^^^^^^^^^^^^^^^^^^^^
+### Customizing HttpBinding
 
 By default, Camel uses the
 `org.apache.camel.component.http.DefaultHttpBinding` to handle how a
@@ -614,9 +586,7 @@ And then we can reference this binding when we define the route:
 <route><from uri="jetty:http://0.0.0.0:8080/myapp/myservice?httpBindingRef=mybinding"/><to uri="bean:doSomething"/></route>
 ---------------------------------------------------------------------------------------------------------------------------
 
-[[Jetty-Jettyhandlersandsecurityconfiguration]]
-Jetty handlers and security configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Jetty handlers and security configuration
 
 You can configure a list of Jetty handlers on the endpoint, which can be
 useful for enabling advanced Jetty security features. These handlers are
@@ -686,9 +656,7 @@ from("jetty:http://0.0.0.0:9080/myservice?handlers=securityHandler")
 If you need more handlers, set the `handlers` option equal to a
 comma-separated list of bean IDs.
 
-[[Jetty-HowtoreturnacustomHTTP500replymessage]]
-How to return a custom HTTP 500 reply message
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to return a custom HTTP 500 reply message
 
 You may want to return a custom reply message when something goes wrong,
 instead of the default reply message Camel link:jetty.html[Jetty]
@@ -699,9 +667,7 @@ link:exception-clause.html[Exception Clause] to construct the custom
 reply message. For example as show here, where we return
 `Dude something went wrong` with HTTP error code 500:
 
-[[Jetty-Multi-partFormsupport]]
-Multi-part Form support
-^^^^^^^^^^^^^^^^^^^^^^^
+### Multi-part Form support
 
 From Camel 2.3.0, camel-jetty support to multipart form post out of box.
 The submitted form-data are mapped into the message header. Camel-jetty
@@ -713,9 +679,7 @@ of the attachment file name. You can find the example here.
 earlier versions you receive the temporary file name for the attachment
 instead*
 
-[[Jetty-JettyJMXsupport]]
-Jetty JMX support
-^^^^^^^^^^^^^^^^^
+### Jetty JMX support
 
 From Camel 2.3.0, camel-jetty supports the enabling of Jetty's JMX
 capabilities at the component and endpoint level with the endpoint
@@ -746,14 +710,11 @@ sharing the same MBeanServer between the instances, you can provide both
 instances with a reference to the same MBeanContainer in order to avoid
 name collisions when registering Jetty MBeans.
 
-[[Jetty-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:http.html[HTTP]
-
+* link:http.html[HTTP]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jgroups/src/main/docs/jgroups-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jgroups/src/main/docs/jgroups-component.adoc b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
index d381aa2..384a3b3 100644
--- a/components/camel-jgroups/src/main/docs/jgroups-component.adoc
+++ b/components/camel-jgroups/src/main/docs/jgroups-component.adoc
@@ -1,4 +1,4 @@
-# JGroups Component
+## JGroups Component
 
 *Available since Camel 2.10.0*
 
@@ -33,9 +33,7 @@ Camel *2.13.0* or higher, please use the following POM entry instead.
 </dependency>
 ------------------------------------------------------------
 
-[[JGroups-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -45,9 +43,7 @@ jgroups:clusterName[?options]
 Where *clusterName* represents the name of the JGroups cluster the
 component should connect to.
 
-[[JGroups-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -93,9 +89,7 @@ The JGroups component supports 7 endpoint options which are listed below:
 
 
 
-[[JGroups-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -116,9 +110,7 @@ consumed message has been extracted.
 endpoint.
 |=======================================================================
 Â 
-[[JGroups-Usage]]
-Usage
-^^^^^
+### Usage
 
 Using `jgroups` component on the consumer side of the route will capture
 messages received by the `JChannel` associated with the endpoint and
@@ -143,9 +135,7 @@ endpoint.
 from("direct:start").to("jgroups:clusterName");
 --------------------------------------------------
 
-[[JGroups-Predefinedfilters]]
-Predefined filters
-^^^^^^^^^^^^^^^^^^
+### Predefined filters
 
 Starting from version *2.13.0* of Camel, JGroups component comes with
 predefined filters factory class named `JGroupsFilters.`
@@ -168,9 +158,7 @@ from("jgroups:clusterName?enableViewMessages=true").
   to("seda:masterNodeEventsQueue");
 ----------------------------------------------------------------------------------------
 
-[[JGroups-Predefinedexpressions]]
-Predefined expressions
-^^^^^^^^^^^^^^^^^^^^^^
+### Predefined expressions
 
 Starting from version *2.13.0* of Camel, JGroups component comes with
 predefined expressions factory class named `JGroupsExpressions.`
@@ -208,13 +196,9 @@ from("jgroups:clusterName?enableViewMessages=true").
 from("timer://master?repeatCount=1").routeId("masterRoute").autoStartup(false).to(masterMockUri); 
 -----------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[JGroups-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[JGroups-SendingreceivingmessagestofromtheJGroupscluster]]
-Sending (receiving) messages to (from) the JGroups cluster
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Sending (receiving) messages to (from) the JGroups cluster
 
 In order to send message to the JGroups cluster use producer endpoint,
 just as demonstrated on the snippet below.
@@ -240,9 +224,7 @@ from("jgroups:myCluster").to("mock:messagesFromTheCluster");
 mockEndpoint.assertIsSatisfied();
 ------------------------------------------------------------
 
-[[JGroups-Receiveclusterviewchangenotifications]]
-Receive cluster view change notifications
-+++++++++++++++++++++++++++++++++++++++++
+#### Receive cluster view change notifications
 
 The snippet below demonstrates how to create the consumer endpoint
 listening to the notifications regarding cluster membership changes. By
@@ -258,9 +240,7 @@ from("jgroups:clusterName?enableViewMessages=true").to(mockEndpoint);
 mockEndpoint.assertIsSatisfied();
 ---------------------------------------------------------------------
 
-[[JGroups-Keepingsingletonroutewithinthecluster]]
-Keeping singleton route within the cluster
-++++++++++++++++++++++++++++++++++++++++++
+#### Keeping singleton route within the cluster
 
 The snippet below demonstrates how to keep the singleton consumer route
 in the cluster of Camel Contexts. As soon as the master node dies, one
@@ -281,4 +261,4 @@ from("jgroups:clusterName?enableViewMessages=true").
   to("controlbus:route?routeId=masterRoute&action=start&async=true");
 
 from("jetty:http://localhost:8080/orders").routeId("masterRoute").autoStartup(false).to("jms:orders"); 
------------------------------------------------------------------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jibx/src/main/docs/jibx-dataformat.adoc b/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
index ec98de0..a322bcb 100644
--- a/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
+++ b/components/camel-jibx/src/main/docs/jibx-dataformat.adoc
@@ -1,4 +1,4 @@
-# JiBX DataFormat
+## JiBX DataFormat
 
 *Available as of Camel 2.6*
 
@@ -26,9 +26,7 @@ from("mqseries:Another.Queue").
   to("activemq:My.Queue");
 -------------------------------------------
 
-[[JiBX-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The JiBX dataformat supports 3 options which are listed below.
@@ -47,9 +45,7 @@ The JiBX dataformat supports 3 options which are listed below.
 // dataformat options: END
 
 
-[[JiBX-JiBXSpringDSL]]
-JiBX Spring DSL
-^^^^^^^^^^^^^^^
+### JiBX Spring DSL
 
 JiBX data format is also supported by Camel Spring DSL.
 
@@ -79,9 +75,7 @@ JiBX data format is also supported by Camel Spring DSL.
 </camelContext>
 --------------------------------------------------------------------------------------
 
-[[JiBX-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use JiBX in your camel routes you need to add the a dependency on
 *camel-jibx* which implements this data format.
@@ -97,4 +91,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-jibx</artifactId>
   <version>2.6.0</version>
 </dependency>
--------------------------------------
+-------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jing/src/main/docs/jing-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jing/src/main/docs/jing-component.adoc b/components/camel-jing/src/main/docs/jing-component.adoc
index 2c4a649..8510f3e 100644
--- a/components/camel-jing/src/main/docs/jing-component.adoc
+++ b/components/camel-jing/src/main/docs/jing-component.adoc
@@ -1,4 +1,4 @@
-# Jing Component
+## Jing Component
 
 The Jing component uses the
 http://www.thaiopensource.com/relaxng/jing.html[Jing Library] to perform
@@ -24,9 +24,7 @@ for this component:
 Note that the link:msv.html[MSV] component can also support RelaxNG XML
 syntax.
 
-[[Jing-URIformatCamel2.16]]
-URI format Camel 2.16
-^^^^^^^^^^^^^^^^^^^^^
+### URI format Camel 2.16
 
 [source,java]
 ------------------------------
@@ -36,9 +34,7 @@ jing:someLocalOrRemoteResource
 From Camel 2.16 the component use jing as name, and you can use the
 option compactSyntax to turn on either RNG or RNC mode.
 
-[[Jing-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -64,9 +60,7 @@ The Jing component supports 3 endpoint options which are listed below:
 
 
 
-[[Jing-Example]]
-Example
-^^^^^^^
+### Example
 
 The following
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-jing/src/test/resources/org/apache/camel/component/validator/jing/rnc-context.xml[example]
@@ -76,12 +70,9 @@ based on whether or not the XML matches the given
 http://relaxng.org/compact-tutorial-20030326.html[RelaxNG Compact
 Syntax] schema (which is supplied on the classpath).
 
-[[Jing-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-jira/src/main/docs/jira-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jira/src/main/docs/jira-component.adoc b/components/camel-jira/src/main/docs/jira-component.adoc
index 28abb51..7ca42ac 100644
--- a/components/camel-jira/src/main/docs/jira-component.adoc
+++ b/components/camel-jira/src/main/docs/jira-component.adoc
@@ -1,4 +1,4 @@
-# JIRA Component
+## JIRA Component
 
 *Available as of Camel 2.15*
 
@@ -31,18 +31,14 @@ for this component:
 </dependency>
 ---------------------------------------
 
-[[JIRA-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,text]
 -------------------------
 jira://endpoint[?options]
 -------------------------
 
-[[JIRA-Options:]]
-JIRA Options
-^^^^^^^^^^^^^
+### JIRA Options
 
 
 // component options: START
@@ -75,9 +71,7 @@ The JIRA component supports 10 endpoint options which are listed below:
 
 
 
-[[JIRA-JQL:]]
-JQL:
-^^^^
+### JQL:
 
 The JQL URI option is used by both consumer endpoints.  Theoretically,
 items like "project key", etc. could be URI options themselves.
@@ -107,4 +101,4 @@ delay, etc.  Example:
 [source,text]
 ----------------------------------------------------------------------------------------------------------------------------------------------
 jira://[endpoint]?[required options]&jql=RAW(project=[project key] AND status in (Open, \"Coding In Progress\") AND \"Number of comments\">0)"
-----------------------------------------------------------------------------------------------------------------------------------------------
+----------------------------------------------------------------------------------------------------------------------------------------------
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[09/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
index 83677bc..8163c28 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
@@ -1,10 +1,8 @@
-# Google Calendar Component
+## Google Calendar Component
 
 *Available as of Camel 2.15*
 
-[[GoogleCalendar-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
 
 The Google Calendar component provides access
 to http://google.com/calendar[Google Calendar] via
@@ -33,9 +31,7 @@ for this component:
         
 ----------------------------------------------------------
 
-[[GoogleCalendar-options]]
-1. Google Calendar Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### 1. Google Calendar Options
 
 
 
@@ -90,9 +86,7 @@ The Google Calendar component supports 16 endpoint options which are listed belo
 // endpoint options: END
 
 
-[[GoogleCalendar-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 The GoogleCalendar Component uses the following URI format:
 
@@ -112,9 +106,7 @@ Endpoint prefix can be one of:
 * list
 * settings
 
-[[GoogleCalendar-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
 
 Producer endpoints can use endpoint prefixes followed by endpoint names
 and associated options described next. A shorthand alias can be used for
@@ -133,9 +125,7 @@ overrides message header, i.e. the endpoint option `inBody=option` would
 override a `CamelGoogleCalendar.option` header.
 
 
-[[GoogleCalendar-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 
 Any of the producer endpoints can be used as a consumer endpoint.
 Consumer endpoints can use
@@ -145,19 +135,15 @@ invocation. Consumer endpoints that return an array or collection will
 generate one exchange per element, and their routes will be executed
 once for each exchange.
 
-[[GoogleCalendar-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Any URI option can be provided in a message header for producer
 endpoints with a `CamelGoogleCalendar.` prefix.
 
-[[GoogleCalendar-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 All result message bodies utilize objects provided by the underlying
 APIs used by the GoogleCalendarComponent. Producer endpoints can specify
 the option name for incoming message body in the `inBody` endpoint URI
 parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages.     
+endpoint will map every element to distinct messages.     
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-drive/src/main/docs/google-drive-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-drive/src/main/docs/google-drive-component.adoc b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
index 39457d7..10feb33 100644
--- a/components/camel-google-drive/src/main/docs/google-drive-component.adoc
+++ b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
@@ -1,4 +1,4 @@
-# Google Drive Component
+## Google Drive Component
 
 *Available as of Camel 2.14*
 
@@ -28,9 +28,7 @@ for this component:
         
 -------------------------------------------------------
 
-[[GoogleDrive-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 '''''
 
@@ -57,9 +55,7 @@ Endpoint prefix can be one of:
 * drive-replies
 * drive-revisions
 
-[[GoogleDrive-GoogleDriveComponent.1]]
-GoogleDriveComponent
-^^^^^^^^^^^^^^^^^^^^
+### GoogleDriveComponent
 
 
 
@@ -114,9 +110,7 @@ The Google Drive component supports 14 endpoint options which are listed below:
 
 
 
-[[GoogleDrive-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
 
 Producer endpoints can use endpoint prefixes followed by endpoint names
 and associated options described next. A shorthand alias can be used for
@@ -137,9 +131,7 @@ override a `CamelGoogleDrive.option` header.
 For more information on the endpoints and options see API documentation
 at: https://developers.google.com/drive/v2/reference/[https://developers.google.com/drive/v2/reference/]
 
-[[GoogleDrive-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 
 Any of the producer endpoints can be used as a consumer endpoint.
 Consumer endpoints can use
@@ -149,19 +141,15 @@ invocation. Consumer endpoints that return an array or collection will
 generate one exchange per element, and their routes will be executed
 once for each exchange.
 
-[[GoogleDrive-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Any URI option can be provided in a message header for producer
 endpoints with a `CamelGoogleDrive.` prefix.
 
-[[GoogleDrive-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 All result message bodies utilize objects provided by the underlying
 APIs used by the GoogleDriveComponent. Producer endpoints can specify
 the option name for incoming message body in the `inBody` endpoint URI
 parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages.     
+endpoint will map every element to distinct messages.     
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-mail/src/main/docs/google-mail-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-mail/src/main/docs/google-mail-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
index 293b216..c39f83d 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
@@ -1,10 +1,8 @@
-# Google Mail Component
+## Google Mail Component
 
 *Available as of Camel 2.15*
 
-[[GoogleMail-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
 
 The Google Mail component provides access
 to http://gmail.com/[Gmail] via
@@ -33,9 +31,7 @@ for this component:
         
 ------------------------------------------------------
 
-[[GoogleMail-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 The GoogleMail Component uses the following URI format:
 
@@ -54,9 +50,7 @@ Endpoint prefix can be one of:
 * threads
 * users
 
-[[GoogleMail-GoogleMailComponent.1]]
-GoogleMailComponent
-^^^^^^^^^^^^^^^^^^^
+### GoogleMailComponent
 
 
 
@@ -109,9 +103,7 @@ The Google Mail component supports 13 endpoint options which are listed below:
 
 
 
-[[GoogleMail-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
 
 Producer endpoints can use endpoint prefixes followed by endpoint names
 and associated options described next. A shorthand alias can be used for
@@ -132,9 +124,7 @@ override a `CamelGoogleMail.option` header.
 For more information on the endpoints and options see API documentation
 at: https://developers.google.com/gmail/api/v1/reference/[https://developers.google.com/gmail/api/v1/reference/]
 
-[[GoogleMail-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 
 Any of the producer endpoints can be used as a consumer endpoint.
 Consumer endpoints can use
@@ -144,19 +134,15 @@ invocation. Consumer endpoints that return an array or collection will
 generate one exchange per element, and their routes will be executed
 once for each exchange.
 
-[[GoogleMail-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 Any URI option can be provided in a message header for producer
 endpoints with a `CamelGoogleMail.` prefix.
 
-[[GoogleMail-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 All result message bodies utilize objects provided by the underlying
 APIs used by the GoogleMailComponent. Producer endpoints can specify the
 option name for incoming message body in the `inBody` endpoint URI
 parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages.     
+endpoint will map every element to distinct messages.     
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
index ddba59e..cdbb8f4 100644
--- a/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
+++ b/components/camel-google-pubsub/src/main/docs/google-pubsub-component.adoc
@@ -1,10 +1,8 @@
-# Google Pubsub Component
+## Google Pubsub Component
 
 *Available as of Camel 2.19*
 
-[[GooglePubsub-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
+### Component Description
 
 The Google Pubsub component provides access
 to https://cloud.google.com/pubsub/[Cloud Pub/Sub Infrastructure] via
@@ -44,9 +42,7 @@ https://developers.google.com/identity/protocols/application-default-credentials
 
 Service Account Email and Service Account Key can be found in the GCP JSON credentials file as client_email and private_key respectively.
 
-[[GooglePubsub-URIFormat]]
-URI Format
-^^^^^^^^^
+### URI Format
 
 The GoogleMail Component uses the following URI format:
 
@@ -56,9 +52,7 @@ The GoogleMail Component uses the following URI format:
 
 Destination Name can be either a topic or a subscription name.
 
-[[GooglePubsub-GooglePubsubComponent]]
-GooglePubsubComponent
-^^^^^^^^^^^^^^^^^^
+### GooglePubsubComponent
 
 // component options: START
 The Google Pubsub component supports 1 options which are listed below.
@@ -96,9 +90,7 @@ The Google Pubsub component supports 11 endpoint options which are listed below:
 {% endraw %}
 // endpoint options: END
 
-[[GooglePubsub-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Producer Endpoints
 
 Producer endpoints can accept and deliver to PubSub individual and grouped
 exchanges alike. Grouped exchanges have `Exchange.GROUPED_EXCHANGE` property set.
@@ -113,9 +105,7 @@ A Map set as message header `GooglePubsubConstants.ATTRIBUTES` will be sent as P
 Once exchange has been delivered to PubSub the PubSub Message ID will be assigned to
 the header `GooglePubsubConstants.MESSAGE_ID`.
 
-[[GooglePubsub-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
+### Consumer Endpoints
 Google PubSub will redeliver the message if it has not been acknowledged within the time period set
 as a configuration option on the subscription.
 
@@ -128,9 +118,7 @@ To ack/nack the message the component uses Acknowledgement ID stored as header `
 If the header is removed or tampered with, the ack will fail and the message will be redelivered
 again after the ack deadline.
 
-[[GooglePubsub-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^
+### Message Headers
 Headers set by the consumer endpoints:
 
 * GooglePubsubConstants.MESSAGE_ID
@@ -138,16 +126,12 @@ Headers set by the consumer endpoints:
 * GooglePubsubConstants.PUBLISH_TIME
 * GooglePubsubConstants.ACK_ID
 
-[[GooglePubsub-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 The consumer endpoint returns the content of the message as byte[] - exactly as the underlying system sends it.
 It is up for the route to convert/unmarshall the contents.
 
-[[GooglePubsub-RollbackRedelivery]]
-Rollback and Redelivery
-^^^^^^^^^^^^
+### Rollback and Redelivery
 
 The rollback for Google PubSub relies on the idea of the Acknowledgement Deadline - the time period where Google PubSub expects to receive the acknowledgement.
 If the acknowledgement has not been received, the message is redelivered.
@@ -164,4 +148,4 @@ setting the message header
 
 * GooglePubsubConstants.ACK_DEADLINE
 
-to the value in seconds.
+to the value in seconds.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-gora/src/main/docs/gora-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gora/src/main/docs/gora-component.adoc b/components/camel-gora/src/main/docs/gora-component.adoc
index 7913685..f09fbb8 100644
--- a/components/camel-gora/src/main/docs/gora-component.adoc
+++ b/components/camel-gora/src/main/docs/gora-component.adoc
@@ -1,4 +1,4 @@
-# Gora Component
+## Gora Component
 
 *Camel-Gora* is an http://camel.apache.org/[Apache Camel] component that
 allows you to work with NoSQL databases using the
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ---------------------------------------------------------
 
-[[Gora-ApacheGoraOverview]]
-Apache Gora Overview
-~~~~~~~~~~~~~~~~~~~~
+### Apache Gora Overview
 
 The http://gora.apache.org/[Apache Gora] open source framework provides
 an in-memory data model and persistence for big data. Gora supports
@@ -39,9 +37,7 @@ http://accumulo.apache.org/[Apache Accumulo],
 http://aws.amazon.com/dynamodb/[Amazon DynamoDB] and SQL databases such
 as http://hsqldb.org/[hsqldb], http://www.mysql.com/[MySQL] and more.
 
-[[Gora-URIformat]]
-URI format
-~~~~~~~~~~
+### URI format
 
 [source,text]
 ---------------------------
@@ -64,9 +60,7 @@ _Java DSL_
 to("gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore")
 -------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-[[Gora-Configuratiion]]
-Configuratiion
-~~~~~~~~~~~~~~
+### Configuratiion
 
 Using camel-gora needs some configuration. This mainly involve to
 configure the _AvroStore_ through the _gora.properties_ file and to
@@ -77,9 +71,7 @@ Extensive information for this configuration can be found in the apache
 http://gora.apache.org/current/index.html[gora documentation] and the
 http://gora.apache.org/current/gora-conf.html[gora-conf] page.
 
-[[Gora-Options]]
-Options
-~~~~~~~
+### Options
 
 
 // component options: START
@@ -126,9 +118,7 @@ The Gora component supports 22 endpoint options which are listed below:
 
 
 
-[[Gora-SupportedGoraOperations]]
-Supported Gora Operations
-~~~~~~~~~~~~~~~~~~~~~~~~~
+### Supported Gora Operations
 
 Supported operations include : *put*, *get*, *delete*, *getSchemaName*,
 *deleteSchema*, *createSchema*, *query*, *deleteByQuery*,
@@ -166,9 +156,7 @@ hold the objects._
 datastore._
 |=======================================================================
 
-[[Gora-GoraHeaders]]
-Gora Headers
-^^^^^^^^^^^^
+### Gora Headers
 
 [width="100%",cols="20%,80%",options="header",]
 |=======================================================================
@@ -179,9 +167,7 @@ Gora Headers
 |GoraKey | _Used in order to define the datum key for the operations need it._
 |=======================================================================
 
-[[Gora-Usageexamples]]
-Usage examples
-^^^^^^^^^^^^^^
+### Usage examples
 
 *Create Schema* _(XML DSL)_:
 
@@ -253,11 +239,9 @@ The full usage examples in the form of integration tests can be found at
 https://github.com/ipolyzos/camel-gora-examples/[camel-gora-examples]
 repository.
 
-[[Gora-Moreresources]]
-More resources
-^^^^^^^^^^^^^^
+### More resources
 
 For more please information and in depth configuration refer to the
 http://gora.apache.org/current/overview.html[Apache Gora Documentation]
 and the http://gora.apache.org/current/tutorial.html[Apache Gora
-Tutorial].
+Tutorial].
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-grape/src/main/docs/grape-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc b/components/camel-grape/src/main/docs/grape-component.adoc
index 02b2b34..4cddf27 100644
--- a/components/camel-grape/src/main/docs/grape-component.adoc
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -1,4 +1,4 @@
-# Grape Component
+## Grape Component
 
 Available as of Camel 2.16 
 
@@ -9,9 +9,7 @@ can add new components, data formats and beans to your `CamelContext`
 without the restart of the router.
 
 
-[[Grape-Options]]
-Grape options
-^^^^^^^^^^^^^
+### Grape options
 
 // component options: START
 The Grape component has no options.
@@ -34,9 +32,7 @@ The Grape component supports 3 endpoint options which are listed below:
 
 
 
-[[Grape-Settingupclassloader]]
-Setting up class loader
-^^^^^^^^^^^^^^^^^^^^^^^
+### Setting up class loader
 
 Grape requires using Groovy class loader with the `CamelContext`. You
 can enable Groovy class loading on the existing Camel Context using the
@@ -57,9 +53,7 @@ yourself:
 camelContext.setApplicationContextClassLoader(new GroovyClassLoader(myClassLoader));
 ------------------------------------------------------------------------------------
 
-[[Grape-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 Grape component supports only producer endpoints.
 
@@ -86,9 +80,7 @@ from("direct:loadCamelFTP").
   to("grape:defaultMavenCoordinates");
 ----------------------------------------------------------
 
-[[Grape-AddingtheGrapecomponenttotheproject]]
-Adding the Grape component to the project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Adding the Grape component to the project
 
 Maven users will need to add the following dependency to their `pom.xml`
 for this component:
@@ -103,9 +95,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Grape-Defaultpayloadtype]]
-Default payload type
-^^^^^^^^^^^^^^^^^^^^
+### Default payload type
 
 By default Camel Grape component operates on the String payloads:
 
@@ -126,9 +116,7 @@ String:
 producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2".getBytes());
 -----------------------------------------------------------------------------------------------------------
 
-[[Grape-Headers]]
-Headers
-^^^^^^^
+### Headers
 
 The following headers are recognized by the Grape component:
 
@@ -139,9 +127,7 @@ The following headers are recognized by the Grape component:
 |`CamelGrapeCommand` |`GrapeConstants.GRAPE_COMMAND` |Producer |`org.apache.camel.component.grape.GrapeCommand` |The command to be performed by the Grape endpoint. Default to `grab`.
 |=======================================================================
 
-[[Grape-Loadingcomponentsatruntime]]
-Loading components at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading components at runtime
 
 In order to load the new component at the router runtime, just grab the
 jar containing the given component:
@@ -153,9 +139,7 @@ template.sendBody("grape:grape", "org.apache.camel/camel-stream/2.15.2");
 template.sendBody("stream:out", "msg");
 -------------------------------------------------------------------------
 
-[[Grape-Loadingprocessorsbeanatruntime]]
-Loading processors bean at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading processors bean at runtime
 
 In order to load the new processor bean  with your custom business login
 at the router runtime, just grab the jar containing the required bean:
@@ -170,9 +154,7 @@ int price = template.requestBody("bean:com.example.PricingBean?method=currentPro
 
 Â 
 
-[[Grape-LoadingdeployedjarsafterCamelcontextrestart]]
-Loading deployed jars after Camel context restart
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading deployed jars after Camel context restart
 
 After you download new jar, you usually would like to have it loaded by
 the Camel again after the restart of the `CamelContext`. It is certainly
@@ -201,9 +183,7 @@ camelContext.addRoutes(
 
 Â 
 
-[[Grape-Managingtheinstalledjars]]
-Managing the installed jars
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Managing the installed jars
 
 If you would like to check what jars have been installed into the given
 `CamelContext`, send message to the grape endpoint with
@@ -237,12 +217,9 @@ command:
         setBody().constant("Installed patches have been deleted."); 
 -----------------------------------------------------------------------------------------
 
-[[Grape-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-groovy/src/main/docs/groovy-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-groovy/src/main/docs/groovy-language.adoc b/components/camel-groovy/src/main/docs/groovy-language.adoc
index 1eca86d..58edbd6 100644
--- a/components/camel-groovy/src/main/docs/groovy-language.adoc
+++ b/components/camel-groovy/src/main/docs/groovy-language.adoc
@@ -1,4 +1,4 @@
-# Groovy Language
+## Groovy Language
 
 Camel supports http://groovy.codehaus.org/[Groovy] among other
 link:scripting-languages.html[Scripting Languages] to allow an
@@ -18,9 +18,7 @@ link:predicate.html[Predicate] in a link:message-filter.html[Message
 Filter] or as an link:expression.html[Expression] for a
 link:recipient-list.html[Recipient List]
 
-[[Groovy-Options]]
-Groovy Options
-^^^^^^^^^^^^^^
+### Groovy Options
 
 
 
@@ -40,9 +38,7 @@ The Groovy language supports 1 options which are listed below.
 
 
 
-[[Groovy-CustomizingGroovyShell]]
-Customizing Groovy Shell
-^^^^^^^^^^^^^^^^^^^^^^^^
+### Customizing Groovy Shell
 
 Sometimes you may need to use custom `GroovyShell` instance in your
 Groovy expressions. To provide custom `GroovyShell`, add implementation
@@ -68,9 +64,7 @@ public class CustomGroovyShellFactory implements GroovyShellFactory {
 ...Camel will use your custom GroovyShell instance (containing your
 custom static imports), instead of the default one.
 
-[[Groovy-Example]]
-Example
-^^^^^^^
+### Example
 
 [source,java]
 ------------------------------------------------------------------------------------------------
@@ -91,9 +85,7 @@ And the Spring DSL:
         </route>
 -----------------------------------------------------------------------------
 
-[[Groovy-ScriptContext]]
-ScriptContext
-^^^^^^^^^^^^^
+### ScriptContext
 
 The JSR-223 scripting languages ScriptContext is pre configured with the
 following attributes all set at `ENGINE_SCOPE`:
@@ -121,9 +113,7 @@ further below for example.
 See link:scripting-languages.html[Scripting Languages] for the list of
 languages with explicit DSL support.
 
-[[Groovy-AdditionalargumentstoScriptingEngine]]
-Additional arguments to ScriptingEngine
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Additional arguments to ScriptingEngine
 
 *Available as of Camel 2.8*
 
@@ -131,9 +121,7 @@ You can provide additional arguments to the `ScriptingEngine` using a
 header on the Camel message with the key `CamelScriptArguments`. +
  See this example:
 
-[[Groovy-Usingpropertiesfunction]]
-Using properties function
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using properties function
 
 *Available as of Camel 2.9*
 
@@ -156,9 +144,7 @@ same example is simpler:
 .setHeader("myHeader").groovy("properties.resolve(request.headers.get(&#39;foo&#39;))")
 ---------------------------------------------------------------------------------------
 
-[[Groovy-Loadingscriptfromexternalresource]]
-Loading script from external resource
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Loading script from external resource
 
 *Available as of Camel 2.11*
 
@@ -172,9 +158,7 @@ eg to refer to a file on the classpath you can do:
 .setHeader("myHeader").groovy("resource:classpath:mygroovy.groovy")
 -------------------------------------------------------------------
 
-[[Groovy-Howtogettheresultfrommultiplestatementsscript]]
-How to get the result from multiple statements script
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get the result from multiple statements script
 
 *Available as of Camel 2.14*
 
@@ -192,9 +176,7 @@ bar = "baz";
 result = body * 2 + 1
 -------------------------------------------------------------
 
-[[Groovy-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use scripting languages in your camel routes you need to add the a
 dependency on *camel-script* which integrates the JSR-223 scripting
@@ -211,4 +193,4 @@ link:download.html[the download page for the latest versions]).
   <artifactId>camel-script</artifactId>
   <version>x.x.x</version>
 </dependency>
----------------------------------------
+---------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gson/src/main/docs/json-gson-dataformat.adoc b/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
index aabde3c..c0df1e6 100644
--- a/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
+++ b/components/camel-gson/src/main/docs/json-gson-dataformat.adoc
@@ -1,4 +1,4 @@
-# JSon GSon DataFormat
+## JSon GSon DataFormat
 
 *Available as of Camel 2.18*
 
@@ -12,9 +12,7 @@ from("activemq:My.Queue").
   to("mqseries:Another.Queue");
 -------------------------------
 
-[[Gson-Options]]
-Gson Options
-^^^^^^^^^^^^
+### Gson Options
 
 
 // dataformat options: START
@@ -49,9 +47,7 @@ The JSon GSon dataformat supports 17 options which are listed below.
 
 
 
-[[Gson-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use Gson in your camel routes you need to add the dependency
 on *camel-gson* which implements this data format.
@@ -68,4 +64,4 @@ link:download.html[the download page for the latest versions]).
   <version>x.x.x</version>
   <!-- use the same version as your Camel core version -->
 </dependency>
-----------------------------------------------------------
+----------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
index f796008..879c8c9 100644
--- a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
+++ b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
@@ -1,4 +1,4 @@
-# Guava EventBus Component
+## Guava EventBus Component
 
 *Available since Camel 2.10.0*
 
@@ -27,9 +27,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[GuavaEventBus-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 --------------------------------
@@ -40,9 +38,7 @@ Where *busName* represents the name of the
 `com.google.common.eventbus.EventBus` instance located in the Camel
 registry.
 
-[[GuavaEventBus-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -87,9 +83,7 @@ The Guava EventBus component supports 7 endpoint options which are listed below:
 
 
 
-[[GuavaEventBus-Usage]]
-Usage
-^^^^^
+### Usage
 
 Using `guava-eventbus` component on the consumer side of the route will
 capture messages sent to the Guava `EventBus` and forward them to the
@@ -131,9 +125,7 @@ eventBus.register(new Object(){
 });
 ----------------------------------------------------------------------
 
-[[GuavaEventBus-DeadEventconsiderations]]
-DeadEvent considerations
-^^^^^^^^^^^^^^^^^^^^^^^^
+### DeadEvent considerations
 
 Keep in mind that due to the limitations caused by the design of the
 Guava EventBus, you cannot specify event class to be received by the
@@ -182,9 +174,7 @@ follows.
 from("guava-eventbus:busName?listenerInterface=com.example.CustomListener").to("seda:queue");
 ---------------------------------------------------------------------------------------------
 
-[[GuavaEventBus-Consumingmultipletypeofevents]]
-Consuming multiple type of events
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming multiple type of events
 
 In order to define multiple type of events to be consumed by Guava
 EventBus consumer use `listenerInterface` endpoint option, as listener
@@ -212,4 +202,4 @@ follows.
 [source,java]
 -----------------------------------------------------------------------------------------------------
 from("guava-eventbus:busName?listenerInterface=com.example.MultipleEventsListener").to("seda:queue");
------------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
index b042205..4873afa 100644
--- a/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
+++ b/components/camel-hazelcast/src/main/docs/hazelcast-component.adoc
@@ -1,4 +1,4 @@
-# Hazelcast Component
+## Hazelcast Component
 
 *Available as of Camel 2.7*
 
@@ -28,9 +28,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[HazelcastComponent-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -------------------------------------------------------------------------------------------------------------------------
@@ -42,9 +40,7 @@ hazelcast:[ map | multimap | queue | topic | seda | set | atomicvalue | instance
 
 * RingBuffer support is available as of Camel 2.16. *
 
-[[HazelcastComponent-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -94,9 +90,7 @@ The Hazelcast component supports 13 endpoint options which are listed below:
 
 
 
-[[HazelcastComponent-Sections]]
-Sections
-^^^^^^^^
+### Sections
 
 1.  Usage of link:hazelcast-component.html[#map]
 2.  Usage of link:hazelcast-component.html[#multimap]
@@ -109,13 +103,9 @@ Sections
 9.  Usage of link:hazelcast-component.html[#replicatedmap] 
 10. Usage of link:hazelcast-component.html[#ringbuffer] 
 
-[[HazelcastComponent-UsageofMap]]
-Usage of Map
-^^^^^^^^^^^^
+### Usage of Map
 
-[[HazelcastComponent-mapcacheproducer-to-map]]
-Map cache producer - to("hazelcast:map:foo")
-++++++++++++++++++++++++++++++++++++++++++++
+#### Map cache producer - to("hazelcast:map:foo")
 
 If you want to store a value in a map you can use the map cache
 producer.
@@ -343,9 +333,7 @@ String q1 = "bar > 1000";
 template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
 -------------------------------------------------------------------------------
 
-[[HazelcastComponent-mapcacheconsumer-from-map]]
-Map cache consumer - from("hazelcast:map:foo")
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Map cache consumer - from("hazelcast:map:foo")
 
 Hazelcast provides event listeners on their data grid. If you want to be
 notified if a cache will be manipulated, you can use the map consumer.
@@ -399,13 +387,9 @@ fromF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
          .log("fail!");
 --------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-UsageofMultiMap]]
-Usage of Multi Map
-^^^^^^^^^^^^^^^^^^
+### Usage of Multi Map
 
-[[HazelcastComponent-multimapcacheproducer-to-multimap]]
-multimap cache producer - to("hazelcast:multimap:foo")
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### multimap cache producer - to("hazelcast:multimap:foo")
 
 A multimap is a cache where you can store n values to one key. The
 multimap producer provides 4 operations (put, get, removevalue, delete).
@@ -543,9 +527,7 @@ you can call them in your test class with:
 template.sendBodyAndHeader("direct:[put|get|removevalue|delete]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
 ------------------------------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-multimapcacheconsumer-from-multimap]]
-multimap cache consumer - from("hazelcast:multimap:foo")
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### multimap cache consumer - from("hazelcast:multimap:foo")
 
 For the multimap cache this component provides the same listeners /
 variables as for the map cache consumer (except the update and enviction
@@ -589,13 +571,9 @@ Header Variables inside the response message:
 |`CamelHazelcastCacheType` |`String` |the type of the cache - here multimap
 |=======================================================================
 
-[[HazelcastComponent-UsageofQueue]]
-Usage of Queue
-^^^^^^^^^^^^^^
+### Usage of Queue
 
-[[HazelcastComponent-Queueproducer]]
-Queue producer – to(“hazelcast:queue:foo”)
-++++++++++++++++++++++++++++++++++++++++++
+#### Queue producer – to(“hazelcast:queue:foo”)
 
 The queue producer provides 6 operations (add, put, poll, peek, offer,
 removevalue).
@@ -660,9 +638,7 @@ from("direct:removevalue")
 .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
 --------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-Queueconsumer]]
-Queue consumer – from(“hazelcast:queue:foo”)
-++++++++++++++++++++++++++++++++++++++++++++
+#### Queue consumer – from(“hazelcast:queue:foo”)
 
 The queue consumer provides 2 operations (add, remove).
 
@@ -683,13 +659,9 @@ fromF("hazelcast:%smm", HazelcastConstants.QUEUE_PREFIX)
 
 [[HazelcastComponent-topic]]
 
-[[HazelcastComponent-UsageofTopic]]
-Usage of Topic
-^^^^^^^^^^^^^^
+### Usage of Topic
 
-[[HazelcastComponent-Topicproducer]]
-Topic producer – to(“hazelcast:topic:foo”)
-++++++++++++++++++++++++++++++++++++++++++
+#### Topic producer – to(“hazelcast:topic:foo”)
 
 The topic producer provides only one operation (publish).
 
@@ -703,9 +675,7 @@ from("direct:add")
 .toF("hazelcast:%sbar", HazelcastConstants.PUBLISH_OPERATION);
 ----------------------------------------------------------------------------------------
 
-[[HazelcastComponent-Topicconsumer]]
-Topic consumer – from(“hazelcast:topic:foo”)
-++++++++++++++++++++++++++++++++++++++++++++
+#### Topic consumer – from(“hazelcast:topic:foo”)
 
 The topic consumer provides only one operation (received). This
 component is supposed to support multiple consumption as it's expected
@@ -724,13 +694,9 @@ fromF("hazelcast:%sfoo", HazelcastConstants.TOPIC_PREFIX)
 
 Â 
 
-[[HazelcastComponent-UsageofList]]
-Usage of List
-^^^^^^^^^^^^^
+### Usage of List
 
-[[HazelcastComponent-Listproducer]]
-List producer – to(“hazelcast:list:foo”)
-++++++++++++++++++++++++++++++++++++++++
+#### List producer – to(“hazelcast:list:foo”)
 
 The list producer provides 4 operations (add, addAll, set, get,
 removevalue, removeAll, clear).
@@ -779,9 +745,7 @@ from("direct:removevalue")
 Note that *CamelHazelcastObjectIndex* header is used for indexing
 purpose.
 
-[[HazelcastComponent-Thelistconsumerprovides2operationsListconsumer]]
-The list consumer provides 2 operations (add, remove).List consumer – from(“hazelcast:list:foo”)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### The list consumer provides 2 operations (add, remove).List consumer – from(“hazelcast:list:foo”)
 
 [source,java]
 -----------------------------------------------------------------------------------------------
@@ -798,17 +762,13 @@ fromF("hazelcast:%smm", HazelcastConstants.LIST_PREFIX)
                         .log("fail!");
 -----------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-UsageofSEDA]]
-Usage of SEDA
-^^^^^^^^^^^^^
+### Usage of SEDA
 
 SEDA component differs from the rest components provided. It implements
 a work-queue in order to support asynchronous SEDA architectures,
 similar to the core "SEDA" component.
 
-[[HazelcastComponent-SEDAproducer]]
-SEDA producer – to(“hazelcast:seda:foo”)
-++++++++++++++++++++++++++++++++++++++++
+#### SEDA producer – to(“hazelcast:seda:foo”)
 
 The SEDA producer provides no operations. You only send data to the
 specified queue.
@@ -839,9 +799,7 @@ Spring DSL :
 </route>
 ----------------------------------
 
-[[HazelcastComponent-SEDAconsumer]]
-SEDA consumer – from(“hazelcast:seda:foo”)
-++++++++++++++++++++++++++++++++++++++++++
+#### SEDA consumer – from(“hazelcast:seda:foo”)
 
 The SEDA consumer provides no operations. You only retrieve data from
 the specified queue.
@@ -889,15 +847,11 @@ Spring DSL:
 </route>
 -----------------------------------
 
-[[HazelcastComponent-UsageofAtomicNumber]]
-Usage of Atomic Number
-^^^^^^^^^^^^^^^^^^^^^^
+### Usage of Atomic Number
 
 * There is no consumer for this endpoint! *
 
-[[HazelcastComponent-atomicnumberproducer]]
-atomic number producer - to("hazelcast:atomicnumber:foo")
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### atomic number producer - to("hazelcast:atomicnumber:foo")
 
 An atomic number is an object that simply provides a grid wide number
 (long). The operations for this producer are setvalue (set the number
@@ -1054,15 +1008,11 @@ Spring DSL:
 </route>
 -----------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-clustersupport]]
-cluster support
-^^^^^^^^^^^^^^^
+### cluster support
 
 * This endpoint provides no producer! *
 
-[[HazelcastComponent-instanceconsumer-from]]
-instance consumer - from("hazelcast:instance:foo")
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### instance consumer - from("hazelcast:instance:foo")
 
 Hazelcast makes sense in one single "server node", but it's extremly
 powerful in a clustered environment. The instance consumer fires if a
@@ -1103,13 +1053,9 @@ Header Variables inside the response message:
 |`CamelHazelcastInstancePort` |`Integer` |port number of the instance
 |=======================================================================
 
-[[HazelcastComponent-Usinghazelcastreference]]
-Using hazelcast reference
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using hazelcast reference
 
-[[HazelcastComponent-Byitsname]]
-By its name
-+++++++++++
+#### By its name
 
 [source,xml]
 --------------------------------------------------------------------------------------------------------
@@ -1144,9 +1090,7 @@ By its name
 </camelContext>
 --------------------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-Byinstance]]
-By instance
-+++++++++++
+#### By instance
 
 [source,xml]
 ------------------------------------------------------------------------------
@@ -1176,18 +1120,14 @@ By instance
 </camelContext>
 ------------------------------------------------------------------------------
 
-[[HazelcastComponent-PublishinghazelcastinstanceasanOSGIservice]]
-Publishing hazelcast instance as an OSGI service
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Publishing hazelcast instance as an OSGI service
 
 If operating in an OSGI container and you would want to use one instance
 of hazelcast across all bundles in the same container. You can publish
 the instance as an OSGI service and bundles using the cache al need is
 to reference the service in the hazelcast endpoint.
 
-[[HazelcastComponent-BundleAcreateaninstanceandpublishesitasanOSGIservice]]
-Bundle A create an instance and publishes it as an OSGI service
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Bundle A create an instance and publishes it as an OSGI service
 
 Â 
 
@@ -1205,9 +1145,7 @@ Bundle A create an instance and publishes it as an OSGI service
 <service ref="hazelcastInstance" interface="com.hazelcast.core.HazelcastInstance" />
 --------------------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-BundleBusestheinstance]]
-Bundle B uses the instance
-++++++++++++++++++++++++++
+#### Bundle B uses the instance
 
 [source,xml]
 --------------------------------------------------------------------------------------
@@ -1234,15 +1172,11 @@ Bundle B uses the instance
 </camelContext>
 --------------------------------------------------------------------------------------
 
-[[HazelcastComponent-UsageofReplicatedmap]]
-Usage of Replicated map
-^^^^^^^^^^^^^^^^^^^^^^^
+### Usage of Replicated map
 
 *Avalaible from Camel 2.16*
 
-[[HazelcastComponent-replicatedmapcacheproducer]]
-replicatedmap cache producer
-++++++++++++++++++++++++++++
+#### replicatedmap cache producer
 
 A replicated map is a weakly consistent, distributed key-value data
 structure with no data partition. The replicatedmap producer provides 4
@@ -1349,9 +1283,7 @@ you can call them in your test class with:
 template.sendBodyAndHeader("direct:[put|get|delete|clear]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
 ------------------------------------------------------------------------------------------------------------
 
-[[HazelcastComponent-replicatedmapcacheconsumer]]
-replicatedmap cache consumer
-++++++++++++++++++++++++++++
+#### replicatedmap cache consumer
 
 For the multimap cache this component provides the same listeners /
 variables as for the map cache consumer (except the update and enviction
@@ -1395,15 +1327,11 @@ Header Variables inside the response message:
 |`CamelHazelcastCacheType` |`String` |the type of the cache - here replicatedmap
 |=======================================================================
 
-[[HazelcastComponent-UsageofRingbuffer]]
-Usage of Ringbuffer
-^^^^^^^^^^^^^^^^^^^
+### Usage of Ringbuffer
 
 *Avalaible from Camel 2.16*
 
-[[HazelcastComponent-ringbuffercacheproducer]]
-ringbuffer cache producer
-+++++++++++++++++++++++++
+#### ringbuffer cache producer
 
 Ringbuffer is a distributed data structure where the data is stored in a
 ring-like structure. You can think of it as a circular array with a
@@ -1459,4 +1387,4 @@ from("direct:get")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.READ_ONCE_HEAD_OPERATION))
 .toF("hazelcast:%sbar", HazelcastConstants.RINGBUFFER_PREFIX)
 .to("seda:out");
------------------------------------------------------------------------------------------------
+-----------------------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hbase/src/main/docs/hbase-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hbase/src/main/docs/hbase-component.adoc b/components/camel-hbase/src/main/docs/hbase-component.adoc
index e9caa6a..dfaa3ba 100644
--- a/components/camel-hbase/src/main/docs/hbase-component.adoc
+++ b/components/camel-hbase/src/main/docs/hbase-component.adoc
@@ -1,4 +1,4 @@
-# HBase Component
+## HBase Component
 
 *Available as of Camel 2.10*
 
@@ -18,9 +18,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[hbase-ApacheHBaseOverview]]
-Apache HBase Overview
-^^^^^^^^^^^^^^^^^^^^^
+### Apache HBase Overview
 
 HBase is an open-source, distributed, versioned, column-oriented store
 modeled after Google's Bigtable: A Distributed Storage System for
@@ -28,9 +26,7 @@ Structured Data. You can use HBase when you need random, realtime
 read/write access to your Big Data. More information at
 http://hbase.apache.org[Apache HBase].
 
-[[hbase-CamelandHBase]]
-Camel and HBase
-^^^^^^^^^^^^^^^
+### Camel and HBase
 
 When using a datasotre inside a camel route, there is always the
 chalenge of specifying how the camel message will stored to the
@@ -59,9 +55,7 @@ Regardless of the mapping strategy camel-hbase will convert a message
 into an org.apache.camel.component.hbase.model.HBaseData object and use
 that object for its internal operations.
 
-[[hbase-Configuringthecomponent]]
-Configuring the component
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Configuring the component
 
 The HBase component can be provided a custom HBaseConfiguration object
 as a property or it can create an HBase configuration object on its own
@@ -81,9 +75,7 @@ You can find more information about how to configure HBase clients at:
 http://archive.apache.org/dist/hbase/docs/client_dependencies.html[HBase
 client configuration and dependencies]
 
-[[hbase-HBaseProducer]]
-HBase Producer
-^^^^^^^^^^^^^^
+### HBase Producer
 
 As mentioned above camel provides produers endpoints for HBase. This
 allows you to store, delete, retrieve or query data from HBase using
@@ -103,9 +95,7 @@ The supported operations are:
 * Delete
 * Scan
 
-[[hbase-SupportedURIoptions]]
-Supported URI options
-+++++++++++++++++++++
+#### Supported URI options
 
 
 
@@ -160,9 +150,7 @@ The HBase component supports 17 endpoint options which are listed below:
 
 
 
-[[hbase-PutOperations.]]
-Put Operations.
-+++++++++++++++
+#### Put Operations.
 
 HBase is a column based store, which allows you to store data into a
 specific column of a specific row. Columns are grouped into families, so
@@ -226,9 +214,7 @@ headers or a combination of both. It is recommended to specify constants
 as part of the uri and dynamic values as headers. If something is
 defined both as header and as part of the uri, the header will be used.
 
-[[hbase-GetOperations.]]
-Get Operations.
-+++++++++++++++
+#### Get Operations.
 
 A Get Operation is an operation that is used to retrieve one or more
 values from a specified HBase row. To specify what are the values that
@@ -251,9 +237,7 @@ message headers.
 In the example above the result of the get operation will be stored as a
 header with name CamelHBaseValue.
 
-[[hbase-DeleteOperations.]]
-Delete Operations.
-++++++++++++++++++
+#### Delete Operations.
 
 You can also you camel-hbase to perform HBase delete operation. The
 delete operation will remove an entire row. All that needs to be
@@ -271,9 +255,7 @@ specified is one or more rows as part of the message headers.
         </route>
 ----------------------------------------------------------------
 
-[[hbase-ScanOperations.]]
-Scan Operations.
-++++++++++++++++
+#### Scan Operations.
 
 A scan operation is the equivalent of a query in HBase. You can use the
 scan operation to retrieve multiple rows. To specify what columns should
@@ -354,9 +336,7 @@ and will pass that model the the ModelAwareColumnMatchingFilter. The
 filter will filter out any rows, that do not contain columns that match
 the model. It is like query by example.
 
-[[hbase-HBaseConsumer]]
-HBase Consumer
-^^^^^^^^^^^^^^
+### HBase Consumer
 
 The Camel HBase Consumer, will perform repeated scan on the specified
 HBase table and will return the scan results as part of the message. You
@@ -382,9 +362,7 @@ specified fields and the scan results will populate the model object
 with values. Finally the mapping strategy will be used to map this model
 to the camel message.
 
-[[hbase-HBaseIdempotentrepository]]
-HBase Idempotent repository
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HBase Idempotent repository
 
 The camel-hbase component also provides an idempotent repository which
 can be used when you want to make sure that each message is processed
@@ -402,18 +380,14 @@ from("direct:in")
   .to("log:out);
 ------------------------------------------------------------------------------------------------------------------
 
-[[hbase-HBaseMapping]]
-HBase Mapping
-^^^^^^^^^^^^^
+### HBase Mapping
 
 It was mentioned above that you the default mapping strategies are
 *header* and *body* mapping. +
  Below you can find some detailed examples of how each mapping strategy
 works.
 
-[[hbase-HBaseHeadermappingExamples]]
-HBase Header mapping Examples
-+++++++++++++++++++++++++++++
+#### HBase Header mapping Examples
 
 The header mapping is the default mapping.
  To put the value "myvalue" into HBase row "myrow" and column
@@ -475,9 +449,7 @@ Please note that in order to avoid boilerplate headers that are
 considered constant for all messages, you can also specify them as part
 of the endpoint uri, as you will see below.
 
-[[hbase-BodymappingExamples]]
-Body mapping Examples
-+++++++++++++++++++++
+#### Body mapping Examples
 
 In order to use the body mapping strategy you will have to specify the
 option mappingStrategy as part of the uri, for example:
@@ -510,10 +482,7 @@ myvalue to the column myfamily:myqualifier. +
 advantage it has over the header mapping strategy is that the HBaseData
 object can be easily converted to or from xml/json.
 
-[[hbase-Seealso]]
-See also
-^^^^^^^^
+### See also
 
 * link:polling-consumer.html[Polling Consumer]
-* http://hbase.apache.org[Apache HBase]
-
+* http://hbase.apache.org[Apache HBase]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hdfs/src/main/docs/hdfs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hdfs/src/main/docs/hdfs-component.adoc b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
index eb420d2..97170fb 100644
--- a/components/camel-hdfs/src/main/docs/hdfs-component.adoc
+++ b/components/camel-hdfs/src/main/docs/hdfs-component.adoc
@@ -1,4 +1,4 @@
-# HDFS Component
+## HDFS Component
 
 *Available as of Camel 2.8*
 
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[HDFS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ---------------------------------------
@@ -51,9 +49,7 @@ fileMode=Append to append each of the chunks together.
 
 Â 
 
-[[HDFS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -134,9 +130,7 @@ The HDFS component supports 41 endpoint options which are listed below:
 
 
 
-[[HDFS-KeyTypeandValueType]]
-KeyType and ValueType
-+++++++++++++++++++++
+#### KeyType and ValueType
 
 * NULL it means that the key or the value is absent
 * BYTE for writing a byte, the java Byte class is mapped into a BYTE
@@ -152,9 +146,7 @@ BYTES is also used with everything else, for example, in Camel a file is
 sent around as an InputStream, int this case is written in a sequence
 file or a map file as a sequence of bytes.
 
-[[HDFS-SplittingStrategy]]
-Splitting Strategy
-^^^^^^^^^^^^^^^^^^
+### Splitting Strategy
 
 In the current version of Hadoop opening a file in append mode is
 disabled since it's not very reliable. So, for the moment, it's only
@@ -197,15 +189,11 @@ than 1 second or if more than 5 bytes have been written. So, running
 `hadoop fs -ls /tmp/simple-file` you'll see that multiple files have
 been created.
 
-[[HDFS-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The following headers are supported by this component:
 
-[[HDFS-Produceronly]]
-Producer only
-+++++++++++++
+#### Producer only
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -217,9 +205,7 @@ link:expression.html[Expression] object. Only relevant when not using a
 split strategy.
 |=======================================================================
 
-[[HDFS-Controllingtoclosefilestream]]
-Controlling to close file stream
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling to close file stream
 
 *Available as of Camel 2.10.4*
 
@@ -234,9 +220,7 @@ the stream should be closed or not.
 Notice this does not apply if you use a split strategy, as there are
 various strategies that can control when the stream is closed.
 
-[[HDFS-UsingthiscomponentinOSGi]]
-Using this component in OSGi
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using this component in OSGi
 
 This component is fully functional in an OSGi environment, however, it
 requires some actions from the user. Hadoop uses the thread context
@@ -245,4 +229,4 @@ classloader will be the bundle class loader of the bundle that contains
 the routes. So, the default configuration files need to be visible from
 the bundle class loader. A typical way to deal with it is to keep a copy
 of core-default.xml in your bundle root. That file can be found in the
-hadoop-common.jar.
+hadoop-common.jar.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc b/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
index e9ec68d..e08eb49 100644
--- a/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
+++ b/components/camel-hdfs2/src/main/docs/hdfs2-component.adoc
@@ -1,4 +1,4 @@
-# HDFS2 Component
+## HDFS2 Component
 
 *Available as of Camel 2.13*
 
@@ -19,9 +19,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[HDFS2-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ----------------------------------------
@@ -48,9 +46,7 @@ chunk using the chunkSize option. If you want to read from hdfs and
 write to a regular file using the file component, then you can use the
 fileMode=Append to append each of the chunks together.
 
-[[HDFS2-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -130,9 +126,7 @@ The HDFS2 component supports 41 endpoint options which are listed below:
 
 
 
-[[HDFS2-KeyTypeandValueType]]
-KeyType and ValueType
-+++++++++++++++++++++
+#### KeyType and ValueType
 
 * NULL it means that the key or the value is absent
 * BYTE for writing a byte, the java Byte class is mapped into a BYTE
@@ -148,9 +142,7 @@ BYTES is also used with everything else, for example, in Camel a file is
 sent around as an InputStream, int this case is written in a sequence
 file or a map file as a sequence of bytes.
 
-[[HDFS2-SplittingStrategy]]
-Splitting Strategy
-^^^^^^^^^^^^^^^^^^
+### Splitting Strategy
 
 In the current version of Hadoop opening a file in append mode is
 disabled since it's not very reliable. So, for the moment, it's only
@@ -190,15 +182,11 @@ than 1 second or if more than 5 bytes have been written. So, running
 `hadoop fs -ls /tmp/simple-file` you'll see that multiple files have
 been created.
 
-[[HDFS2-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The following headers are supported by this component:
 
-[[HDFS2-Produceronly]]
-Producer only
-+++++++++++++
+#### Producer only
 
 [width="100%",cols="10%,90%",options="header",]
 |=======================================================================
@@ -210,9 +198,7 @@ link:expression.html[Expression] object. Only relevant when not using a
 split strategy.
 |=======================================================================
 
-[[HDFS2-Controllingtoclosefilestream]]
-Controlling to close file stream
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Controlling to close file stream
 
 When using the link:hdfs2.html[HDFS2] producer *without* a split
 strategy, then the file output stream is by default closed after the
@@ -225,9 +211,7 @@ the stream should be closed or not.
 Notice this does not apply if you use a split strategy, as there are
 various strategies that can control when the stream is closed.
 
-[[HDFS2-UsingthiscomponentinOSGi]]
-Using this component in OSGi
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using this component in OSGi
 
 There are some quirks when running this component in an OSGi environment
 related to the mechanism Hadoop 2.x uses to discover different
@@ -242,9 +226,7 @@ be visible from the bundle class loader. A typical way to deal with it
 is to keep a copy of `core-default.xml` (and e.g., `hdfs-default.xml`)
 in your bundle root.
 
-[[HDFS2-Usingthiscomponentwithmanuallydefinedroutes]]
-Using this component with manually defined routes
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Using this component with manually defined routes
 
 There are two options:
 
@@ -265,9 +247,7 @@ FileSystem.get("hdfs://localhost:9000/", conf);
 ...
 ----------------------------------------------------------------------------------------------------
 
-[[HDFS2-UsingthiscomponentwithBlueprintcontainer]]
-Using this component with Blueprint container
-+++++++++++++++++++++++++++++++++++++++++++++
+#### Using this component with Blueprint container
 
 Two options:
 
@@ -291,4 +271,4 @@ resource with bundle that contains blueprint definition.
 ------------------------------------------------------------------------------------------------------
 
 This way Hadoop 2.x will have correct mapping of URI schemes to
-filesystem implementations.
+filesystem implementations.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hessian/src/main/docs/hessian-dataformat.adoc b/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
index b2b7abb..a42c9c8 100644
--- a/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
+++ b/components/camel-hessian/src/main/docs/hessian-dataformat.adoc
@@ -1,4 +1,4 @@
-# Hessian DataFormat
+## Hessian DataFormat
 
 Hessian is Data Format for marshalling and unmarshalling messages using Caucho's Hessian format.
 
@@ -14,9 +14,7 @@ If you want to use Hessian Data Format from Maven, add the following dependency
 </dependency>
 ------------------------------------------------------------
 
-[[HessianDataFormat-Options]]
-Options
-^^^^^^^
+### Options
 
 // dataformat options: START
 The Hessian dataformat supports 1 options which are listed below.
@@ -32,9 +30,7 @@ The Hessian dataformat supports 1 options which are listed below.
 {% endraw %}
 // dataformat options: END
 
-[[hessian-UsingHessianDataFormat]]
-Using the Hessian data format in Java DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Hessian data format in Java DSL
 
 [source,java]
 --------------------------------------------------------------------------------
@@ -42,9 +38,7 @@ Using the Hessian data format in Java DSL
         .marshal().hessian();
 --------------------------------------------------------------------------------
 
-[[hessian-UsingHessianDataFormatXml]]
-Using the Hessian data format in Spring DSL
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using the Hessian data format in Spring DSL
 
 [source,xml]
 --------------------------------------------------------------------------------
@@ -54,4 +48,4 @@ Using the Hessian data format in Spring DSL
             <marshal ref="hessian"/>
         </route>
     </camelContext>
---------------------------------------------------------------------------------
+--------------------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hipchat/src/main/docs/hipchat-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hipchat/src/main/docs/hipchat-component.adoc b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
index 067aef7..063a165 100644
--- a/components/camel-hipchat/src/main/docs/hipchat-component.adoc
+++ b/components/camel-hipchat/src/main/docs/hipchat-component.adoc
@@ -1,4 +1,4 @@
-# Hipchat Component
+## Hipchat Component
 
 *Available as of Camel 2.15.0*
 
@@ -12,9 +12,7 @@ https://www.hipchat.com/account/api[personal access token] that you can
 use to produce/consume messages.
 
 
-[[Hipchat-URIFormat]]
-URI Format
-^^^^^^^^^^
+### URI Format
 
 [source,java]
 -------------------------------
@@ -24,9 +22,7 @@ hipchat://[host][:port]?options
 You can append query options to the URI in the following format,
 ?options=value&option2=value&...
 
-[[Hipchat-URIOptions]]
-URI Options
-^^^^^^^^^^^
+### URI Options
 
 
 // component options: START
@@ -78,9 +74,7 @@ The Hipchat component supports 24 endpoint options which are listed below:
 
 
 
-[[Hipchat-ScheduledPollConsumer]]
-Scheduled Poll Consumer
-^^^^^^^^^^^^^^^^^^^^^^^
+### Scheduled Poll Consumer
 
 This component implements the
 link:polling-consumer.html[ScheduledPollConsumer]. Only the last message
@@ -105,9 +99,7 @@ public void configure() throws Exception {
 }
 ---------------------------------------------------------------------------------
 
-[[Hipchat-MessageheaderssetbytheHipchatconsumer]]
-Message headers set by the Hipchat consumer
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Hipchat consumer
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -124,9 +116,7 @@ Hipchat https://www.hipchat.com/docs/apiv2/method/view_recent_privatechat_histor
 The status of the API response received.
 |=======================================================================
 
-[[Hipchat-HipchatProducer]]
-Hipchat Producer
-^^^^^^^^^^^^^^^^
+### Hipchat Producer
 
 Producer can send messages to both Room's and User's simultaneously. The
 body of the exchange is sent as message. Sample usage is shown below.
@@ -143,9 +133,7 @@ Appropriate headers needs to be set.
  }
 ----------------------------------------------------------
 
-[[Hipchat-MessageheadersevaluatedbytheHipchatproducer]]
-Message headers evaluated by the Hipchat producer
-+++++++++++++++++++++++++++++++++++++++++++++++++
+#### Message headers evaluated by the Hipchat producer
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -166,9 +154,7 @@ a user notification (change the tab color, play a sound, notify mobile
 phones, etc). *Default: 'false' (Room Only)*
 |=======================================================================
 
-[[Hipchat-MessageheaderssetbytheHipchatproducer]]
-Message headers set by the Hipchat producer
-+++++++++++++++++++++++++++++++++++++++++++
+#### Message headers set by the Hipchat producer
 
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
@@ -181,9 +167,7 @@ The status of the API response received when message sent to the user.
 |HipchatFromUserResponseStatus |HipchatConstants.TO_ROOM_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_ |The status of the API response received when message sent to the room.
 |=======================================================================
 
-[[Hipchat-Dependencies]]
-Dependencies
-++++++++++++
+#### Dependencies
 
 Maven users will need to add the following dependency to their pom.xml.
 
@@ -199,4 +183,4 @@ Maven users will need to add the following dependency to their pom.xml.
 ------------------------------------------
 
 where `${camel-version}` must be replaced by the actual version of Camel
-(2.15.0 or higher)
+(2.15.0 or higher)
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
index cbdfcb1..6691468 100644
--- a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
+++ b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
@@ -1,4 +1,4 @@
-# HL7 DataFormat
+## HL7 DataFormat
 
 The *HL7* component is used for working with the HL7 MLLP protocol and
 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=185[HL7
@@ -26,9 +26,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[HL7-HL7MLLPprotocol]]
-HL7 MLLP protocol
-^^^^^^^^^^^^^^^^^
+### HL7 MLLP protocol
 
 HL7 is often used with the HL7 MLLP protocol, which is a text based TCP
 socket based protocol. This component ships with a Mina and Netty4 Codec
@@ -66,9 +64,7 @@ the HL7 message content.
 segment terminators. The HAPI library requires the use of `\r`.
 |=======================================================================
 
-[[HL7-ExposinganHL7listenerusingMina]]
-Exposing an HL7 listener using Mina
-+++++++++++++++++++++++++++++++++++
+#### Exposing an HL7 listener using Mina
 
 In the Spring XML file, we configure a mina2 endpoint to listen for HL7
 requests using TCP on port `8888`:
@@ -128,9 +124,7 @@ public class PatientLookupService {
     }
 ----------------------------------------------------------------------------------------------------
 
-[[HL7-ExposinganHL7listenerusingNetty]]
-Exposing an HL7 listener using Netty (available from Camel 2.15 onwards)
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Exposing an HL7 listener using Netty (available from Camel 2.15 onwards)
 
 In the Spring XML file, we configure a netty4 endpoint to listen for HL7
 requests using TCP on port `8888`:
@@ -160,9 +154,7 @@ consumer, as this Java DSL example illustrates:
     from("hl7NettyListener").beanRef("patientLookupService");
 -------------------------------------------------------------
 
-[[HL7-HL7Modelusingjava.lang.Stringorbyte]]
-HL7 Model using java.lang.String or byte[]
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Model using java.lang.String or byte[]
 
 The HL7 MLLP codec uses plain String as its data format. Camel uses its
 link:type-converter.html[Type Converter] to convert to/from strings to
@@ -174,9 +166,7 @@ plain `byte[]` as its data format by setting the `produceString`
 property to false. The Type Converter is also capable of converting
 the `byte[]` to/from HAPI HL7 model objects.
 
-[[HL7-HL7v2ModelusingHAPI]]
-HL7v2 Model using HAPI
-^^^^^^^^^^^^^^^^^^^^^^
+### HL7v2 Model using HAPI
 
 The HL7v2 model uses Java objects from the HAPI library. Using this
 library, you can encode and decode from the EDI format (ER7) that is
@@ -212,9 +202,7 @@ QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class);
 String patientId = msg.getQRD().getWhoSubjectFilter(0).getIDNumber().getValue();
 --------------------------------------------------------------------------------
 
-[[HL7-HL7DataFormat]]
-HL7 DataFormat
-^^^^^^^^^^^^^^
+### HL7 DataFormat
 
 The link:hl7.html[HL7] component ships with a HL7 data format that can
 be used to marshal or unmarshal HL7 model objects.
@@ -300,9 +288,7 @@ object:
   from("jms:queue:hl7out").unmarshal().hl7().to("patientLookupService");
 ------------------------------------------------------------------------
 
-[[HL7-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 The unmarshal operation adds these fields from the MSH segment as
 headers on the Camel message:
@@ -343,9 +329,7 @@ that was used to parse the message
 All headers except `CamelHL7Context `are `String` types. If a header
 value is missing, its value is `null`.
 
-[[HL7-Options]]
-Options
-^^^^^^^
+### Options
 
 The HL7 Data Format supports the following options:
 
@@ -369,9 +353,7 @@ custom ValidationContext etc. This gives you full control over the HL7
 parsing and rendering process.
 |=======================================================================
 
-[[HL7-Dependencies]]
-Dependencies
-^^^^^^^^^^^^
+### Dependencies
 
 To use HL7 in your Camel routes you'll need to add a dependency on
 *camel-hl7* listed above, which implements this data format.
@@ -434,9 +416,7 @@ repository].
 </dependency>
 -------------------------------------------
 
-[[HL7-Terserlanguage]]
-Terser language
-^^^^^^^^^^^^^^^
+### Terser language
 
 http://hl7api.sourceforge.net[HAPI] provides a
 http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
@@ -463,9 +443,7 @@ import static org.apache.camel.component.hl7.HL7.terser;
       .to("mock:test2");
 --------------------------------------------------------------------------------------------------
 
-[[HL7-HL7Validationpredicate]]
-HL7 Validation predicate
-^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Validation predicate
 
 Often it is preferable to first parse a HL7v2 message and in a separate
 step validate it against a HAPI
@@ -488,9 +466,7 @@ import ca.uhn.hl7v2.validation.impl.DefaultValidation;
       .to("mock:test1");
 ----------------------------------------------------------------------
 
-[[HL7-HL7ValidationpredicateusingtheHapiContext]]
-HL7 Validation predicate using the HapiContext (Camel 2.14)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Validation predicate using the HapiContext (Camel 2.14)
 
 The HAPI Context is always configured with a
 http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/validation/ValidationContext.html[ValidationContext]
@@ -533,9 +509,7 @@ import static org.apache.camel.component.hl7.HL7.messageConforms
 
 Â 
 
-[[HL7-HL7Acknowledgementexpression]]
-HL7 Acknowledgement expression
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HL7 Acknowledgement expression
 
 A common task in HL7v2 processing is to generate an acknowledgement
 message as response to an incoming HL7v2 message, e.g. based on a
@@ -564,9 +538,7 @@ import ca.uhn.hl7v2.validation.impl.DefaultValidation;
       .transform(ack())
 ------------------------------------------------------------------------------------------
 
-[[HL7-MoreSamples]]
-More Samples
-^^^^^^^^^^^^
+### More Samples
 
 In the following example, a plain `String` HL7 request is sent to an HL7
 listener that sends back a response:
@@ -584,12 +556,9 @@ the example above.
 
 Â 
 
-[[HL7-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
+* link:getting-started.html[Getting Started]
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-hl7/src/main/docs/terser-language.adoc
----------------------------------------------------------------------
diff --git a/components/camel-hl7/src/main/docs/terser-language.adoc b/components/camel-hl7/src/main/docs/terser-language.adoc
index c176659..8d9e340 100644
--- a/components/camel-hl7/src/main/docs/terser-language.adoc
+++ b/components/camel-hl7/src/main/docs/terser-language.adoc
@@ -1,7 +1,5 @@
-# HL7 Terser Language
-[[HL7-Terserlanguage]]
-Terser language
-^^^^^^^^^^^^^^^
+## HL7 Terser Language
+### Terser language
 
 http://hl7api.sourceforge.net[HAPI] provides a
 http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/util/Terser.html[Terser]
@@ -28,9 +26,7 @@ import static org.apache.camel.component.hl7.HL7.terser;
       .to("mock:test2");
 --------------------------------------------------------------------------------------------------
 
-[[HL7-Terserlanguage-options]]
-Terser Language options
-^^^^^^^^^^^^^^^^^^^^^^^
+### Terser Language options
 
 // language options: START
 The HL7 Terser language supports 1 options which are listed below.
@@ -44,5 +40,4 @@ The HL7 Terser language supports 1 options which are listed below.
 | trim | true | Boolean | Whether to trim the value to remove leading and trailing whitespaces and line breaks
 |=======================================================================
 {% endraw %}
-// language options: END
-
+// language options: END
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-http/src/main/docs/http-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-http/src/main/docs/http-component.adoc b/components/camel-http/src/main/docs/http-component.adoc
index f1fe9a5..4f404ee 100644
--- a/components/camel-http/src/main/docs/http-component.adoc
+++ b/components/camel-http/src/main/docs/http-component.adoc
@@ -1,4 +1,4 @@
-# HTTP Component
+## HTTP Component
 
 The *http:* component provides HTTP based link:endpoint.html[endpoints]
 for consuming external HTTP resources (as a client to call external
@@ -17,9 +17,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[HTTP-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 ------------------------------------------------------------------
@@ -37,9 +35,7 @@ route, you can use the link:jetty.html[Jetty Component] or the
 link:servlet.html[Servlet Component]
 
 
-[[HTTP-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
 Call the url with the body using POST and return response as out
 message. If body is null call URL using GET and return response as out
@@ -110,9 +106,7 @@ from("direct:start")
 <to uri="mock:results"/>
 ----------------------------------------
 
-[[HTTP-HttpOptions]]
-Http Options
-^^^^^^^^^^^^
+### Http Options
 
 
 
@@ -186,9 +180,7 @@ The HTTP component supports 26 endpoint options which are listed below:
 
 
 
-[[HTTP-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
+### Message Headers
 
 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
@@ -233,18 +225,14 @@ default value "HTTP/1.1"
 The header name above are constants. For the spring DSL you have to use
 the value of the constant instead of the name.
 
-[[HTTP-MessageBody]]
-Message Body
-^^^^^^^^^^^^
+### Message Body
 
 Camel will store the HTTP response from the external server on the OUT
 body. All headers from the IN message will be copied to the OUT message,
 so headers are preserved during routing. Additionally Camel will add the
 HTTP response headers as well to the OUT message headers.
 
-[[HTTP-Responsecode]]
-Response code
-^^^^^^^^^^^^^
+### Response code
 
 Camel will handle according to the HTTP response code:
 
@@ -264,9 +252,7 @@ codes. This allows you to get any response from the remote server. +
 There is a sample below demonstrating this.
 
 
-[[HTTP-HttpOperationFailedException]]
-HttpOperationFailedException
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### HttpOperationFailedException
 
 This exception contains the following information:
 
@@ -276,9 +262,7 @@ This exception contains the following information:
 * Response body as a `java.lang.String`, if server provided a body as
 response
 
-[[HTTP-CallingusingGETorPOST]]
-Calling using GET or POST
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Calling using GET or POST
 
 The following algorithm is used to determine if either `GET` or `POST`
 HTTP method should be used: +
@@ -288,9 +272,7 @@ HTTP method should be used: +
  4. `POST` if there is data to send (body is not null). +
  5. `GET` otherwise.
 
-[[HTTP-HowtogetaccesstoHttpServletRequestandHttpServletResponse]]
-How to get access to HttpServletRequest and HttpServletResponse
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to get access to HttpServletRequest and HttpServletResponse
 
 You can get access to these two using the Camel type converter system
 using
@@ -301,20 +283,14 @@ HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
 HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
 ----------------------------------------------------------------------------------
 
-[[HTTP-Usingclienttimeout-SO_TIMEOUT]]
-Using client timeout - SO_TIMEOUT
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using client timeout - SO_TIMEOUT
 
 See the unit test in
 http://svn.apache.org/viewvc?view=rev&revision=781775[this link]
 
-[[HTTP-MoreExamples]]
-More Examples
-~~~~~~~~~~~~~
+### More Examples
 
-[[HTTP-ConfiguringaProxy]]
-Configuring a Proxy
-^^^^^^^^^^^^^^^^^^^
+### Configuring a Proxy
 
 Java DSL
 
@@ -327,9 +303,7 @@ from("direct:start")
 There is also support for proxy authentication via the `proxyUsername`
 and `proxyPassword` options.
 
-[[HTTP-UsingproxysettingsoutsideofURI]]
-Using proxy settings outside of URI
-+++++++++++++++++++++++++++++++++++
+#### Using proxy settings outside of URI
 
 Java DSL
 
@@ -353,9 +327,7 @@ Spring DSL
 
 Options on Endpoint will override options on the context.
 
-[[HTTP-Configuringcharset]]
-Configuring charset
-^^^^^^^^^^^^^^^^^^^
+### Configuring charset
 
 If you are using `POST` to send data you can configure the `charset`
 
@@ -364,9 +336,7 @@ If you are using `POST` to send data you can configure the `charset`
 setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
 -------------------------------------------------
 
-[[HTTP-Samplewithscheduledpoll]]
-Sample with scheduled poll
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Sample with scheduled poll
 
 The sample polls the Google homepage every 10 seconds and write the page
 to the file `message.html`:
@@ -378,9 +348,7 @@ from("timer://foo?fixedRate=true&delay=0&period=10000")
     .setHeader(FileComponent.HEADER_FILE_NAME, "message.html").to("file:target/google");
 ----------------------------------------------------------------------------------------
 
-[[HTTP-GettingtheResponseCode]]
-Getting the Response Code
-^^^^^^^^^^^^^^^^^^^^^^^^^
+### Getting the Response Code
 
 You can get the HTTP response code from the HTTP component by getting
 the value from the Out message header with
@@ -397,9 +365,7 @@ the value from the Out message header with
    int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);
 ----------------------------------------------------------------------------------------------
 
-[[HTTP-UsingthrowExceptionOnFailure=falsetogetanyresponseback]]
-Using `throwExceptionOnFailure=false` to get any response back
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Using `throwExceptionOnFailure=false` to get any response back
 
 In the route below we want to route a message that we
 link:content-enricher.html[enrich] with data returned from a remote HTTP
@@ -408,25 +374,19 @@ call. As we want any response from the remote server, we set the
 the `AggregationStrategy`. As the code is based on a unit test that
 simulates a HTTP status code 404, there is some assertion code etc.
 
-[[HTTP-DisablingCookies]]
-Disabling Cookies
-^^^^^^^^^^^^^^^^^
+### Disabling Cookies
 
 To disable cookies you can set the HTTP Client to ignore cookies by
 adding this URI option: +
  `httpClient.cookiePolicy=ignoreCookies`
 
-[[HTTP-AdvancedUsage]]
-Advanced Usage
-^^^^^^^^^^^^^^
+### Advanced Usage
 
 If you need more control over the HTTP producer you should use the
 `HttpComponent` where you can set various classes to give you custom
 behavior.
 
-[[HTTP-SettingMaxConnectionsPerHost]]
-Setting MaxConnectionsPerHost
-+++++++++++++++++++++++++++++
+#### Setting MaxConnectionsPerHost
 
 The link:http.html[HTTP] Component has a
 `org.apache.commons.httpclient.HttpConnectionManager` where you can
@@ -445,9 +405,7 @@ connection to 5 instead of the default of 2.
 
 And then we can just use it as we normally do in our routes:
 
-[[HTTP-Usingpreemptiveauthentication]]
-Using preemptive authentication
-+++++++++++++++++++++++++++++++
+#### Using preemptive authentication
 
 An end user reported that he had problem with authenticating with HTTPS.
 The problem was eventually resolved when he discovered the HTTPS server
@@ -455,18 +413,14 @@ did not return a HTTP code 401 Authorization Required. The solution was
 to set the following URI option:
 `httpClient.authenticationPreemptive=true`
 
-[[HTTP-Acceptingselfsignedcertificatesfromremoteserver]]
-Accepting self signed certificates from remote server
-+++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Accepting self signed certificates from remote server
 
 See this
 http://www.nabble.com/Using-HTTPS-in-camel-http-when-remote-side-has-self-signed-cert-td25916878.html[link]
 from a mailing list discussion with some code to outline how to do this
 with the Apache Commons HTTP API.
 
-[[HTTP-SettingupSSLforHTTPClient]]
-Setting up SSL for HTTP Client
-++++++++++++++++++++++++++++++
+#### Setting up SSL for HTTP Client
 
 [[HTTP-UsingtheJSSEConfigurationUtility]]
 Using the JSSE Configuration Utility
@@ -559,14 +513,11 @@ If you are doing this using the Spring DSL, you can specify your
 As long as you implement the HttpClientConfigurer and configure your
 keystore and truststore as described above, it will work fine.
 
-[[HTTP-SeeAlso]]
-See Also
-^^^^^^^^
+### See Also
 
 * link:configuring-camel.html[Configuring Camel]
 * link:component.html[Component]
 * link:endpoint.html[Endpoint]
 * link:getting-started.html[Getting Started]
 
-* link:jetty.html[Jetty]
-
+* link:jetty.html[Jetty]
\ No newline at end of file

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[10/14] camel git commit: Use single line header for adoc files

davsclaus-2
In reply to this post by davsclaus-2
http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-cxf/src/main/docs/cxfrs-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-cxf/src/main/docs/cxfrs-component.adoc b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
index d3b9e7d..d3ffe40 100644
--- a/components/camel-cxf/src/main/docs/cxfrs-component.adoc
+++ b/components/camel-cxf/src/main/docs/cxfrs-component.adoc
@@ -1,4 +1,4 @@
-# CXF-RS Component
+## CXF-RS Component
 
 [Note]
 ====
@@ -29,9 +29,7 @@ for this component:
 </dependency>
 -------------------------------------------------------------------------------------
 
-[[CXFRS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------
@@ -55,9 +53,7 @@ For either style above, you can append options to the URI as follows:
 cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
 ------------------------------------------------------------------
 
-[[CXFRS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 
@@ -129,9 +125,7 @@ http://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/main/resour
 file] and https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAX-RS
 documentation] for more information.
 
-[[CXFRS-HowtoconfiguretheRESTendpointinCamel]]
-How to configure the REST endpoint in Camel
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to configure the REST endpoint in Camel
 
 In
 http://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/main/resources/schema/cxfEndpoint.xsd[camel-cxf
@@ -139,9 +133,7 @@ schema file], there are two elements for the REST endpoint definition.
 *cxf:rsServer* for REST consumer, *cxf:rsClient* for REST producer. +
  You can find a Camel REST service route configuration example here.
 
-[[CXFRS-HowtooverridetheCXFproduceraddressfrommessageheader]]
-How to override the CXF producer address from message header
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to override the CXF producer address from message header
 
 The `camel-cxfrs` producer supports to override the services address by
 setting the message with the key of "CamelDestinationOverrideUrl".
@@ -152,9 +144,7 @@ setting the message with the key of "CamelDestinationOverrideUrl".
  exchange.getIn().setHeader(Exchange.DESTINATION_OVERRIDE_URL, constant(getServiceAddress()));
 ----------------------------------------------------------------------------------------------
 
-[[CXFRS-ConsumingaRESTRequest-SimpleBindingStyle]]
-Consuming a REST Request - Simple Binding Style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming a REST Request - Simple Binding Style
 
 *Available as of Camel 2.11*
 
@@ -192,9 +182,7 @@ respected and it becomes the final response.
 * In all cases, Camel headers permitted by custom or default
 `HeaderFilterStrategy` are added to the HTTP response.
 
-[[CXFRS-EnablingtheSimpleBindingStyle]]
-Enabling the Simple Binding Style
-+++++++++++++++++++++++++++++++++
+#### Enabling the Simple Binding Style
 
 This binding style can be activated by setting the `bindingStyle`
 parameter in the consumer endpoint to value `SimpleConsumer`:
@@ -205,9 +193,7 @@ parameter in the consumer endpoint to value `SimpleConsumer`:
     .to("log:TEST?showAll=true");
 ---------------------------------------------------------
 
-[[CXFRS-Examplesofrequestbindingwithdifferentmethodsignatures]]
-Examples of request binding with different method signatures
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+#### Examples of request binding with different method signatures
 
 Below is a list of method signatures along with the expected result from
 the Simple binding.
@@ -239,9 +225,7 @@ as the IN message body.
  The DataHandler is unwrapped from the MessageContentsList and preserved
 as the IN message body.
 
-[[CXFRS-MoreexamplesoftheSimpleBindingStyle]]
-More examples of the Simple Binding Style
-+++++++++++++++++++++++++++++++++++++++++
+#### More examples of the Simple Binding Style
 
 Given a JAX-RS resource class with this method:
 
@@ -290,9 +274,7 @@ For more examples on how to process requests and write responses can be
 found
 https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/simplebinding/[here].
 
-[[CXFRS-ConsumingaRESTRequest-DefaultBindingStyle]]
-Consuming a REST Request - Default Binding Style
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Consuming a REST Request - Default Binding Style
 
 The https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAXRS front end]
 implements the https://jsr311.java.net/[JAX-RS (JSR-311) API], so we can
@@ -327,9 +309,7 @@ set on the Camel exchange and the route execution will continue as
 usual. This can be useful for integrating the existing JAX-RS implementations into Camel routes and
 for post-processing JAX-RS Responses in custom processors.
 
-[[CXFRS-HowtoinvoketheRESTservicethroughcamel-cxfrsproducer]]
-How to invoke the REST service through camel-cxfrs producer
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### How to invoke the REST service through camel-cxfrs producer
 
 The https://cwiki.apache.org/CXF20DOC/JAX-RS[CXF JAXRS front end]
 implements
@@ -367,4 +347,4 @@ Index: 20, Size: 20
 
 To support the Dynamical routing, you can override the URI's query
 parameters by using the CxfConstants.CAMEL_CXF_RS_QUERY_MAP header to
-set the parameter map for it.
+set the parameter map for it.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-disruptor/src/main/docs/disruptor-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-disruptor/src/main/docs/disruptor-component.adoc b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
index f3d7bce..7d67f52 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-component.adoc
@@ -1,4 +1,4 @@
-# Disruptor Component
+## Disruptor Component
 
 *Available as of Camel 2.12*
 
@@ -61,9 +61,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[Disruptor-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 [source,java]
 -----------------------------
@@ -88,9 +86,7 @@ across contexts in case of +
   ?option=value&option=value&…
 ------------------------------
 
-[[Disruptor-Options]]
-Options
-^^^^^^^
+### Options
 
 All the following options are valid for both the **disruptor:** and
 **disruptor-vm:** components.
@@ -145,9 +141,7 @@ The Disruptor component supports 13 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[Disruptor-Waitstrategies]]
-Wait strategies
-^^^^^^^^^^^^^^^
+### Wait strategies
 
 The wait strategy effects the type of waiting performed by the consumer
 threads that are currently waiting for the next exchange to be
@@ -176,9 +170,7 @@ barrier after an initially spinning. |This strategy is a good compromise between
 without incurring significant latency spikes.
 |=======================================================================
 
-[[Disruptor-UseofRequestReply]]
-Use of Request Reply
-^^^^^^^^^^^^^^^^^^^^
+### Use of Request Reply
 
 The Disruptor component supports using link:request-reply.html[Request
 Reply], where the caller will wait for the Async route to complete. For
@@ -196,9 +188,7 @@ buffer. As it is a link:request-reply.html[Request Reply] message, we
 wait for the response. When the consumer on the _disruptor:input_ buffer
 is complete, it copies the response to the original message response.
 
-[[Disruptor-Concurrentconsumers]]
-Concurrent consumers
-^^^^^^^^^^^^^^^^^^^^
+### Concurrent consumers
 
 By default, the Disruptor endpoint uses a single consumer thread, but
 you can configure it to use concurrent consumer threads. So instead of
@@ -214,9 +204,7 @@ increase/shrink dynamically at runtime depending on load, whereas the
 number of concurrent consumers is always fixed and supported by the
 Disruptor internally so performance will be higher.
 
-[[Disruptor-Threadpools]]
-Thread pools
-^^^^^^^^^^^^
+### Thread pools
 
 Be aware that adding a thread pool to a Disruptor endpoint by doing
 something like:
@@ -233,9 +221,7 @@ of the performance gains achieved by using the Disruptor. Instead, it is
 advices to directly configure number of threads that process messages on
 a Disruptor endpoint using the concurrentConsumers option.
 
-[[Disruptor-Sample]]
-Sample
-^^^^^^
+### Sample
 
 In the route below we use the Disruptor to send the request to this
 async queue to be able to send a fire-and-forget message for further
@@ -268,9 +254,7 @@ another thread for further processing. Since this is from a unit test,
 it will be sent to a mock endpoint where we can do assertions in the
 unit test.
 
-[[Disruptor-UsingmultipleConsumers]]
-Using multipleConsumers
-^^^^^^^^^^^^^^^^^^^^^^^
+### Using multipleConsumers
 
 In this example we have defined two consumers and registered them as
 spring beans.
@@ -309,9 +293,7 @@ public class FooEventConsumer {
 }
 -------------------------------------------
 
-[[Disruptor-Extractingdisruptorinformation]]
-Extracting disruptor information
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+### Extracting disruptor information
 
 If needed, information such as buffer size, etc. can be obtained without
 using JMX in this fashion:
@@ -320,4 +302,4 @@ using JMX in this fashion:
 --------------------------------------------------------------------
 DisruptorEndpoint disruptor = context.getEndpoint("disruptor:xxxx");
 int size = disruptor.getBufferSize();
---------------------------------------------------------------------
+--------------------------------------------------------------------
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/camel/blob/28429681/components/camel-dns/src/main/docs/dns-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-dns/src/main/docs/dns-component.adoc b/components/camel-dns/src/main/docs/dns-component.adoc
index 1a0a1ec..1b232d9 100644
--- a/components/camel-dns/src/main/docs/dns-component.adoc
+++ b/components/camel-dns/src/main/docs/dns-component.adoc
@@ -1,4 +1,4 @@
-# DNS Component
+## DNS Component
 
 *Available as of Camel 2.7*
 
@@ -31,9 +31,7 @@ for this component:
 </dependency>
 ------------------------------------------------------------
 
-[[DNS-URIformat]]
-URI format
-^^^^^^^^^^
+### URI format
 
 The URI scheme for a DNS component is as follows
 
@@ -44,9 +42,7 @@ dns://operation[?options]
 
 This component only supports producers.
 
-[[DNS-Options]]
-Options
-^^^^^^^
+### Options
 
 
 // component options: START
@@ -69,9 +65,7 @@ The DNS component supports 2 endpoint options which are listed below:
 // endpoint options: END
 
 
-[[DNS-Headers]]
-Headers
-^^^^^^^
+### Headers
 [width="100%",cols="10%,10%,10%,70%",options="header",]
 |=======================================================================
 
@@ -93,13 +87,9 @@ Optional.
 one specified by the OS will be used. Optional.
 |=======================================================================
 
-[[DNS-Examples]]
-Examples
-^^^^^^^^
+### Examples
 
-[[DNS-IPlookup]]
-IP lookup
-+++++++++
+#### IP lookup
 
 [source,xml]
 --------------------------------------
@@ -114,9 +104,7 @@ This looks up a domain's IP. For example, www.example.com resolves to
  The IP address to lookup must be provided in the header with key
 `"dns.domain"`.
 
-[[DNS-DNSlookup]]
-DNS lookup
-++++++++++
+#### DNS lookup
 
 [source,xml]
 --------------------------------------
@@ -130,9 +118,7 @@ This returns a set of DNS records associ