anchor.diff:  	my.servers[1]=another.example.com
   ----
   
  -To bind to properties like that by using the Spring `DataBinder` utilities (which is what
  +To bind to properties like that by using Spring Boot's `Binder` utilities (which is what
   `@ConfigurationProperties` does), you need to have a property in the target bean of type
   `java.util.List` (or `Set`) and you either need to provide a setter or initialize it with
   a mutable value. For example, the following example binds to the properties shown
  
positive.code: 
  
  
  [[boot-features-external-config-complex-type-merge]]
  ==== Merging YAML Lists
  As <<boot-features-external-config-loading-yaml,we showed earlier>>, any YAML content is
  ultimately transformed to properties. That process may be counter-intuitive when
  overriding "`list`" properties through a profile.
  
  For example, assume a `MyPojo` object with `name` and `description` attributes that are
  `null` by default. The following example exposes a list of `MyPojo` objects from
  
negative.code: 	  profiles: dev
  	acme:
  	  list:
  	    - name: my another name
  ----
  
  If the `dev` profile is not active, `AcmeProperties.list` contains one `MyPojo` entry,
  