anchor.diff:  
   NOTE: Pending
   
  -One of the key features of Dandelion-Datatables is that it is highly configurable. Plenty of options are at your disposal to configure the component through several levels of granularity.
  +One of the key features of Dandelion is that it is highly configurable. Plenty of options, with default values depending on the active <<10-profiles, profile>>, are at your disposal to configure the framework.
   
  -See the <<_appendix_c_configuration_options_reference, configuration options reference>> for an exhaustive list of available options.
  +=== 12.1. Available options
   
  -=== 12.1. Configuration loading
  +See the <<appendix-c-configuration-options-reference, configuration options reference>> for an exhaustive list of available options and their corresponding default value with both `dev` and `prod` <<10-1-built-in-profiles, profiles>>.
   
  -==== 12.1.1. Loading strategy
  +=== 12.2. Reading configuration options
   
  -Any configuration option must be set in a file called <code>datatables.properties</code>. Dandelion-Datatables will load it thanks to the http://docs.oracle.com/javase/6/docs/api/java/util/ResourceBundle.html[ResourceBundle mechanism] and using the following strategy:
  +==== 12.2.1. From classpath
   
  -* First, check if the `dandelion.datatables.configuration` system property is defined.
  -
  -If it exists, Dandelion-Datatables attempts to convert the value to a URL and use it to load a resource bundle called `datatables.properties`
  -
  -* Then, if no system property is defined, Dandelion-Datatables tries to load the same resource bundle (called `datatables.properties`) from the `dandelion/datatables/` folder within the classpath.
  -
  -* If no `datatables.properties` file is found, the default configuration will be used
  -
  -==== 12.1.2. Example using classpath configuration
  -
  -Let's say you use Maven as a build tool. When reading configuration from classpath, you should strictly follow the convention, i.e. place the properties files under the <code>classpath_root/dandelion/datatables/</code> folder.
  +By default, Dandelion expects a file called `dandelion.properties` to be located in the `classpath-root/dandelion` folder.
   
   .Example with a Maven project
   [source, xml]
  
positive.code: |__ src
     |__ main
        |__ java
        |__ resources
           |__ dandelion
              |__ datatables 
                 |__ datatables.properties
                 |__ datatables_FR.properties
                 |__ datatables_ES.properties
  ----
  
  ==== 12.1.3. Example using externalized configuration
  
  Let's say you have the following files:
  
  [source, xml]
  
negative.code: 
  Just add `-Ddandelion.datatables.configuration="C:\Documents\MyApp\"` to the starting script of the application server.
  
  NOTE: Note that when reading from an externalized file, you don't have to put the properties file under the `dandelion/` folder.
  
  
  ==== 12.2.3. Loading strategy
  
  Any configuration option must be set in a file called <code>datatables.properties</code>. Dandelion-Datatables will load it thanks to the http://docs.oracle.com/javase/6/docs/api/java/util/ResourceBundle.html[ResourceBundle mechanism] and using the following strategy:
  
  * First, check if the `dandelion.datatables.configuration` system property is defined.
  
  +
  If it exists, Dandelion-Datatables attempts to convert the value to a URL and use it to load a resource bundle called `datatables.properties`
  
  * Then, if no system property is defined, Dandelion-Datatables tries to load the same resource bundle (called `datatables.properties`) from the `dandelion/datatables/` folder within the classpath.
  
  * If no `datatables.properties` file is found, the default configuration will be used
  
  
  === 12.3. Setting configuration options
  
  Dandelion uses a very particular PropertySource order that is designed to allow sensible overriding of values, properties are considered in the the following order:
  
  ==== 12.3.1. Using properties
  
  .dandelion/dandelion.properties
  [source, properties]
  ----
  asset.minification=true
  ----
  
  ==== 12.3.2. Using filter initialization parameters
  
  You can also set configuration options as initialization parameters of the `DandelionFilter`:
  
  .web.xml
  [source, xml]
  ----
  <filter>
    <filter-name>dandelion</filter-name>
    <filter-class>com.github.dandelion.core.web.DandelionFilter</filter-class>
    <init-param>
      <param-name>asset.minification</param-name>
      <param-value>true</param-value>
    </init-param>
  </filter>
  ----
  
  ==== 12.3.3. Using Java System properties
  
  And finally as Java System properties:
  
  .Inside your server startup script
  [source, bash]
  ----
  -Dasset.minification=true
  ----
  
  [IMPORTANT] 
  ==== 
  Remember that the following precedence rule applies:
  
  *System property* > *filter init param* > *properties file*
  ====
  
  