anchor.diff:  | Standard YAML list syntax or comma-separated values
   
   | Environment Variables
  -| Upper case format with underscore as the delimiter.
  -  `_` should not be used within a property name
  -| Numeric values surrounded by underscores, such as `MY_ACME_1_OTHER = my.acme[1].other`
  +| Upper case format with underscore as the delimiter (see <<boot-features-external-config-relaxed-binding-from-environment-variables>>).
  +| Numeric values surrounded by underscores (see <<boot-features-external-config-relaxed-binding-from-environment-variables>>)`
   
   | System properties
   | Camel case, kebab case, or underscore notation
  
positive.code: 
  TIP: We recommend that, when possible, properties are stored in lower-case kebab format, such as `my.property-name=acme`.
  
  When binding to `Map` properties, if the `key` contains anything other than lowercase alpha-numeric characters or `-`, you need to use the bracket notation so that the original value is preserved.
  If the key is not surrounded by `[]`, any characters that are not alpha-numeric or `-` are removed.
  For example, consider binding the following properties to a `Map`:
  
negative.code: These default values can then be overridden at runtime with a different file located in one of the custom locations.
  
  NOTE: If you use environment variables rather than system properties, most operating systems disallow period-separated key names, but you can use underscores instead (for example, `SPRING_CONFIG_NAME` instead of `spring.config.name`).
  See <<boot-features-external-config-relaxed-binding-from-environment-variables>> for details.
  
  NOTE: If your application runs in a container, then JNDI properties (in `java:comp/env`) or servlet context initialization parameters can be used instead of, or as well as, environment variables or system properties.
  
  