anchor.diff:    <td>name</td><td>The name you use to identify the plan</td><td>A sequence of letters, digits, and underscore characters. Quota plan names within an account must be unique.</td><td>sliver_quota</td>
   </tr>
   <tr>
  -  <td>memory_limit</td><td>Maximum memory usage (in MB) allowed</td><td>integer</td><td>2048</td>
  +  <td>memory_limit</td><td>Maximum memory usage allowed</td><td>integer with a unit of measurement like M, MB, G, or GB</td><td>2048M</td>
   </tr>
   <tr>
     <td>non_basic_services_allowed</td><td>Determines whether users can provision instances of non-free service plans. Does not control plan visibility. When false, non-free service plans may be visible in the marketplace but instances can not be provisioned.</td><td>true/false</td><td>true</td>
  
positive.code:     ```
      quota_definitions:
        default:
          memory_limit: 10240
          non_basic_services_allowed: true
          total_routes: 1000
          total_services: 100
          trial_db_allowed: true
        silver_quota:
          memory_limit: 2048
          non_basic_services_allowed: true
          total_routes: 500
          total_services: 25
  
negative.code: Example:
  
   ```
  $ cf update-quota small -m 4096M -n medium -r 20 -s 20 --allow-paid-service-plans
   ```
  <p class="note"><strong>Note</strong>: To create or modify quotas for individual spaces rather than across an entire organization, you can use the <code>space-quota</code> command. It is almost identical to the <code>quota</code> command. For example: to create a quota for a space, use <code>create-space-quota</code>. To modify that quota, use the <code>update-quota</code> command. The org manager sets and manages the space quotas.
  