anchor.diff:  $ cf create-space-quota big -i 1024M -m 4096M -r 20 -s 20 --allow-paid-service-plans
   </pre>
   
  -### <a id='modify-space'></a>Modifying a Quota Plan for a Space ###
  -
  -1. Run `cf space-quotas` to find the names of all space quota available to your organization. Note the name of the quota plan to be modified.
  -
  -    <pre class='terminal'>
  -    $ cf space-quotas
  -    Getting quotas as admin@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.
  -    <pre class='terminal'> $ 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]</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>
  +  <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 of all cf CLI commands and a brief description of each. Scroll to view org and space quotas usage and information.
  -
  -<pre class='terminal'>
  +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
  
positive.code: 
  <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.
  
  ## <a id='attributes'></a>Org Quota Plan Attributes ##
  
  
negative.code: 
  * Trial DB Allowed: `True`
  
  ## <a id='new'></a>Create a New Quota Plan for an Org ##
  
  <p class="note"><strong>Note</strong>: The org manager sets and manages quotas. See the <a href="../../concepts/roles.html">Orgs, Spaces, Roles, and Permissions topic </a> for more information.</p>
  
  You must set an org quota. You can create a new quota plan for an org in one of two ways:
  
  * Directly [modify the CF deployment manifest](#manifest) before deploying
  * Use [`cf create-quota`](#create-quota) after deploying
  
  ### <a id='manifest'></a> Modify the CF Deployment Manifest ###
  
  The manifest specifies the default quota plans applied to orgs. Follow the steps below to modify the default quota plans by locating and editing the manifest:
  
  1. In a terminal window, run `bosh edit deployment` to open the deployment manifest YAML file in your default text editor.
  1. Search for `quota_definitions`.
  1. Add a new quota definition with values that you specify. Use the default quota definition as a formatting template. The following example shows the `quota_definitions` portion of the `cf.yml` manifest after adding the `silver_quota` plan:
    <pre class='terminal'>
    quota\_definitions:
      default:
        memory\_limit: 10240M
        non\_basic\_services\_allowed: true
        total\_routes: 1000
        total\_services: 100
        trial\_db\_allowed: true
      silver\_quota:
        memory\_limit: 2048M
        non\_basic\_services\_allowed: true
        total\_routes: 500
        total\_services: 25
        trial\_db\_allowed: true
    </pre>
  
  1. Save and close the deployment manifest.
  
  ### <a id='create-quota'></a>Use cf create-quota ###
  
  In a terminal window, run the following command. Replace the placeholder attributes with the values for this quota plan:
  
  ```
  cf create-quota QUOTA [-m TOTAL_MEMORY] [-i INSTANCE_MEMORY] [-r ROUTES] [-s SERVICE_INSTANCES] [--allow-paid-service-plans]
  ```
  
  The command accepts the following flags:
  
  * `-m`: Total amount of memory
  * `-i`: Maximum amount of memory an application instance can have (`-1` represents an unlimited amount)
  * `-r`: Total number of routes
  * `-s`: Total number of service instances
  * `-allow-paid-service-plans`: Can provision instances of paid service plans
  
  Example:
  
  <pre class='terminal'>
  $ cf create-quota small -m 2048M -i 1024M -r 10 -s 10 --allow-paid-service-plans
  </pre>
  
  ## <a id='modify'></a> Modify an Existing Quota Plan for an Org##
  
  You can modify an existing quota plan for an org in one of two ways:
  
  * Directly [modify the CF deployment manifest](#modify) before deploying.
  * Use [`cf update-quota`](#update-quota) after deploying.
  
  ### <a id='modify'></a> Modify the Manifest ###
  
  1. In a terminal window, run `bosh edit deployment` to open the deployment manifest YAML file in your default text editor.
  1. Search for `quota_definitions`.
  1. Modify the value of the attribute.
  1. Save and close the deployment manifest.
  
  ### <a id='update-quota'></a> Use cf update-quota ###
  
  1. Run `cf quotas` to find the names of all quota definitions available to your org. Note the name of the quota plan to be modified.
  
      <pre class='terminal'>
      $ cf quotas
  