DATAES-497 - Polishing.

Consistently add anchors to headings. Tiny syntax tweaks. Remove superfluous newlines.

Original pull request: #291.

src/main/asciidoc/preface.adoc

@@ -1,3 +1,4 @@
+[[preface]]
 = Preface
 
 The Spring Data Elasticsearch project applies core Spring concepts to the development of solutions using the Elasticsearch Search Engine. It provides:

src/main/asciidoc/reference/elasticsearch-clients.adoc

@@ -123,7 +123,7 @@ Mono<IndexResponse> response = client.index(request ->
     .setRefreshPolicy(IMMEDIATE);
 );
 ----
-<1> Use the builder to provide cluster addresses, set default `HttpHeaders` or enbale SSL.
+<1> Use the builder to provide cluster addresses, set default `HttpHeaders` or enable SSL.
 ====
 
 NOTE: The ReactiveClient response, especially for search operations, is bound to the `from` (offset) & `size` (limit) options of the request.

src/main/asciidoc/reference/elasticsearch-new.adoc

@@ -1,8 +1,12 @@
+[[new-features]]
 = What's new
 
+[[new-features.3-2-0]]
 == New in Spring Data Elasticsearch 3.2
 
 * Secured Elasticsearch cluster support with Basic Authentication and SSL transport.
 * Upgrade to Elasticsearch 6.8.1.
 * Reactive programming support with <<elasticsearch.reactive.operations>> and <<elasticsearch.reactive.repositories>>.
 * Introduction of the <<elasticsearch.mapping.meta-model,ElasticsearchEntityMapper>> as an alternative to the Jackson `ObjectMapper`.
+* Field name customization in `@Field`.
+* Support for Delete by Query.

src/main/asciidoc/reference/elasticsearch-object-mapping.adoc

@@ -21,7 +21,7 @@ public class Config extends AbstractElasticsearchConfiguration { <1>
 
   @Override
   public RestHighLevelClient elasticsearchClient() {
-    return RestClients.create(ClientConfiguration.create("localhost:9200")).rest()
+    return RestClients.create(ClientConfiguration.create("localhost:9200")).rest();
   }
 }
 ----
@@ -110,7 +110,7 @@ Those type hints are represented as `_class` attributes within the document and
 ====
 [source,java]
 ----
-public class Person { <1>
+public class Person {              <1>
 
   @Id String id;
   String firstname;
@@ -138,7 +138,7 @@ to already have entity information available when first reading data from the st
 ====
 [source,java]
 ----
-@TypeAlias("human") <1>
+@TypeAlias("human")                <1>
 public class Person {
 
   @Id String id;
@@ -148,7 +148,7 @@ public class Person {
 [source,json]
 ----
 {
-  "_class" : "human", <1>
+  "_class" : "human",              <1>
   "id" : ...
 }
 ----
@@ -254,7 +254,7 @@ public class Config extends AbstractElasticsearchConfiguration {
 
   @Override
   public RestHighLevelClient elasticsearchClient() {
-    return RestClients.create(ClientConfiguration.create("localhost:9200")).rest()
+    return RestClients.create(ClientConfiguration.create("localhost:9200")).rest();
   }
 
   @Bean

src/main/asciidoc/reference/elasticsearch-operations.adoc

@@ -45,7 +45,6 @@ public class TransportClientConfig extends ElasticsearchConfigurationSupport {
   }
 }
 ----
-
 <1> Setting up the <<elasticsearch.clients.transport>>.
 <2> Creating the `ElasticsearchTemplate` bean, offering both names, _elasticsearchOperations_ and _elasticsearchTemplate_.
 <3> Using the <<elasticsearch.mapping.meta-model>> ElasticsearchMapper.
@@ -84,7 +83,6 @@ public class RestClientConfig extends AbstractElasticsearchConfiguration {
 <1> Setting up the <<elasticsearch.clients.rest>>.
 <2> The base class `AbstractElasticsearchConfiguration` already provides the `elasticsearchTemplate` bean.
 <3> Using the <<elasticsearch.mapping.meta-model>> ElasticsearchMapper.
-
 ====
 
 [[elasticsearch.operations.usage]]
@@ -127,7 +125,6 @@ public class TestController {
 }
 
 ----
-
 <1> Let Spring inject the provided `ElasticsearchOperations` bean in the constructor.
 <2> Store some entity in the Elasticsearch cluster.
 <3> Retrieve the entity with a query by id.

src/main/asciidoc/reference/reactive-elasticsearch-repositories.adoc

@@ -4,7 +4,7 @@
 Reactive Elasticsearch repository support builds on the core repository support explained in <<repositories>> utilizing
 operations provided via <<elasticsearch.reactive.operations>> executed by a <<elasticsearch.clients.reactive>>.
 
-Spring Data Elasticsearchs reactive repository support uses https://projectreactor.io/[Project Reactor] as its reactive
+Spring Data Elasticsearch reactive repository support uses https://projectreactor.io/[Project Reactor] as its reactive
 composition library of choice.
 
 There are 3 main interfaces to be used: