anchor.diff:   * `@Nullable` annotations where specific parameters or return values can be `null`.
   
   Both annotations are meta-annotated with https://jcp.org/en/jsr/detail?id=305[JSR 305]
  -meta-annotations (a dormant JSR but supported by tools like IDEA, Findbugs, etc.)
  +annotations (a dormant JSR but supported by tools like IDEA, Findbugs, etc.)
   to provide useful warnings to Java developers.
   
  -On the Kotlin side - as of the https://blog.jetbrains.com/kotlin/2017/08/kotlin-1-1-4-is-out/[Kotlin 1.1.4 release] -
  +On the Kotlin side - as of https://blog.jetbrains.com/kotlin/2017/08/kotlin-1-1-4-is-out/[Kotlin 1.1.4 release] -
   these annotations https://github.com/Kotlin/KEEP/blob/jsr-305/proposals/jsr-305-custom-nullability-qualifiers.md[are recognized by Kotlin]
  -in order to provide null-safety for the whole Spring Framework API. That means you should
  -never have `NullPointerException` in your code when using Spring Framework and Kotlin because
  +in order to provide null-safety for the whole Spring Framework API. That means
  +one should never experience a `NullPointerException` when using Spring Framework and Kotlin because
   the compiler will not allow it.
   
  -For now, you need to use a `-Xjsr305-annotations=enable` flag (specified via the
  +For now, one needs to use a `-Xjsr305-annotations=enable` flag (specified via the
   `freeCompilerArgs` property with Maven or Gradle Kotlin plugins), but that should become
   the default behavior in an upcoming release of Kotlin.
   
  
positive.code: 
  === Injecting configuration properties
  
  In Java, you can inject configuration properties using annotations like `@Value("${property}")`,
  however in Kotlin `$` is a reserved character that is used for https://kotlinlang.org/docs/reference/idioms.html#string-interpolation[string interpolation].
  
  In order to use `@Value` in Kotlin, you have to escape the `$` character by  writing `@Value("\${property}")`.
  
  As an alternative, you can also customize the properties placeholder prefix by declaring
  the following beans in your configuration:
  
  [source,kotlin]
  ----
  
negative.code: == Annotations
  
  Spring Framework also takes advantage of https://kotlinlang.org/docs/reference/null-safety.html[Kotlin null-safety]
  to determine if a HTTP parameter is required without having to explicitly
  define the `required` attribute.  That means `@RequestParam name: String?` will be treated
  as not required and conversely `@RequestParam name: String` as being required.
  This feature is also supported on the Spring Messaging `@Header` annotation.
  
  In a similar fashion, Spring bean injection with `@Autowired` or `@Inject` uses this information
  to determine if a bean is required or not. `@Autowired lateinit var foo: Foo` implies that a bean
  of type `Foo` must be registered in the application context while `@Autowired lateinit var foo: Foo?`
  won’t raise an error if such bean does not exist.
  
  