anchor.diff:    </servlet>
   -----------------------------------------------------------------------------------------------
   
  -But its *strongly advised* to use unique servlet-name for each Camel
  +But it is *strongly advised* to use unique `servlet-name` for each Camel
   application to avoid this duplication clash, as well any unforeseen
   side-effects.
   
  -### Sample
  -
  -INFO: From Camel 2.7 onwards it's easier to use <<servlet-component,Servlet>> in
  +=== Sample
  +
  +NOTE: From Camel 2.7 onwards it's easier to use <<servlet-component,Servlet>> in
   Spring web applications. See link:servlet-tomcat-example.html[Servlet
   Tomcat Example] for details.
   
   In this sample, we define a route that exposes a HTTP service at
  -`http://localhost:8080/camel/services/hello`. +
  +http://localhost:8080/camel/services/hello. +
    First, you need to publish the
   http://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/CamelHttpTransportServlet.java[CamelHttpTransportServlet]
   through the normal Web Container, or OSGi Service. +
  
positive.code: can access the `camel-servlet` endpoint through the servlet publish
  address: `("http://localhost:8080/camel/services") + RELATIVE_PATH("/hello")`.
  
  #### Sample when using Spring 3.x
  
  See Servlet Tomcat Example
  
  #### 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
  
negative.code: <web-app>
  -------------------------------------------------------------------------
  
  ==== 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]
  