anchor.diff:  
   The results of all the above are provided asynchronously in the handler.
   
  -Here's an example loading the authorization cache an authorising a user:
  +Here's an example loading the authorization cache an authorizing a user:
   
   [source,$lang]
   ----
   {@link examples.AuthCommonExamples#example2}
   ----
   
  -And another example of authorising in a roles based model which uses the the interface {@link io.vertx.ext.auth.authorization.RoleBasedAuthorization}.
  +And another example of authorizing in a roles based model which uses the the interface {@link io.vertx.ext.auth.authorization.RoleBasedAuthorization}.
   
   Please note, as discussed above how the authority string is interpreted is completely determined by the underlying
   implementation and Vert.x makes no assumptions here.
  
positive.code: {@link examples.AuthCommonExamples#example1}
  ----
  
  == Authorisation
  
  Once you have an {@link io.vertx.ext.auth.User} instance you can call methods on it to authorise it. A newly created
  object will contain no cached authorizations, which means that the object is not authorized for any action. Once a user
  is updated using an {@link io.vertx.ext.auth.authorization.AuthorizationProvider} then the cache can be used to verify
  a given authorization.
  
negative.code: 
  _Authentication_ means verifying the identity of a user.
  
  _Authorization_ means verifying a user has an authority.
  
  What the authority means is determined by the particular implementation and we don't mandate any particular model,
  e.g. a permissions/roles model, to keep things very flexible all authorization operations are performed on the type
  