anchor.diff:  A location group is a collection of locations that are all considered at the same level.
   For example, you might want to group all classpath locations, then all external locations.
   Items within a location group should be separated with `;`.
  -See the example in the "`<<features.external-config.files.profile-specific>>`" section for more details.
  +See the example in the "`<<features#features.external-config.files.profile-specific>>`" section for more details.
   
   Locations configured by using `spring.config.location` replace the default locations.
   For example, if `spring.config.location` is configured with the value `optional:classpath:/custom-config/,optional:file:./custom-config/`, the complete set of locations considered is:
  
positive.code: At runtime they will be appended with the names generated from `spring.config.name` before being loaded.
  Files specified in `spring.config.location` are imported directly.
  
  NOTE: Both directory and file location values are also expanded to check for <<boot-features-external-config-files-profile-specific,profile-specific files>>.
  For example, if you have a `spring.config.location` of `classpath:myconfig.properties`, you will also find appropriate `classpath:myconfig-<profile>.properties` files are loaded.
  
  In most situations, each configprop:spring.config.location[] item you add will reference a single file or directory.
  
negative.code: 
  [NOTE]
  ====
  The last-wins strategy applies at the <<features#features.external-config.files.location-groups,location group>> level.
  A configprop:spring.config.location[] of `classpath:/cfg/,classpath:/ext/` will not have the same override rules as `classpath:/cfg/;classpath:/ext/`.
  
  For example, continuing our `prod,live` example above, we might have the following files:
  