anchor.diff:  There is no automated means of removing a category. If a category needs to be removed from a CRA
   the following procedure is recommended:
   
  +// TODO: This should have example instructions
   . Ensure that no documents with the value corresponding to the category to be removed will be sent
      either by stopping indexing or by fixing the incoming data stream
  -. Modify the alias definition in zookeeper, removing the collection corresponding to the category.
  +. Modify the alias definition in ZooKeeper, removing the collection corresponding to the category.
   . Delete the collection corresponding to the category. Note that if the collection is not removed
      from the alias first, this step will fail.
   
  -=== Limitations & Assumptions
  -
  -* CRAs are presently unsuitable for non-english data values due to the limits on collection names.
  -  This can be worked around by duplicating the route value to a *_url safe_* base 64 encoded field
  +==== Limitations & Assumptions
  +
  +* CRAs are presently unsuitable for non-English data values due to the limits on collection names.
  +  This can be worked around by duplicating the route value to a *_url safe_* Base64-encoded field
     and routing on that value instead.
   
   * The check for the __CRA__ infix is independent of the regular expression validation and occurs after
     the name of the collection to be created has been calculated. It may not be avoided and is necessary
     to support future features.
   
  -== Improvement Possibilities
  +=== Improvement Possibilities
   
   Routed aliases are a relatively new feature of SolrCloud that can be expected to be improved.
   Some _potential_ areas for improvement that _are not implemented yet_ are:
  
positive.code: * *TRAs*: Ways to automatically optimize (or reduce the resources of) older collections that aren't expected to receive more
    updates, and might have less search demand.
  
  * *CRAs*: Intrinsic support for non-english text via base64 encoding
  
  * *CRAs*: Supply an initial list of values for cases where these are known before hand to reduce pauses during indexing
  
  * CloudSolrClient could route documents to the correct collection based on the route value instead always picking the
    latest/first.
  
  * Presently only updates are routed and queries are distributed to all collections in the alias, but future
  
negative.code:   create more collections than expected during initial testing. Removing them after such events is overly tedious.
  
  As always, patches and pull requests are welcome!
  
  == Collection Commands and Aliases
  Starting with version 8.1 SolrCloud supports using alias names in collection commands where normally a
  collection name is expected. This works only when the following criteria are satisfied:
  
  * an alias must not refer to more than one collection
  * an alias must not refer to a <<Routed Aliases,Routed Alias>> (see below)
  
  If all criteria are satisfied then the command will resolve alias names and operate on the collections the aliases
  refer to as if it was invoked with the collection names instead. Otherwise the command will not be executed and
  an exception will be thrown.
  