anchor.diff:  
   ### How to Scale
   
  -Because local workers are colocated with the Cloud Controller API pod, they are scaled horizontally along with the API.
  +Because local workers are co-located with the Cloud Controller API pod, they are scaled horizontally along with the API.
   
   ## <a id='cf-api-worker'></a> cf-api-worker
   
  -Colloquially known as "generic workers" or just "workers", these pods are responsible for handling asynchronous work, batch deletes, and other periodic tasks scheduled by the `cf-api-clock`.
  +Known as "generic workers" or just "workers", these pods are responsible for handling asynchronous work, batch deletes, and other periodic tasks scheduled by the `cf-api-clock`.
   
   ### When to Scale
   
  
positive.code: 
  ## <a id='cf-api-server'></a> cf-api-server
  
  The `cf-api-server` is the primary container in CAPI. It, along with `nginx`, powers the Cloud Controller API that all users of Cloud Foundry interact with. In addition to serving external clients, `cf-api-server` also provides APIs for internal components within Cloud Foundry, such as Logging and Networking subsystems.
  
  ### When to Scale
  
  
negative.code: 
  Cloud Controller emits the following metrics:
  
  * `cc_job_queue_length_cc-CF_API_WORKER_POD_NAME` (for example, `cc_job_queue_length_cc_cf_api_worker_565c45df86_h2nsp`) is continuously growing.
  * `cc_job_queue_length_total` is continuously growing.
  
  #### Heuristic Failures
  