anchor.diff:  significant overhead associated with this pre-filter phase.
   ================================
   
  +[role="xpack"]
  +[testenv="basic"]
  +[[monitoring_frozen_indices]]
   == Monitoring frozen indices
   
   Frozen indices are ordinary indices that use search throttling and a memory efficient shard implementation. For API's like the
  -`<<cat-indices>>` frozen indicies may identified by an index's `search.throttled` property (`sth`).
  +<<cat-indices>> frozen indices may identified by an index's `search.throttled` property (`sth`).
   
   [source,js]
   --------------------------------------------------
  
positive.code: // CONSOLE
  // TEST[setup:twitter]
  
  == Searching a frozen index
  
  Frozen indices are throttled in order to limit memory consumptions per node. The number of concurrently loaded frozen indices per node is
  limited by the number of threads in the <<search-throttled>> threadpool,  which is `1` by default. 
  Search requests will not be executed against frozen indices by default, even if a frozen index is named explicitly. This is 
  to prevent accidental slowdowns by targeting a frozen index by mistake. To include frozen indices a search request must be executed with
  the query parameter `ignore_throttled=false`.
  
negative.code: [role="xpack"]
  [testenv="basic"]
  [[frozen-indices]]
  = Frozen indices
  
  [partintro]
  --
  