anchor.diff:  
   Attaching a Message History to the message will provide a list of all applications that the message passed through since its origination.
   
  -IMPORTANT: The message history is disabled by default (to optimize for lower footprint out of the box). You should only enable message history
  +== Enabling Message History
  +
  +The message history is disabled by default (to optimize for lower footprint out of the box). You should only enable message history
   if needed, such as during development, where Camel can report route stack-traces when a message failed with an exception.
   But for production usage, then message history should only be enabled if you have monitoring systems that rely on gathering these
  -fine grained details. When message history is enabled then there is a slight performance overhead as the history data is stored
  +fine-grained details. When message history is enabled then there is a slight performance overhead as the history data is stored
   in a `java.util.concurrent.CopyOnWriteArrayList` due to the need of being thread safe.
   
  -== Enabling or disabling Message History
  -
   The Message History can be enabled or disabled per CamelContext or per route (disabled by default).
  -For example you can turn it on with
  +For example, you can turn it on with:
   
   [source,java]
   ----
  
positive.code: </camelContext>
  ----
  
  You can also do this per route. Then a route level configuration overrides the CamelContext level configuration.
  
  == Route stack-trace in exceptions logged by error handler
  
  If Message History is enabled, then Camel will leverage this information,
  when the Error Handler logs exhausted exceptions. Then in addition to the caused exception with its stacktrace,
  you can see the message history; you may think this as a "route stacktrace".
  
  And example is provided below:
  
  
negative.code: 	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]
  ----
  
  When Message History is enabled then the full history is logged as shown above. Here we can see the full path
  the message has been routed, where it started from route1, called route2 and returned to route1 again, and so on.
  
  When Message History is disabled (by default) then the error handler logs a brief history with the last node
  where the exception occurred as shown below:
  
  [source,text]
  