Fixed chunking of breaking changes docs

docs/reference/migration/migrate_6_0/docs.asciidoc

@@ -1,11 +1,11 @@
 [[breaking_60_docs_changes]]
 === Document API changes
 
-==== version type 'force' removed
+==== version type `force` removed
 
 Document modification operations may no longer specify the `version_type` of
 `force` to override any previous version checks.
 
-==== <<upserts>> no longer support versions
+==== <<upserts,Upserts>> no longer support versions
 
 Adding a `version` to an upsert request is no longer supported.

docs/reference/migration/migrate_6_0/indices.asciidoc

@@ -1,7 +1,7 @@
 [[breaking_60_indices_changes]]
-=== Templates changes
+=== Indices changes
 
-==== `template` is now `index_patterns`
+==== Index templates use `index_patterns` instead of `template`
 
 Previously templates expressed the indices that they should match using a glob
 style pattern in the `template` field. They should now use the `index_patterns`
@@ -29,7 +29,7 @@ PUT _template/template_2
 // CONSOLE
 
 
-=== Shadow Replicas have been removed
+==== Shadow Replicas have been removed
 
 Shadow replicas don't see enough usage, and have been removed. This includes the
 following settings:
@@ -38,7 +38,7 @@ following settings:
 - `index.shadow_replicas`
 - `node.add_lock_id_to_custom_path`
 
-=== Open/Close index API allows wildcard expressions that match no indices by default
+==== Open/Close index API allows wildcard expressions that match no indices by default
 
 The default value of the `allow_no_indices` option for the Open/Close index API
 has been changed from `false` to `true` so it is aligned with the behaviour of the

docs/reference/migration/migrate_6_0/mappings.asciidoc

@@ -4,7 +4,7 @@
 ==== Coercion of boolean fields
 
 Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0
-recognizes only `true` and `false` as boolean and will throw an error otherwise. For backwards compatibility purposes, during the 6.x
+recognizes only the strings `true` and `false` as booleans and will throw an error otherwise. For backwards compatibility purposes, during the 6.x
 series the previous coercion rules will continue to work on pre-6.0 indices. This means that you do not need to change affected existing
 mappings immediately. However, it is not possible to create new indices from existing index templates that violate the strict `boolean`
 coercion rules.
@@ -20,7 +20,7 @@ created with Elasticsearch version 6.0 or later.
 
 ==== The `include_in_all` mapping parameter is now disallowed
 
-Since the `_all` field is now disabled by default and cannot be configured for
+Since the ++_all++ field is now disabled by default and cannot be configured for
 indices created with Elasticsearch 6.0 or later, the `include_in_all` setting is
 now disallowed for these indices' mappings.
 

docs/reference/migration/migrate_6_0/rest.asciidoc

@@ -48,7 +48,7 @@ Refresh requests that are broadcast to multiple shards that can have one or more
 shards fail during the request now return a 500 response instead of a 200
 response in the event there is at least one failure.
 
-=== Delete by Query API requires an explicit query
+==== Delete by Query API requires an explicit query
 
 In previous versions of Elasticsearch, delete by query requests without an explicit query
 were accepted, match_all was used as the default query and all documents were deleted