anchor.diff:  ----
   
   NOTE: You need to add `compileJava.dependsOn(processResources)` to your build to ensure
  -that resources are processed before code is compiled. Without this directive any
  -`additional-spring-configuration-metadata.json` files will not be processed.
  -
  -The processor will pick up both classes and methods that are annotated with
  +that resources are processed before code is compiled. Without this directive, any
  +`additional-spring-configuration-metadata.json` files are not processed.
  +
  +The processor picks up both classes and methods that are annotated with
   `@ConfigurationProperties`. The Javadoc for field values within configuration classes
  -will be used to populate the `description` attribute.
  -
  -NOTE: You should only use simple text with `@ConfigurationProperties` field Javadoc since
  +is used to populate the `description` attribute.
  +
  +NOTE: You should only use simple text with `@ConfigurationProperties` field Javadoc, since
   they are not processed before being added to the JSON.
   
  -Properties are discovered via the presence of standard getters and setters with special
  -handling for collection types (that will be detected even if only a getter is present). The
  -annotation processor also supports the use of the `@Data`, `@Getter` and `@Setter` lombok
  +Properties are discovered through the presence of standard getters and setters with special
  +handling for collection types (that is detected even if only a getter is present). The
  +annotation processor also supports the use of the `@Data`, `@Getter`, and `@Setter` lombok
   annotations.
   
   [NOTE]
   ====
   If you are using AspectJ in your project, you need to make sure that the annotation
  -processor only runs once. There are several ways to do this: with Maven, you can
  +processor runs only once. There are several ways to do this. With Maven, you can
   configure the `maven-apt-plugin` explicitly and add the dependency to the annotation
   processor only there. You could also let the AspectJ plugin run all the processing
  -and disable annotation processing in the `maven-compiler-plugin` configuration:
  +and disable annotation processing in the `maven-compiler-plugin` configuration, as
  +follows:
   
   [source,xml,indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.code: 
  |`name`
  | String
  | The full name of the property. Names are in lowercase dashed form (e.g.
    `server.servlet.path`). This attribute is mandatory.
  
  |`type`
  | String
  | The full signature of the data type of the property. For example, `java.lang.String`
    but also a full generic type such as `java.util.Map<java.util.String,acme.MyEnum>`.
    This attribute can be used to guide the user as to the types of values that they can
    enter. For consistency, the type of a primitive is specified using its wrapper
    counterpart, i.e. `boolean` becomes `java.lang.Boolean`. Note that this class may be
    a complex type that gets converted from a String as values are bound. May be omitted
    if the type is not known.
  
  |`description`
  | String
  | A short description of the group that can be displayed to users. May be omitted if no
    description is available. It is recommended that descriptions are a short paragraphs,
    with the first line providing a concise summary. The last line in the description should
    end with a period (`.`).
  
  |`sourceType`
  | String
  | The class name of the source that contributed this property. For example, if the
    property was from a class annotated with `@ConfigurationProperties` this attribute
    would contain the fully qualified name of that class. May be omitted if the source type
    is not known.
  
  |`defaultValue`
  | Object
  | The default value which will be used if the property is not specified. Can also be an
    array of value(s) if the type of the property is an array. May be omitted if the default
    value is not known.
  
  |`deprecation`
  | Deprecation
  | Specify if the property is deprecated. May be omitted if the field is not deprecated
    or if that information is not known. See below for more details.
  |===
  
  The JSON object contained in the `deprecation` attribute of each `properties` element can
  
negative.code: 
  
  ===== Handle As
  The **handle-as** provider lets you substitute the type of the property to a more
  high-level type. This typically happens when the property has a `java.lang.String` type,
  because you do not want your configuration classes to rely on classes that may not be
  on the classpath. This provider supports the following parameters:
  
  [cols="1,1,2,4"]
  |===
  