anchor.diff:  }
   ----
   1. Specify the `@EnableFullTextSolrIndexing` annotation in an `@Configuration` class
  -2. Spring Content Solr works with any Spring Content Store Module
  +2. Spring Content Solr works with any Spring Content Storage Module
   3. Ensure a `(SolrJ) SolrClient` `@Bean` is instantiated somewhere within your `@Configuration`
   ====
   
  -== Configuring
  +== When your Solr cluster is secured with Basic Authentication 
   
   If required, credentials can be specified using the following configuration properties.
   
  
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: With fulltext-indexing enabled, Store interfaces can be made `Searchable`.  See
  <<content-repositories.search,Searchable Stores>> for more information on how to do this.
  
  == 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.
  
  == Indexing additional attributes
  
  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).
  
  Add a bean that implements `AttributeProvider` to your application's configuration:
  
  ====
  [source, java]
  