Fix 6.3 migrate docs
The 6.3 migrate docs are missing some formatting so they render poorly
(all changes land under plugins). This commit fixes these issues
breaking the 6.3 migrate docs into three sections (API, plugins, and
settings).
[[breaking-changes-6.3]]
== Breaking changes in 6.3
+[[breaking_63_api_changes]]
+=== API changes
+
+==== Suggest stats metrics deprecated
+
+The suggest stats were previously folded into the search on the indices stats
+API. As such, the `suggest` metric on the indices stats API has been a synonym
+for the `search` metric. In 6.3.0, the `suggest` metric is deprecated in favor
+of using `search`.
+
+Similarly, the `suggest` index metric on the `indices` metric on the nodes stats
+API has provided a response containing only an empty object since 5.0.0. In
+6.3.0 this metric has been deprecated.
+
[[breaking_63_plugins_changes]]
=== Plugins changes
==== GCS Repository plugin
-* The repository settings `application_name`, `connect_timeout` and `read_timeout` have been deprecated and
-must now be specified in the client settings instead.
+The repository settings `application_name`, `connect_timeout` and `read_timeout`
+have been deprecated and must now be specified in the client settings instead.
See {plugins}/repository-gcs-client.html#repository-gcs-client[Google Cloud Storage Client Settings].
==== Ingest Geoip Plugin
-* In earlier versions, database files have been stored as gzip compressed files with the extension `.gz` to
-save disk space. As a consequence, database files had to be loaded in memory. Now the default database files
-that are stored uncompressed as `.mmdb` files which allows to memory-map them and save heap memory. Any
-custom database files must also be stored uncompressed. Consequently, the `database_file` property in any
-ingest pipelines that use the Geoip Processor must refer to the uncompressed database files as well.
+In earlier versions, database files have been stored as gzip compressed files
+with the extension `.gz` to save disk space. As a consequence, database files
+had to be loaded in memory. Now the default database files that are stored
+uncompressed as `.mmdb` files which allows to memory-map them and save heap
+memory. Any custom database files must also be stored uncompressed. Consequently,
+the `database_file` property in any ingest pipelines that use the Geoip Processor
+must refer to the uncompressed database files as well.
==== Using the plugin installer without a TTY
@@ -30,6 +46,9 @@ accept these permissions either by keeping standard input open and attaching a
TTY (i.e., using interactive mode to accept the permissions), or by passing the
`--batch` flag.
+[[breaking_63_settings_changes]]
+=== Settings changes
+
==== Concurrency level of analyze requests
Previously, analyze requests would run on the same thread pool as indexing
@@ -60,14 +79,3 @@ place) you can start Elasticsearch with the JVM option
`-Des.thread_pool.write.use_bulk_as_display_name=true` to have Elasticsearch
continue to display the name of this thread pool as `bulk`. Elasticsearch will
stop observing this system property in 7.0.0.
-
-==== Suggest stats metrics deprecated
-
-The suggest stats were previously folded into the search on the indices stats
-API. As such, the `suggest` metric on the indices stats API has been a synonym
-for the `search` metric. In 6.3.0, the `suggest` metric is deprecated in favor
-of using `search`.
-
-Similarly, the `suggest` index metric on the `indices` metric on the nodes stats
-API has provided a response containing only an empty object since 5.0.0. In
-6.3.0 this metric has been deprecated.
