anchor.diff:  Example:
   
   <pre class='terminal'>
  -$ cf create-quota small -m 2048M -i 1024M -r 10 -s 10 --allow-paid-service-plans
  +$ cf create-quota small -m 1024M -i 1024M -l 2k -r 10 -s 10 --allow-paid-service-plans
   </pre>
   
   
  
positive.code: 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: 1024M
            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
  
negative.code: </div>
  <% end %>
  
  Quota plans are named sets of memory, service, log-rate and instance usage quotas. For example, one quota plan might allow up to 10 services, 10 routes, 2&nbsp;GB of RAM, and generate 2&nbsp;KB of logs, while another might offer 100 services, 100 routes, 10&nbsp;GB of RAM, and generate 16&nbsp;KB of logs. Quota plans have user-friendly names, but are referenced in <%= vars.app_runtime_first %> 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.
  
  