anchor.diff:  {@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
  +== Authorization
  +
  +Once you have an {@link io.vertx.ext.auth.User} instance you can call methods on it to authorize 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.
  
positive.code: 
  The results of all the above are provided asynchronously in the handler.
  
  Here's an example loading the authorization cache an authorising 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}.
  
  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.
  
negative.code: = Vert.x Auth - Authentication and Authorization
  
  This Vert.x component provides interfaces for authentication and authorization that can be used from
  your Vert.x applications and can be backed by different providers.
  
  Vert.x auth is also used by vertx-web to handle its authentication and authorization.
  
  To use this project, add the following dependency to the _dependencies_ section of your build descriptor:
  
  