anchor.diff:  
   <strong><%= modified_date %></strong>
   
  -Quota plans are named sets of memory, service, and instance usage quotas. For example, one quota plan might allow up to 10 services, 10 routes, and 2 GB of RAM, while another might offer 100 services, 100 routes, and 10 GB of RAM. Quota plans have user-friendly names, but are referenced in Cloud Foundry internal systems by unique GUIDs.
  -
  -Quota plans are not directly associated with user accounts. Instead, every organization has a list of available quota plans, and the account admin assigns a specific quota plan from the list to the organization. Everyone in the organization shares the quotas described by the plan. There is no limit to the number of defined quota plans an account can have, but only one plan can be assigned at a time.
  -
  -Setting a quota plan for an [organization](../../concepts/roles.html) is required. Setting a [space](../../concepts/roles.html) quota is optional.
  +Quota plans are named sets of memory, service, and instance usage quotas. For example, one quota plan might allow up to 10 services, 10 routes, and 2 GB of RAM, while another might offer 100 services, 100 routes, and 10 GB of RAM. Quota plans have user-friendly names, but are referenced in Cloud Foundry (CF) internal systems by unique GUIDs.
  +
  +Quota plans are not directly associated with user accounts. Instead, every org has a list of available quota plans, and the account admin assigns a specific quota plan from the list to the org. Everyone in the org shares the quotas described by the plan. There is no limit to the number of defined quota plans an account can have, but only one plan can be assigned at a time.
  +
  +You must set a quota plan for an [org](../../concepts/roles.html#orgs), but you can choose whether to set a [space](../../concepts/roles.html#spaces) quota.
   
   ## <a id='attributes'></a>Org Quota Plan Attributes ##
   
  
positive.code:     </pre>
  1. Run `cf update-quota` with the name of the quota. Use the appropriate flags to specify the attributes.
  
      <pre class='terminal'>
      $ cf update-quota QUOTA [-i INSTANCE_MEMORY] [-m MEMORY] [-n NEW_NAME] [-r ROUTES] [-s SERVICE_INSTANCES] [--allow-paid-service-plans | --disallow-paid-service-plans]
      </pre>
  Options include:
    * `-i` -- Maximum amount of memory an application instance can have. -1 represents an unlimited amount.
    * `-m` -- Total amount of memory a space can have.
    * `-n` -- New name.
    * `-r` -- Total number of routes.
    * `-s` -- Total number of service instances.
    * `--allow-paid-service-plans` -- Can provision instances of paid service plans.
    * `--disallow-paid-service-plans` -- Can not provision instances of paid service plans.
  
      Example:
      <pre class='terminal'> $ cf update-quota small -i 2048M -m 4096M -n medium -r 20 -s 20 --allow-paid-service-plans</pre>
  
  ## <a id='space'></a>Creating and Modifying Quota Plans for a Space ##
  
  For each org, Org Managers create and modify quota plans for a space. If an Org Manager allocates a space quota, CF verifies that resources are within the allocated space limit.  For example, when a Space Developer deploys an application, CF first checks the memory allocation at the space level, then at the org level.
  
  To create or modify quotas for individual [spaces](../../concepts/roles.html) within an entire organization, use the following commands.
  
  ### <a id='new-space'></a>Creating a New Quota Plan for a Space ###
  In a terminal window, run the following command to create a quota for a space. Replace the placeholder attributes with the values for this quota plan:
  
  <pre class='terminal'> $ cf create-space-quota QUOTA [-i INSTANCE_MEMORY] [-m MEMORY] [-r ROUTES] [-s SERVICE_INSTANCES] [--allow-paid-service-plans]
  </pre>
  
  Example:
  
  
negative.code: $ cf create-space-quota big -i 1024M -m 4096M -r 20 -s 20 --allow-paid-service-plans
  </pre>
  
  ### <a id='modify-space'></a>Modify a Quota Plan for a Space ###
  
  Run `cf space-quotas` to find the names of all space quota available to your org. Note the name of the quota plan to be modified.
  
  <pre class='terminal'>
  $ cf space-quotas
  Getting quotas as admin<span>@</span>example.com...
  OK
  
  name           total memory limit   instance memory limit   routes       service instances   paid service plans
  big            2G                   unlimited               0            10                  allowed
  trial          2G                   0                       0            10                  allowed
  </pre>
  
  To modify that quota, use the <code>update-space-quota</code> command. Replace the placeholder attributes with the values for this quota plan:
  
  ```
  $ cf update-space-quota SPACE-QUOTA-NAME [-i MAX-INSTANCE-MEMORY] [-m MEMORY] [-n NEW_NAME] [-r ROUTES] [-s SERVICES] [--allow-paid-service-plans | --disallow-paid-service-plans]
  ```
  
  Example:
    <pre class='terminal'> $ cf update-space-quota big -i 20 -m 4096M -n bigger -r 20 -s 20 --allow-paid-service-plans</pre>
  
  ## <a id='cfhelp'></a>Run cf help ##
  
  For more information regarding quotas, run `cf help` to view a list and brief description of all cf CLI commands. Scroll to view org and space quotas usage and information.
  
  <pre class='terminal'>
  $ cf help
  ...
  ORG ADMIN:
     quotas                                 List available usage quotas
     quota                                  Show quota info
  