anchor.diff:        methods: GET,PUT,POST
   ----
   
  -In general, null YAML keys are not included in assembly of the configuration property name, allowing them to be used to
  +In general, `null` YAML keys are not included in assembly of the configuration property name, allowing them to be used to
   any level for disambiguating configuration keys.
   
   == More info on how to configure
  
positive.code: For example, consider the two configuration properties `quarkus.http.cors` and `quarkus.http.cors.methods`.
  One property is the prefix of another, so it may not be immediately evident how to specify both keys in your YAML configuration.
  
  This is solved by using a null key (normally represented by `~`) for any YAML property which is a prefix of another one.  Here's an example:
  
  .An example YAML configuration resolving prefix-related key name conflicts
  [source,yaml]
  
negative.code: ----
  
  NOTE: When injecting a configured value, you can use `@Inject @ConfigProperty` or just `@ConfigProperty`.
  The `@Inject` annotation is not necessary for members annotated with `@ConfigProperty`, a behavior which differs from https://microprofile.io/project/eclipse/microprofile-config[MicroProfile Config].
  
  Edit the `org.acme.config.GreetingResource`, and introduce the following configuration properties:
  
  