anchor.diff:  released, additional policies will be made available.  For each policy, a policy definition must be
   configured in the *System Administration* UI.
   
  +Additionally, it is possible for a plugin, when installed, to contribute one or more policy
  +definitions to the list.  This is a very common way for new policy definitions to be added to
  +apiman.
  +
   ==== Gateways
  -apiman allows multiple logical Gateways to be configured.  The Gateway is the server that actually applies
  +Apiman allows multiple logical Gateways to be configured.  The Gateway is the server that actually applies
   the policies configured in the API Manager to live requests to managed APIs.  When using apiman, at
   least one Gateway must be running and configured in the API Manager.  However, there is no limit to the
   total number of Gateways that may be running.  The typical reason to have multiple Gateways is when
  
positive.code: user can take within an organization.
  
  ==== New Users
  End users must self register with the management UI in order to be given access to an organization or to
  create their own organization. In some configurations it is possible that end user self registration is
  unavailable and instead user information is provided by a standard source of identity such as LDAP.  In
  either case, the actions a user can take are determined by that user's role memberships within the context
  of an organization.
  
  ==== Membership
  End users can be members of organizations. All memberships in an organization include the specific roles the
  user is granted. It is typically up to the owner of an organization to grant role memberships to the members
  of that organization.
  
  
negative.code: published to a Gateway that can handle such load, while the low volume APIs could be published to
  another (perhaps cheaper) Gateway.
  
  Another reason you may want multiple Gateways if if you need some of your APIs to be provided in
  a particular physical region and others in a different one.  In this case, you may have a Gateway
  (perhaps clustered) running in a US data center, while another Gateway (different cluster) is
  running separately in a data center in Europe.
  
  In all cases, the apiman admin must configure these Gateways in the *System Administration* UI.  Each
  Gateway has a name, description, and configuration endpoint.  The configuration endpoint is what the
  API Manager will use when publishing APIs and client apps into the Gateway.
  