anchor.diff:  // CONSOLE
   // TEST[skip:no need to execute snapshot/restore here]
   
  -This will show a recovery of type snapshot in the response
  +The API returns the following response with a recovery type of `snapshot`:
   
   [source,txt]
   --------------------------------------------------------------------------------
   i       s t      ty       st    rep     snap   f  fp   b     bp
   twitter 0 1978ms snapshot done  twitter snap_1 79 8.0% 12086 9.0%
   --------------------------------------------------------------------------------
  -// TESTRESPONSE[non_json]
  +// TESTRESPONSE[non_json]
positive.code: [[cat-recovery]]
  === cat recovery
  
  The `recovery` command is a view of index shard recoveries, both on-going and previously
  completed. It is a more compact view of the JSON <<indices-recovery,recovery>> API.
  
  A recovery event occurs anytime an index shard moves to a different node in the cluster.
  This can happen during a snapshot recovery, a change in replication level, node failure, or
  on node startup. This last type is called a local store recovery and is the normal
  way for shards to be loaded from disk when a node starts up.
  
  As an example, here is what the recovery state of a cluster may look like when there
  are no shards in transit from one node to another:
  
  [source,js]
  ----------------------------------------------------------------------------
  
negative.code: // CONSOLE
  // TEST[setup:twitter]
  
  The API returns the following response:
  
  [source,txt]
  ---------------------------------------------------------------------------
  