anchor.diff:  
   == Custom Indexing
   
  -When you `@EnableElasticsearchFulltextIndexing` a store event handler is registered that intercepts content being added
  -to a Store and sends that content to your Elasticsearch 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.
  +By default when you `@EnableElasticsearchFulltextIndexing` a store event handler is registered that intercepts content
  +being added to a Store and sends that content to your Elasticsearch cluster 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.
  +
  +When performing custom indexing it is usual to turn of the auto-indexing feature but specifying
  +`spring.content.elasticsearch.autoindex=false` in your application properties.
   
   == Text Extraction
   
  
positive.code: 3. Ensure a `RestHighLevelClient` bean is instantiated somewhere within your `@Configuration`
  ====
  
  == Making Stores Searchable
  
  With fulltext-indexing enabled, Store interfaces can be made `Searchable`.  See
  
negative.code: 
  == Overview
  
  When enabled, the Elasticsearch integration will, by default, forward all content to an Elasticsearch cluster for fulltext indexing.
  
  == Annotation-based Configuration
  
  Spring Content Elasticsearch requires a `RestHighLevelClient` bean that is used as the connection to your Elasticsearch
  cluster.
  
  Elasticsearch can be enabled with the following Java Config.
  
  .Enabling Spring Content Elasticsearch with Java Config
  ====
  