anchor.diff:      }
   }
   ----
  -
   <1> `doSomething` can be executed if the current logged in user is the same as the `username` method parameter
   <2> `doSomethingElse` can be executed if the current logged in user is the same as the `name` field of `person` method parameter
  -
  -*Tip* the use of `authentication.` is optional, so using `principal.username` has the same result.
  -
  -#paramName != authentication.principal.username:: This is similar to the previous expression with the difference being that the method parameter must different than the logged in username.
  ++
  +TIP: the use of `authentication.` is optional, so using `principal.username` has the same result.
  +
  +#paramName != authentication.principal.username:: This is similar to the previous expression with the difference being that the method parameter must be different than the logged in username.
   
   @beanName.method():: This syntax allows developers to specify that the execution of method of a specific bean will determine if the current user can access the secured method.
  -+The syntax is best explained with an example.
  -+Let's assume that a `MyComponent` bean has been created like so:
  -
  ++
  +The syntax is best explained with an example.
  +Let's assume that a `MyComponent` bean has been created like so:
  ++
   [source,java]
   ----
   @Component
  
positive.code:     }
  }
  ----
  
  Note that for the `check` method the parameter types must match what is specified in `@PreAuthorize` and that the return type must be a `boolean`.
  
  ===== Combining expressions
  
negative.code:     }
  }
  ----
  +
  The `doSomething` method has been annotated with `@PreAuthorize` using an expression that indicates that method `check` of a bean named `personChecker` needs
  to be invoked to determine whether the current user is authorized to invoke the `doSomething` method.
  +
  An example of the `PersonChecker` could be:
  +
  [source,java]
  ----
  @Component
  