anchor.diff:  
   [source,java]
   ----
  -boolean startupRoute = true;
  -from("activemq:queue:special").autoStartup(startupRoute).to("file://backup");
  -
  -String startupRoute = "true";
  -from("activemq:queue:special").autoStartup(startupRoute).to("file://backup");
  -
  -from("activemq:queue:special").autoStartup("{{startupRouteProperty}}").to("file://backup");
  +// using a boolean
  +from("activemq:queue:special").autoStartup(false)
  +    .to("file://backup");
  +
  +// using a string
  +from("activemq:queue:special").autoStartup("false")
  +    .to("file://backup");
  +
  +// using property placeholders
  +from("activemq:queue:special").autoStartup("{{startupRouteProperty}}")
  +    .to("file://backup");
   ----
   
   == Configuring starting order for routes
   
   You can also configure the order in which routes are started. Previously
  -Camel started the routes in a non deterministic order. Now you have fine
  -grained control in which order the routes should be started. There is a
  +Camel started the routes in a non-deterministic order. Now you have
  +fine-grained control in which order the routes should be started. There is a
   new attribute `startupOrder` which is an `Integer` that states the order.
   Camel then sorts the routes before starting time. The routes with the
   lowest `startupOrder` are started first and the ones with the highest are
   started last.
   
   IMPORTANT: All `startupOrder` defined must be unique among all routes in your
  -xref:camelcontext.adoc[CamelContext]. Otherwise if there are clashes in
  +xref:camelcontext.adoc[CamelContext]. Otherwise, if there are clashes in
   `startupOrder` numbers among routes, the routes will fail to start up throwing
   `org.apache.camel.FailedToStartRouteException`.
   
  
positive.code:         <from uri="direct:start"/>
          <to uri="seda:foo"/>
      </route>
  ----
  
  In this example we have two routes in which we have started that the
  `direct:start` route should be started *after* the `seda:foo` route.
  As `direct:start` is consider the input and we want that `seda:foo`
  route to be up and running beforehand.
  
  You can also mix and match routes with and without `startupOrder`
  define.
  
  === Startup ordering example with startupOrder and without
  
  [source,java]
  ----
      from("seda:foo").startupOrder(1).to("mock:result");
      from("direct:start").startupOrder(2).to("seda:foo");
  
      from("direct:bar").to("seda:bar");
  ----
  
  And the same example with XML DSL:
  
  [source,xml]
  ----
      <route startupOrder="1">
          <from uri="seda:foo"/>
          <to uri="mock:result"/>
  
negative.code:         <from uri="direct:bar"/>
          <to uri="seda:bar"/>
      </route>
  </routes>
  ----
  
  In the route above we have *not* defined a `startupOrder` on the last
  route direct:bar in which Camel will auto assign a number for it, in
  which this case will be 1000; therefore the route will be started
  last.
  
  