anchor.diff:  This LRUCache implementation is using an algorithm where elements that are removed may not be in strict order, and therefore
   not ideal for LRU caches assuming ordering.
   
  -The need for this implementation is not needed anymore in Camel 3, as we are using a simpler default implementation internally.
  -This component is deprecated, and has been removed as Maven dependency in `camel-core` pom.xml file.
  +The implementation is not needed anymore in Camel 3, as we are using a simpler default implementation internally.
  +This component was deprecated, and has been removed as Maven dependency in `camel-core` pom.xml file.
   
   === camel-infinispan
   
   The infinispan component has been splitup into client and embedded server mode.
   The module `camel-infinispan` is the client mode, and `camel-infinispan-embedded` is for server mode.
  -Most use cases would be client mode to integrate with an existing Infinispan cluster, and hence why it was choosen
  +Most use cases would be client mode to integrate with an existing Infinispan cluster, therefore it was choosen
   to be the `camel-infinispan` component.
   
   === camel-activemq and camel-jms
   
  -The JMS and ActiveMQ component now supports optimized toD EIP pattern by using a single endpoint/producer for dynamic destination names.
  +The JMS and ActiveMQ components now support the optimized toD EIP pattern by using a single endpoint/producer for dynamic destination names.
   
   === camel-sjms and camel-sjms2
   
  -These two components has been overhauled and re-written with the goals of being more feature complete with the Spring JMS component.
  -They also no longer uses their own connection pooling, but let you use the existing 3rd party pooling for `ConnectionFactory` which is common practice.
  -The components are now also reactive and non-blocking, and also supports optimized toD EIP pattern by using a single endpoint/producer for dynamic destination names.
  +These two components have been overhauled and re-written with the goal of being more feature complete with the Spring JMS component.
  +They no longer uses their own connection pooling, but let you use the existing 3rd party pooling for `ConnectionFactory` which is common practice.
  +The components are now reactive and non-blocking, and support the optimized toD EIP pattern by using a single endpoint/producer for dynamic destination names.
   
   Many of the previous features and configuration options have been removed/renamed.
   To migrate you need to read their documentation and see what options they now offer.
   
   === Camel-AWS2-SNS
   
  -The policy option now expects a file, since the policy are going to be complex. It can be from classpath:, http: or file: etc.
  +The policy option now expects a file, since the policy is going to be complex. It can be from classpath:, http: or file: etc.
   
   === Camel-AWS2-SQS
   
  -The policy option now expects a file, since the policy are going to be complex. It can be from classpath:, http: or file: etc.
  +The policy option now expects a file, since the policy is going to be complex. It can be from classpath:, http: or file: etc.
   
   === Camel-Github
   
  
positive.code: 
  Camel will now initialize all routes during initialization of `CamelContext` itself.
  Before all routes where lazy initialized when they were started, which happens in the starting phase of `CamelContext`.
  But moving this forward to initialization phase, then we ensure all is done together.
  
  This means that all the resources used in the routes such as EIPs, processors, beans, components, data formats, languages etc.
  are also initialized. An affect of this change is that any custom Camel component that may do initialization logic in
  the constructors of `Consumer` or `Producer` should *not* do this, but move this logic to `doInit` or `doStart` where
  such logic correctly belongs.
  
  === API changes
  
  
negative.code: There are now two components for Infinispan:
  
  - *camel-infinispan* to integrate with remote caches through the Hot Rod protocol (scheme: *infinispan*).
  - *camel-infinispan-embedded* to integrate with local/embedded caches (scheme: *infinispan-embedded*).
  
  As consequence of the refactor:
  
  - the remote and embedded endpoints provide support the same capabilities, as example queries were only possible on a remote cache and now they are suported on both remote and local/embedded caches
  - the configuration options for the endpoint are now specific to the context which remove the possibility to mix unrelated propertis
  