anchor.diff:  |Total number of persistent volume claims
   |===
   
  -== Quota enforcement
  +== Quota Enforcement
   
  -After a quota is first created in a project, the project restricts the ability to
  -create any new resources that may violate a quota constraint until it has calculated
  -updated usage statistics.
  +After a project quota is first created, the project restricts the ability
  +to create any new resources that may violate a quota constraint until it has
  +calculated updated usage statistics.
   
  -Once a quota is created and usage statistics are up-to-date, the project accepts the
  -creation of new content. When you create resources, your quota usage is incremented
  -immediately upon the request to create or modify the resource. When you delete
  -a resource, your quota use is decremented during the next full recalculation of
  -quota statistics for the project. As a result, it may take a moment for your quota
  -usage statistics to be reduced to their current observed system value when you
  -delete resources.
  +Once a quota is created and usage statistics are up-to-date, the project accepts
  +the creation of new content. When you create or modify resources, your quota
  +usage is incremented immediately upon the request to create or modify the
  +resource. When you delete a resource, your quota use is decremented during the
  +next full recalculation of quota statistics for the project. When you delete
  +resources, a link:#configuring_quota_sync_period[configurable amount of time]
  +determines how long it takes to reduce quota usage statistics to their current
  +observed system value.
   
  -If your modification to a project would exceed a quota usage limit, the action
  -is denied by the server, and an appropriate error message is returned to the
  -end-user. The error explains what quota constraint was violated, and what their
  -currently observed usage stats are in the system.
  +If project modifications exceed a quota usage limit, the server denies the
  +action, and an appropriate error message is returned to the end-user explaining
  +the quota constraint violated, and what their currently observed usage stats are
  +in the system.
   
  -== Sample resource quota file
  +== Sample Resource Quota File
   
   resource-quota.json
   ====
  
positive.code: 
  == Overview
  
  A *ResourceQuota* object enumerates hard resource usage limits per project.  It
  can limit the total number of a particular type of object that may be created in
  a project, and the total amount of compute resources that may be consumed by
  resources in that project.
  
  == Usage limits
  
  The following describes the set of limits that may be enforced by a *ResourceQuota*.
  
  .Usage limits
  [cols="3a,8a",options="header"]
  
negative.code: services                3       5
  ----
  
  [[configuring_quota_sync_period]]
  
  == Configuring the Quota Synchronization Period
  
  When a set of resources are deleted, the synchronization timeframe of resources
  is determined by the `*resource-quota-sync-period*` setting in the
  *_/etc/openshift/master/master-config.yaml_* file. Before your quota usage is
  restored, you may encounter problems when attempting to reuse the resources.
  Change the `*resource-quota-sync-period*` setting to have the set of resources
  regenerate at the desired amount of time (in seconds) and for the resources to
  be available again:
  
  ====
  ----
  kubernetesMasterConfig:
    apiLevels:
    - v1beta3
    - v1
    apiServerArguments: null
    controllerArguments:
      resource-quota-sync-period:
        - "10s"
  ----
  ====
  
  Adjusting the regeneration time can be helpful for creating resources and
  determining resource usage when automation is used.
  
  [NOTE]
  ====
  The `*resource-quota-sync-period*` setting is designed to balance system
  performance. Reducing the sync period can result in a heavy load on
  the master.
  ====
  