anchor.diff:  With fulltext-indexing enabled, Store interfaces can be made `Searchable`.  See
   <<content-repositories.search,Searchable Stores>> for more information on how to do this.
   
  -== Custom Indexing
  +== Taking control of the indexing process
   
   When you `@EnableFullTextSolrIndexing` a store event handler is registered that intercepts content being added to a
   Store and sends that content to your Solr instance for full-text indexing.  This is usually all you need.  However,
   sometimes you may need more control over when documents are indexed.  For these cases you can use the `IndexService`
   bean directly in your code to index (or unindex) content as required.
   
  -== Custom Attributes and Filtering Queries
  +== Indexing additional attributes
   
  -By default Spring Content Solr indexes content only.  However, it is common to synchronize additional 
  -attributes from the primary domain model that can then be used for filtering full-text queries or for efficiently populating 
  -search results (removing the need to perform subsequent queries against the primary domain model).
  +By default Spring Content Solr indexes content only.  However, it is common to index additional 
  +attributes (from the primary domain model) that can then be used for filtering subsequent full-text queries 
  +or for efficiently populating search results (removing the need to perform additional queries against the 
  +primary domain model).
   
  -To synchronize additional attributes when content is indexed add a bean that implements `AttributeProvider` to your 
  -application's configuration:
  +Add a bean that implements `AttributeProvider` to your application's configuration:
   
   ====
   [source, java]
  
positive.code: filter queries based on the current execution context. 
  ====
  
  == Search Return Types
  
  `Searchable` is a generic type allowing you to specify the return type of the result set.  The simplest option is to 
  type this interface to String in which case result sets will be collections of content IDs.
  
  You can also type the interface to your own custom class.  Several annotations are available allowing you to tailor full-text search
  results to your specific needs:
  
  - @ContentId; extracts the content ID of the content from your search results
  - @Highlight; extracts highlighted snippets from your search results so you can show users where the query matches are
  - Attribute; extracts the specified attribute from your search results (must be synchronized using an `AttributeProvider`)
negative.code:         };
      }
  ====
  
  Whenever content is indexed this bean will be consulted providing an opportunity to provide the set additional attributes that 
  you would like to be indexed.
  
  To customize the query that gets executed when a Store's Searchable method is invoked add a `FilterQueryProvider` bean to your 
  application's configuration:
  