anchor.diff:  
   == Overview
   
  -A multi-project quota, defined by a `*ClusterResourceQuota*` object, allows xref:../admin_guide/quota.adoc#admin-guide-quota[quota]
  -to be shared across multiple projects.  Resources used in each selected project
  -will be aggregated and that aggregate will be used to limit resources across
  -all the selected projects.
  +A multi-project quota, defined by a `*ClusterResourceQuota*` object, allows
  +xref:../admin_guide/quota.adoc#admin-guide-quota[quotas] to be shared across
  +multiple projects. Resources used in each selected project will be aggregated
  +and that aggregate will be used to limit resources across all the selected
  +projects.
   
   [[multi-project-quotas-selecting-projects]]
  -=== Selecting Projects
  +== Selecting Projects
   
   Projects can be selected based on either annotation selection, label selection, or both.
  -For example, `oc create clusterquota for-user --project-annotation-selector openshift.io/requester=<user-name> --hard pods=10 --hard secrets=20`
  -creates: 
  +For example:
  +
  +====
  +----
  +$ oc create clusterquota for-user \
  +     --project-annotation-selector openshift.io/requester=<user-name> \
  +     --hard pods=10 \
  +     --hard secrets=20
  +----
  +====
  +
  +creates:
   
   ====
   [source,yaml]
  
positive.code: [[admin-guide-muliproject-quota]]
  = Multi-Project Quotas
  {product-author}
  {product-version}
  :data-uri:
  
negative.code: 
  
  [[multi-project-quotas-selection-granularity]]
  == Selection Granularity
  
  Due to the locking consideration when claiming quota allocations, the number of
  active projects selected by a multi-project quota is an important consideration.
  Selecting more than 100 projects under a single multi-project quota may have
  detrimental effects on API server responsiveness in those projects.
  