Remove references to quilr according to pull req #65 in riak_search

pages/Riak/Searching-and-Aggregating-Data/Riak-Search/Riak-Search---Indexing.textile

@@ -243,7 +243,7 @@ Riak Search implements Stop Words, much as you might find in Solr itself:
 
 The source code for Riak Search's "default analyzer factory" can be found here:
 
-[[http://github.com/basho/riak_search/blob/master/apps/qilr/src/text_analyzers.erl]]
+[[http://github.com/basho/riak_search/blob/master/src/text_analyzers.erl]]
 
 In short, the following words will be skipped when indexing. The official list is maintained in the source file, linked above:
 

pages/Riak/Searching-and-Aggregating-Data/Riak-Search/Riak-Search---Schema.textile

@@ -190,7 +190,7 @@ You can create your own custom analyzers in Erlang.
 
 Some tips:
 
-* Model your custom analyzer after an existing analyzer.  See "apps/qilr/src/text_analyzers.erl" for sample code.
+* Model your custom analyzer after an existing analyzer.  See [[https://github.com/basho/riak_search/blob/master/src/text_analyzers.erl"]] for sample code.
 
 * The analyzer should take a string and configuration parameters and return a list of tokens. The order of tokens is important for proximity searching.
 

pages/Riak/Searching-and-Aggregating-Data/Riak-Search/Riak-Search.textile

@@ -93,7 +93,6 @@ Riak Search is comprised of:
 ** *Bitcask* -  Default storage backend used by Riak KV.
 * *Riak Search* - Distributed index and full-text search engine.
 ** *Merge Index* - Storage backend used by Riak Search. This is a pure Erlang storage format based roughly on ideas borrowed from other storage formats including log structured merge trees, sstables, bitcask, and the Lucene file format.
-** *Qilr* - Library for parsing queries into execution plans and documents into terms.
 ** *Riak Solr* - Adds a subset of Solr HTTP interface capabilities to Riak Search.